-
Notifications
You must be signed in to change notification settings - Fork 0
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
Shared libs instead of static? #5
Comments
OS X and 64-bit linux were both built with static libs to build the JNI. Shared libs for the native libraries makes more sense, though. Thanks for pointing that out; I'm not too familiar with C++ |
The JNI .so should be able to depend on the native .so files as well. Doing so will substantially reduce the JNI .so file size. |
Although maybe on Windows we need to use static libs since C++ DLLs are somewhat broken? I guess it's okay for all desktop stuff to be static since we don't care about file sizes, just make the arm stuff dynamic? |
That would certainly make the build process easier |
Currently at least the linux64 package contains static libraries; I've not checked the rest. I think the plan is to use shared libs instead, particularly on the roborio, to reduce user program size.
The text was updated successfully, but these errors were encountered: