build: fix Windows small-icu build with ClangCL - #64263
Closed
moluopro wants to merge 1 commit into
Closed
Conversation
Signed-off-by: moluopro <moluopro@qq.com>
Collaborator
|
Review requested:
|
StefanStojanovic
approved these changes
Jul 3, 2026
StefanStojanovic
left a comment
Contributor
There was a problem hiding this comment.
Tested it locally and it worked.
Collaborator
Member
|
This needs a rebase, and resolving conflicts in |
Contributor
Author
|
Thanks, but could you clarify why #65095, which was opened later to address the same issue, was merged before this already-approved PR? |
Member
I looked into #65095. It's possible that collaborators prioritized it's review since a bug report was linked to it? |
Member
|
Closing since it's fixed in #65095 |
realthunder
added a commit
to realthunder/v8-embed-feedstock
that referenced
this pull request
Sep 2, 2026
Both routes advanced and each hit one thing. conda-clang-cl (ninja) compiled 500 edges with clang-cl 21.1.8 -- ICU, the host tools, the builtins library found and on the link line -- and stopped in v8_libbase at v8config.h: "C++20 or later required." Two causes, both needed fixing: - gyp's ninja generator appends CFLAGS, CXXFLAGS and LDFLAGS from the environment after its own flags, and conda's clang-cl activation exports /std:c++17 in CXXFLAGS, which then outranked whatever V8 said. bld.bat now strips /std:, -std and -fuse-ld= from those, and clears LDFLAGS: the `-Xlinker /DEFAULTLIB:...` there is clang-driver syntax that link.exe answered with LNK4044, and patch 0104 already links the builtins library in a form it understands. build.sh strips -std= for the same reason. - Even with a clean environment there was no /std: at all: with clang, common.gypi expresses the standard as the MSBuild-only property LanguageStandard (stdcpp20), and gyp's ninja emulation has no case for it. Patch 0106 adds one, per language -- C files get /std:c11, not c++20, which clang-cl would refuse where cl.exe ignores it. Verified on Windows ninja files generated here (gyp's ninja-win flavour, with its registry probes stubbed): cflags_cc = /TP /std:c++20, cflags_c = /std:c11, and the MSVC branch's -std:c++20 gone. vs-clang-cl (MSBuild) built ICU's tools with Visual Studio's clang-cl 22.1.3 and stopped writing the ICU data object: genccode: CPU architecture must be set for Clang-CL A genccode compiled by clang will not infer the machine type from its own macros, and node's small-icu action for Windows never passed -c. Node's Windows builds are full-icu, so nobody hit it until now; the fix is nodejs/node#64263, after 26.6.0, and patch 0107 is that one line. The ninja route runs the same action and would have reached it too. Also caught before it could fail: v8config.h guards on __cplusplus, which cl.exe reports as 199711L unless given /Zc:__cplusplus. The consumer test compiles with cl.exe on Windows, so it gets the flag. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KzqRnuUy9dpMik6sxVaKXd
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When building the static
libnodelibrary withsmall-icuon Windows, thegenccodestep fails under ClangCL because the target CPU architecture is not passed to the tool.The Windows full-ICU branch already passes
-c <(target_arch)togenccodewhenclang==1, while preserving the existing MSVC command. The small-ICU branch did not have the same conditional handling, so it hit ICU's architecture check under ClangCL.This change makes the Windows small-ICU branch consistent with the full-ICU branch:
-c <(target_arch)whenclang==1.genccodecommand unchanged for the non-ClangCL MSVC path.Reproduction
Windows builds for Node.js 24+ use ClangCL, and the build fails with: