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

Fix ninja build on Windows & --build-v8-with-gn improvements #56

Closed
wants to merge 1 commit into from

Conversation

agrieve
Copy link

@agrieve agrieve commented Apr 17, 2018

No description provided.

Build Fixes:
 * Fixed several hardcoded paths to use <(STATIC_LIB_PREFIX) &
   <(STATIC_LIB_SUFFIX)
 * Added GENERATOR=='ninja' conditionals to /WHOLEARCHIVE flags (msbuild
   puts .lib files under separate directories).
 * Add missing link_settings for v8_monolith
 * Set use_sysroot=false only for non-windows builds.

Other improvements:
 * Split gn gen step from ninja step for --build-v8-with-gn
 * Add use_goma=true GN arg when --build-v8-with-gn-use-goma is passed

To build using clang-cl:

  set CC="%cd%\deps\v8\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe"
  python configure --build-v8-with-gn
@hashseed
Copy link
Member

hashseed commented Apr 17, 2018

The build instructions are

  set CC="%cd%\deps\v8\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe"
  python configure --build-v8-with-gn

However, clang-cl.exe is checked out via gclient hooks during configure in the first place, so that part seems a bit unpolished. Is there any way to hide this detail inside of configure?

@agrieve
Copy link
Author

agrieve commented Apr 17, 2018

The build also works with msvc, so we wouldn't want to set it unconditionally. Maybe add a --use-clang-cl flag?

@hashseed
Copy link
Member

Yup that makes sense.

@agrieve
Copy link
Author

agrieve commented Apr 17, 2018

Split this into #60 #58

@agrieve agrieve closed this Apr 17, 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.

2 participants