nwjs / nwjs/node

Unable to build (libcpp.lib not found)

Open
#53 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
22
Forks
42
PR merge metrics
No merged PRs in 30d

Description

Hello,

For now it's impossible to build node correctly. This is what I get:

FAILED: node.dll node.dll.lib node.dll.pdb
f:\dev\depot_tools\bootstrap-2@3_8_10_chromium_26_bin\python\bin\python.exe gyp-win-tool link-with-manifests environment.x64 True node.dll "f:\dev\depot_tools\bootstrap-2@3_8_10_chromium_26_bin\python\bin\python.exe gyp-win-tool link-wrapper environment.x64 False ..\..\third_party/llvm-build/Release+Asserts/bin/lld-link.exe /nologo /IMPLIB:node.dll.lib /DLL /OUT:node.dll @node.dll.rsp" 2 mt.exe rc.exe "obj\third_party\node-nw\node.node.dll.intermediate.manifest" obj\third_party\node-nw\node.node.dll.generated.manifest
lld-link: error: could not open '../nw/obj/buildtools/third_party/libc++/libcpp.lib': no such file or directory
lld-link: error: /failifmismatch: mismatch detected for 'RuntimeLibrary':
>>> obj\third_party\node-nw\src\node.tls_wrap.obj has value MTd_StaticDebug
>>> ../nw/obj/v8\v8_libplatform/trace-object.obj has value MDd_DynamicDebug
Traceback (most recent call last):
  File "gyp-win-tool", line 323, in <module>
    sys.exit(main(sys.argv[1:]))
  File "gyp-win-tool", line 29, in main
    exit_code = executor.Dispatch(args)
  File "gyp-win-tool", line 71, in Dispatch
    return getattr(self, method)(*args[1:])
  File "gyp-win-tool", line 179, in ExecLinkWithManifests
    subprocess.check_call(ldcmd + add_to_ld)
  File "f:\dev\depot_tools\bootstrap-2@3_8_10_chromium_26_bin\python\bin\lib\subprocess.py", line 190, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command 'f:\dev\depot_tools\bootstrap-2@3_8_10_chromium_26_bin\python\bin\python.exe gyp-win-tool link-wrapper environment.x64 False ..\..\third_party/llvm-build/Release+Asserts/bin/lld-link.exe /nologo /IMPLIB:node.dll.lib /DLL /OUT:node.dll @node.dll.rsp node.dll.manifest.res' returned non-zero exit status 1
ninja: build stopped: subcommand failed.

I also tried to call build manually like this:

f:\nwjs\src>autoninja -C out\nw libcpp
"f:\dev\depot_tools\bootstrap-2@3_8_10_chromium_26_bin\python3\bin\python3.exe" F:\dev\depot_tools\ninja.py -C out\nw libcpp -j 34
ninja: Entering directory `out\nw'
[2/2] LIB obj/buildtools/third_party/libc++/libcpp.lib

f:\nwjs\src>autoninja -C out\nw libc++
"f:\dev\depot_tools\bootstrap-2@3_8_10_chromium_26_bin\python3\bin\python3.exe" F:\dev\depot_tools\ninja.py -C out\nw libc++ -j 34
ninja: Entering directory `out\nw'
ninja: no work to do.

And it shows, that it does something, but doesn't generate any output file in case of libcpp.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the reported autoninja commands for libcpp and libc++ and the out\nw build paths, then inspect why libcpp.lib is not available to the node.dll link step. Reproduce the link and resolve the missing library and RuntimeLibrary mismatch; done means the build produces node.dll successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, javascript
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.