-
Notifications
You must be signed in to change notification settings - Fork 42
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
Statically linking SDL2 at compile time, rather than dynamically loading it at runtime #327
Comments
This is probably impossible, because they both want to define symbols of the same name with different meanings. Shared libraries can do this if you're very, very careful; static libraries can't. |
This will probably also never work, unless you rename all SDL3 symbols such that they do not conflict with SDL2. Is there a way to change all symbol names in a static archive? |
Not for sdl12-compat, but for sdl2-compat I just managed to link a sdl2 project to a static sdl2-compat and static SDL3.
It goes without saying that this configuration is 100% unsupported. |
Is it possible to add an option for statically linking SDL2 directly into the program, along with sdl12-compat, instead of having to dynamically load SDL2 at runtime?.. That means both sdl12-compat and SDL2 are built as static libraries.
Thank you.
The text was updated successfully, but these errors were encountered: