-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: duplicate ninja rules for v8 (cross-compiling) #185
base: main
Are you sure you want to change the base?
Conversation
Please rebase. |
09e3ad8
to
58e88cf
Compare
Rebased again. |
avoids duplicate ninja rules for v8 used in host and target From: minrk/node@5e533cb Signed-off-by: Thomas Petazzoni <[email protected]> Reported in nodejs/node#46690 and nodejs/node#37441 Minor refactoring as recommended by Christian Clauss. Signed-off-by: Tim Orling <[email protected]>
58e88cf
to
ef910d3
Compare
Rebased to pick up the |
@cclauss I believe I addressed your recommendations and rebase concerns. Anything else that needs to be done or any more discussion? |
This pull request is rebased and the tests are all green. ✅ Thanks for that. Now what we need is some maintainer who has enough expertise to review and approve or make suggestions. |
@cclauss great. Thank you for the response. |
I can confirm that this goes with the default naming conventions of |
The v8 library supports only limited number of build platforms based on the host architecture. The rule there is the bitness (the mixing of 32bit and 64bit architectures seems to be in most cases disallowed). Thus this adds usage of the emulator of the host platform and builds tools for that. This also allows us to use ninja instead of make when build ≠ host while waiting for nodejs/gyp-next#185 to be merged. Co-authored-by: Ivan Trubach <[email protected]>
avoids duplicate ninja rules for v8 used in host and target
From: minrk/node@5e533cb
Reported in nodejs/node#46690 and nodejs/node#37441