You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to build the llnode module on Windows, which can only be built with clang-cl. The project previously (ab)used the passthrough of arguments to msbuild to configure the CLToolPath and CLToolExe properties, which has hence been fixed in #1164. (nodejs/llnode#321, nodejs/llnode#377)
This does have some effect on the configure phase, but only accepts GCC (not CL) compatible compilers, and it has no effect on the building phase which still uses CL.exe.
This issue might be a case of #1537 if there is no special way to specify the compiler executable on Windows.
Node Version: node v18.20.4 npm 10.7.0
Platform: Microsoft Windows 11 Enterprise 10.0.22631 N/A Build 22631 x64-based PC
Compiler: MSBuild version 17.11.2+c078802d4 for .NET Framework 17.11.2.32701 MSVC 19.41.34120 for x64
I am trying to build the llnode module on Windows, which can only be built with clang-cl. The project previously (ab)used the passthrough of arguments to msbuild to configure the
CLToolPath
andCLToolExe
properties, which has hence been fixed in #1164. (nodejs/llnode#321, nodejs/llnode#377)I have attempted the following to no avail,
binding.gyp
This does put the properties into the vcxproj, but in the
ClCompile
section. https://stackoverflow.com/a/31362960/12385184CC
andCXX
environment variables (Build defaults to x86 on a x64 Windows machine. How to force an x64 build? #2813 (comment))This does have some effect on the configure phase, but only accepts GCC (not CL) compatible compilers, and it has no effect on the building phase which still uses CL.exe.
This issue might be a case of #1537 if there is no special way to specify the compiler executable on Windows.
The text was updated successfully, but these errors were encountered: