| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
This does the configure + build dance before running any of the JS tests. Probably should be moved but I kept it as close as possible to the existing order for now.
Sorry, something went wrong.
There was a problem hiding this comment.
Could console.log call perhaps be removed in favour of just printing console.log(`building addon ${path}`); before 9864090#diff-31601f8dbf082ea61af036efe1e9c00dR54?
Sorry, something went wrong.
There was a problem hiding this comment.
Perhaps --silent could be added to this to avoid extra output?
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM as long as ci is green.
Sorry, something went wrong.
|
Remember that time when my pull request worked on Windows on the first try? That's right, me neither... LINK : fatal error LNK1181: cannot open input file 'c:\workspace\node-test-binary-windows\RUN_SUBSET\0\VS_VERSION\vs2015\label\win2008r2\test\addons\Release\node.lib' [c:\workspace\node-test-binary-windows\RUN_SUBSET\0\VS_VERSION\vs2015\label\win2008r2\test\gc\build\binding.vcxproj] node-gyp looks for node.lib in a hard-coded (in lib/build.js) location relative to --nodedir=.... Needs more bovine coiffure. (yak shaving) |
Sorry, something went wrong.
There was a problem hiding this comment.
Please could you also remove the relative include_dirs from test/addons/zlib-binding/binding.gyp?
Sorry, something went wrong.
There was a problem hiding this comment.
Also test/addons/include should be added to .gitignore?
Sorry, something went wrong.
|
All the red lines (not red tests) make me so warm and fuzzy inside 😻 |
Sorry, something went wrong.
|
I'm not really sure where commit eebfadc ended up but it's a solution for passing on windows |
Sorry, something went wrong.
|
Let's see if I'm right: https://ci.nodejs.org/job/node-test-pull-request/7392/ https://ci.nodejs.org/job/node-test-commit/9097/ |
Sorry, something went wrong.
|
Well it's green where it counts https://ci.nodejs.org/job/node-test-binary-windows/7690/ 🤷 |
Sorry, something went wrong.
|
Rebased and included a simplified version of @refack's fix. Not sure yet how I feel about installing node.lib to $(PREFIX)/node/Release but I suppose it doesn't matter much because we don't otherwise use install.py on Windows. CI: https://ci.nodejs.org/job/node-test-pull-request/7511/
Done.
I'm not sure why but it doesn't show up with git status. It's not because of an exclusion in my global .gitignore, that I checked by moving it out of the way. |
Sorry, something went wrong.
|
Well, that clearly didn't work. The ARM addons buildbot is passing an Intel-only flag to V8: g++ '-DV8_TARGET_ARCH_ARM' '-DENABLE_DISASSEMBLER' '-DV8_I18N_SUPPORT' '-DUSE_EABI_HARDFLOAT=1' -I../deps/v8 -pthread -Wall -Wextra -Wno-unused-parameter -fno-strict-aliasing -m32 -fdata-sections -ffunction-sections -O3 -O3 -fno-omit-frame-pointer -fno-rtti -fno-exceptions -std=gnu++0x -MMD -MF /home/iojs/build/workspace/node-test-binary-arm/out/Release/.deps//home/iojs/build/workspace/node-test-binary-arm/out/Release/obj.host/v8_libbase/deps/v8/src/base/bits.o.d.raw -c -o /home/iojs/build/workspace/node-test-binary-arm/out/Release/obj.host/v8_libbase/deps/v8/src/base/bits.o ../deps/v8/src/base/bits.cc g++: error: unrecognized command line option ‘-m32’ deps/v8/src/v8_libbase.host.mk:112: recipe for target '/home/iojs/build/workspace/node-test-binary-arm/out/Release/obj.host/v8_libbase/deps/v8/src/base/bits.o' failed Some weird interaction with the distributed build perhaps? One more try in case it was a fluke, I need to test the fixed Windows fix anyway: https://ci.nodejs.org/job/node-test-pull-request/7513/ |
Sorry, something went wrong.
Not sure either, but it kinda makes sense, since otherwise the headers are only half useful (unless build target was a shared_lib). Ref: a short discussion about this by the GYP authors indutny/gyp.js#37 |
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM if CI passes.
Sorry, something went wrong.
Until now we built add-ons by pointing node-gyp at the src/ directory. We've had at least one DOA release where add-ons were broken because of a header dependency issue that wasn't caught because we build our test add-ons in a non-standard way. This commit does the following: * Use tools/install.py to install the headers to test/addons/include. * Add a script to build everything in test/addons. * Remove the pile-up of hacks from the Makefile. The same logic is applied to test/addons-napi and test/gc. Everything is done in parallel as much as possible to speed up builds. Ideally, we derive the level of parallelism from MAKEFLAGS but it lacks the actual `-j<n>` flag. That's why it simply spawns as many processes as there are processors for now. The exception is tools/doc/addon-verify.js: I switched it to synchronous logic to make it easy to use from another script. Since it takes no time at all to do its work, that seemed like a reasonable trade-off to me. Refs: nodejs#11628
|
@bnoordhuis I think this mainly just needs a rebase and is otherwise good to go? It is stalled since quite a while and I would go ahead and close this in a couple of days otherwise. |
Sorry, something went wrong.
|
Closing this due to a long inactivity and no response. @bnoordhuis please reopen if you want to follow up on this. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Until now we built add-ons by pointing node-gyp at the src/ directory.
We've had at least one DOA release where add-ons were broken because of
a header dependency issue that wasn't caught because we build our test
add-ons in a non-standard way.
This commit does the following:
The same logic is applied to test/addons-napi and test/gc.
Everything is done in parallel as much as possible to speed up builds.
Ideally, we derive the level of parallelism from MAKEFLAGS but it lacks
the actual -j<n> flag. That's why it simply spawns as many processes
as there are processors for now.
The exception is tools/doc/addon-verify.js: I switched it to synchronous
logic to make it easy to use from another script. Since it takes no time
at all to do its work, that seemed like a reasonable trade-off to me.
Refs: #11628
CI: https://ci.nodejs.org/job/node-test-pull-request/7225/