node-gyp Unresolved Sxternal Symbol Error
See original GitHub issueI’m trying to make a native module that uses DirectX for some of it’s functionality, but I get this error when I try to node-gyp build
:
main.obj : error LNK2001: unresolved external symbol Direct3DCreate9
I’m including d3d9.h in my c++ file. Is there something I’m doing wrong?
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
node-gyp build gives unresolved external symbol error
1 Answer 1 ... GYP is a meta-build system that generates files for various build systems, MSBuild, in your case. In your case,...
Read more >node-gyp LNK2001: unresolved external symbol #1788 - GitHub
I have a static library that I want to link against in a native node addon. I've created a minimum example to showcase...
Read more >Unresolved symbols when compiling native node module ...
I'm trying to create an application with node-webkit that has also to call some Julia code. However, when trying to compile the module...
Read more >Linker Tools Error LNK2001 - Microsoft Learn
The compiled code makes a reference or call to symbol. The symbol isn't defined in any libraries or object files searched by the...
Read more >How to use a static library with node-gyp on Windows?-C++
However, node-gyp uses the Microsoft C and C++ (MSVC) runtime libraries. ... in this question (i.e., error LNK2001: unresolved external symbol ).
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
https://github.com/nodejs/help/issues - but if it’s an issue with a specific module, people should report it there.
As @bnoordhuis suggested, since this is a “usage” problem and not a direct bug in
node-gyp
, open an issue there and I’ll give you some tips[Reasoning] This is not just a whim, on the one hand we want this issue board to reflect actual “bugs” in
node-gyp
, and on the other hand we wantnodejs/help
to be the knowledge base for “how to use” the products in the nodejs org.