search

nodejs / llnode

An lldb plugin for Node.js and V8, which enables inspection of JavaScript states for insights into Node.js processes and their core dumps.
Other
1.15k stars 99 forks source link

Cannot install on Windows. #321

Open danny-su opened 4 years ago

danny-su commented 4 years ago

if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\....\node_modules\node-gyp\bin\node-gyp.js" build /p:CLToolExe="clang-cl.exe" /p:CLToolPath="C:\Program Files\LLVM\bin" ) else (node "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" build /p:CLToolExe="clang-cl.exe" /p:CLToolPath="C:\Program Files\LLVM\bin" ) Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch. C:\Users\danny\AppData\Roaming\npm\node_modules\llnode\build\binding.sln : error MSB4014: The build stopped unexpectedly because of an internal failure. C:\Users\danny\AppData\Roaming\npm\node_modules\llnode\build\binding.sln : error MSB4014: System.ArgumentException: The name "plugin:CLToolExe=clang-cl. exe" contains an invalid character ".".

bzoz commented 4 years ago

Please provide the entire, verbose log (add --verbose to the npm command). Put it inside triple ticks so the formatting works:

```
like this, output goes here
```

Also: what's your Windows version and Visual Studio version?

No9 commented 4 years ago

I also suspect that the error is accurate 

error MSB4014: System.ArgumentException: The name "plugin:CLToolExe=clang-cl. exe" contains an invalid character ".".

Please can you post the file C:\Users\danny\AppData\Roaming\npm\node_modules\llnode\build\binding.sln

manuel220x commented 3 years ago

having the same issue (LLVM 9)

Microsoft Visual Studio Solution File, Format Version 12.00
# Visual Studio 2015
Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "plugin", "plugin.vcxproj", "{7B017421-278E-EC0A-5B2D-BDDD478EE171}"
EndProject
Global
    GlobalSection(SolutionConfigurationPlatforms) = preSolution
        Debug|x64 = Debug|x64
        Release|x64 = Release|x64
    EndGlobalSection
    GlobalSection(ProjectConfigurationPlatforms) = postSolution
        {7B017421-278E-EC0A-5B2D-BDDD478EE171}.Debug|x64.ActiveCfg = Debug|x64
        {7B017421-278E-EC0A-5B2D-BDDD478EE171}.Debug|x64.Build.0 = Debug|x64
        {7B017421-278E-EC0A-5B2D-BDDD478EE171}.Release|x64.ActiveCfg = Release|x64
        {7B017421-278E-EC0A-5B2D-BDDD478EE171}.Release|x64.Build.0 = Release|x64
    EndGlobalSection
    GlobalSection(SolutionProperties) = preSolution
        HideSolutionNode = FALSE
    EndGlobalSection
EndGlobal
dolezel commented 1 year ago

Facing same issue. There is some docs about the error - https://learn.microsoft.com/en-us/visualstudio/msbuild/how-to-build-specific-targets-in-solutions-by-using-msbuild-exe?view=vs-2022#to-build-a-specific-target-of-a-specific-project-in-a-solution