napi-bindings/node-api-stub

Node-API stub

node-api-stub's Issues

Refactor for the stub.

Use the features provided by node-api-headers (https://github.com/nodejs/node-api-headers) and do a refactor for the stub.

List of steps to create the builder

The Go backend compiler needs the N-API stub to compile the add-on otherwise it arise a linker error. In this case on the folder napi-stub there is a stub used in experimentation phase, but now the stub needs to be generated in a dynamic way.
The following are the necessary tasks:

• Get the platform / OS on which node is in execution
• Get the Node.js version
• Get the N-API version. See: https://github.com/inspiredware/napi-build-utils
• Generate all the headers files for N-API based on its version

See: This issue is correlated with napi-bindings/go-napi-sys#5

Undefined symbols napi_module_register

Trying to compile using the stub the following error happens:

[ 50%] Linking CXX shared library addon.node
Undefined symbols for architecture x86_64:
  "_napi_module_register", referenced from:
      _register_addon() in addon.cc.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[3]: *** [addon.node] Error 1
make[2]: *** [CMakeFiles/addon.dir/all] Error 2
make[1]: *** [CMakeFiles/addon.dir/rule] Error 2
make: *** [addon] Error 2