-
Notifications
You must be signed in to change notification settings - Fork 37
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
Question: How to build lzma as a static library #101
Comments
I may have jumped the gun, for some reason I didn't see the |
I attempted to set
I suspect this should be the right way to have node-gype build the library statically, but the compilation warning is a blocker. I'll continue debugging. |
@baparham Can I ask why the compilation warning is a blocker? In any case, if it is, then I’m not sure how to help with that particular problem (the code in question was lifted from the libzma library itself) |
It seems to stop node-gyp from compiling. If I initialize I've began to explore other ways of meeting my requirements without a statically compiled lzma, but I think this still would be nice to get figured out. |
@baparham Yeah, it’s a warning, not an error, it shouldn’t affect the compilation process. If you can give me exact steps to reproduce what you’re running into, I’m happy to help, but I don’t think the information here is actionable right now. |
Do you have any documentation or advice on how I might rebuild lzma-native with node-gyp but as a static library?
It seems to me, at some basic digging, that I'd need to update
"libraries: ['-llzma']
in thebinding.gyp
file to point to a full path to the lzma.a library, but I am having trouble determining where that might be.Thanks for the help!
The text was updated successfully, but these errors were encountered: