Skip to content
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

deps, v8: fix build torque on Windows #61

Closed
wants to merge 1 commit into from

Conversation

refack
Copy link

@refack refack commented May 17, 2018

On Windows the torque binary needs to be compiled and linked
with exception semantics and assume V8 is embedded

Fixes: #57

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • commit message follows commit guidelines

@refack refack mentioned this pull request May 17, 2018
@refack
Copy link
Author

refack commented May 17, 2018

@refack refack force-pushed the fix-v8-torque-build-on-windows branch 2 times, most recently from 6915796 to 03770e0 Compare May 17, 2018 19:51
@refack
Copy link
Author

refack commented May 17, 2018

P.S. spec'ing at the target level gets this to build with ninja as well

@refack
Copy link
Author

refack commented May 17, 2018

Full CI: https://ci.nodejs.org/job/node-test-commit/18567/ (✔️ except for flake)

@refack refack self-assigned this May 17, 2018
@targos
Copy link
Member

targos commented May 18, 2018

@nodejs/gyp

Copy link
Member

@bnoordhuis bnoordhuis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM with a comment.

'defines!': [
'_HAS_EXCEPTIONS=0',
'BUILDING_V8_SHARED=1',
'BUILDING_UV_SHARED=1',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess these were the missing keys? (Or rather, not missing...)

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(To figure this out I run the GN recipe and bisected the diff in the generated ninja files. That was not fun)
I guess BUILDING_UV_SHARED is inconsequential.

'include_dirs': [
'../third_party/antlr4/runtime/Cpp/runtime/src',
'../src/torque',
],
'default_configuration': 'Release',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't be necessary.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ack

@nodejs-ci nodejs-ci force-pushed the canary branch 3 times, most recently from b2733b8 to 491eb0f Compare May 23, 2018 07:10
On windows the torque binary needs to be compiled and linked
with exception semantics and assume V8 is embedded

Fixes: nodejs#57
@refack refack force-pushed the fix-v8-torque-build-on-windows branch from 03770e0 to d125781 Compare May 24, 2018 15:09
@refack
Copy link
Author

refack commented May 24, 2018

@targos
Copy link
Member

targos commented May 24, 2018

CI is as green as it can be (test failure is a known issue). Thanks!

@targos
Copy link
Member

targos commented May 24, 2018

Pushed to canary-base in nodejs/node@11c42e3

@targos targos closed this May 24, 2018
@refack refack deleted the fix-v8-torque-build-on-windows branch May 24, 2018 17:34
@refack refack removed their assignment Sep 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Windows build failure
3 participants