-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bind vg library with node.js nbind - how to set library and linking parameters in binding.gyp? #540
Comments
You compiler's complaining it can't find vg.hpp. You can fix this with the https://github.com/glennhickey/ultrabubble_eval (which relies on the VGDIR variable hardcoded in the Makefile). On Thu, Nov 10, 2016 at 11:05 AM, subwaystation notifications@github.com
|
In addition to copying libvg.a, a proper global install will need all the *.hpp files under Unfortunately, in vg we have a bad habit of referring to our includes from dependencies without qualifying paths. So maybe you want to just dump them all into |
The issue has been solved, for a short tutorial see here: charto/nbind#35 |
Hi
vg
team,at the moment I am trying to build a JavaScript wrapper around your C++ library using https://github.com/charto/nbind.
However, I ran into some issues, see here https://github.com/charto/nbind/issues/35.
So at the moment I am stuck at the compilation step
npm run -- node-gyp configure build
. The problem is that thevg.hpp
is not found:Here is my source file from which I want to invoke
vg
:And here my
binding.gyp
file:I tried putting
libvg.a
into the directory where I am building the stuff. Then I copiedlibvg.a
into/usr/lib/libvg.a
. All of this is not working. How do I have to set the compiler flags and the library stuff in order to compile it? Please help me out here.For
node-gyp
see:https://github.com/nodejs/node-gyp
https://gyp.gsrc.io/docs/InputFormatReference.md
https://gyp.gsrc.io/docs/UserDocumentation.md
https://github.com/nodejs/node-gyp/wiki/"binding.gyp"-files-out-in-the-wild
All the best.
The text was updated successfully, but these errors were encountered: