You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When #1195 prevented me from building my small image-using project with the bundled feature, I tried to link statically against the system libraries instead. Unfortunately, everything gets dynamically linked, as if static-link was never specified.
Using the following config:
[dependencies.sdl2]
version = "~0.35"default-features = falsefeatures = ["static-link", "use-pkgconfig", "image"]
The expected result is a binary with ~5 dependencies, which is what I get if I replace use-pkgconfig with bundled and commend out any use of the image feature.
However, running ldd on the binary built with the config shown above results in the following monstrosity:
This seems to be a regression, I have no idea from when though.
Even without image simply using cargo build --example demo --features use-pkgconfig,static-link links SDL2 dynamically, which is not the behavior expected:
valderman
changed the title
static-link feature seem to do anything without also specifying bundled (Linux)
static-link feature doesn't seem to do anything without also specifying bundled (Linux)
Jan 11, 2022
When #1195 prevented me from building my small
image
-using project with thebundled
feature, I tried to link statically against the system libraries instead. Unfortunately, everything gets dynamically linked, as ifstatic-link
was never specified.Using the following config:
The expected result is a binary with ~5 dependencies, which is what I get if I replace
use-pkgconfig
withbundled
and commend out any use of theimage
feature.However, running
ldd
on the binary built with the config shown above results in the following monstrosity:The text was updated successfully, but these errors were encountered: