-
Notifications
You must be signed in to change notification settings - Fork 66
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
Support for static library build #95
Comments
On windows this should produce static library. Are you having troubles with this kind of build? |
No that doesn't work because to build static libs CMakeLists.txt will have to be updated to support building static libraries only. |
Now I see. |
@hs-apotell one small thing, doy you want a static build for windows or linux? What I am trying to ask is if you actually need a static build so your users do not have to care about an extra lib or it is because there is no package in any public repo for C library and the more correct solution is to make a apt,conda, etc package. |
We are building for Windows, Linux (multiple different flavors) and Mac, so we need for all these platforms. That said, I don't expect you to support all these platforms. If one is supported we can port for others. It's basically just a way to ensure this particular configuration is validated and tested in your release cycle. We plan on linking it always as a static library to avoid dynamic library nightmares. Also, we use custom memory management and that's a whole lot more maintenance when dealing with dynamic modules. Also, we will always build it our self because of the number of different platforms we have to support and so release packages are not very attractive for our use case. |
Add support for static library build - for use in native tools without bringing in python dependency.
The text was updated successfully, but these errors were encountered: