nodejs / nodejs/node-gyp

’libraries‘ config not used when compile source files

Open
#2,535 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

ERR! node-gyp -v < v10.x.x macOS
Dominant language
Python
Stars
10.7k
Forks
1.9k
Avg merge
1d 4h
Merged PRs (30d)
5

Description

  • Node Version: npm(6.14.13) node(v14.17.6)
  • Platform: macOS Big Sur 11.6.1
  • Compiler: Apple clang version 13.0.0 (clang-1300.0.29.3)

I set this in binding.gpy

"libraries": [
   '-F/Users/plum/Desktop/addon/lib/ -framework Plum2',
 ],

but it not used when compile source file.

this is complile log

node-gyp rebuild --debug -v

c++ '-DNODE_GYP_MODULE_NAME=hello' '-DUSING_UV_SHARED=1' '-DUSING_V8_SHARED=1' '-DV8_DEPRECATION_WARNINGS=1' '-DV8_DEPRECATION_WARNINGS' '-DV8_IMMINENT_DEPRECATION_WARNINGS' '-D_DARWIN_USE_64_BIT_INODE=1' '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-DOPENSSL_NO_PINSHARED' '-DOPENSSL_THREADS' '-DNAPI_DISABLE_CPP_EXCEPTIONS' '-DBUILDING_NODE_EXTENSION' '-DDEBUG' '-D_DEBUG' '-DV8_ENABLE_CHECKS' -I/Users/plum/Library/Caches/node-gyp/14.17.6/include/node -I/Users/plum/Library/Caches/node-gyp/14.17.6/src -I/Users/plum/Library/Caches/node-gyp/14.17.6/deps/openssl/config -I/Users/plum/Library/Caches/node-gyp/14.17.6/deps/openssl/openssl/include -I/Users/plum/Library/Caches/node-gyp/14.17.6/deps/uv/include -I/Users/plum/Library/Caches/node-gyp/14.17.6/deps/zlib -I/Users/plum/Library/Caches/node-gyp/14.17.6/deps/v8/include -I../node_modules/node-addon-api -I/Users/plum/Desktop/addon/lib/Plum2.framework -O0 -gdwarf-2 -mmacosx-version-min=10.13 -arch x86_64 -Wall -Wendif-labels -W -Wno-unused-parameter -std=gnu++1y -stdlib=libc++ -fno-rtti -fno-exceptions -fno-strict-aliasing -MMD -MF ./Debug/.deps/Debug/obj.target/hello/src/hello.o.d.raw -c -o Debug/obj.target/hello/src/hello.o ../src/hello.cc

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 binding.gpy and the node-gyp rebuild --debug -v output, comparing the generated compile and link commands. Trace how the libraries setting is handled for source compilation, then verify that the configured framework reaches the appropriate build step without breaking the addon build.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, nodejs, python
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.