We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 4061

Summary: Allow dynamically linking libvulkan.so
Product: SDL Reporter: Niklas Haas <sdl>
Component: videoAssignee: Sam Lantinga <slouken>
Status: RESOLVED ABANDONED QA Contact: Sam Lantinga <slouken>
Severity: normal    
Priority: P2 CC: chewi
Version: HG 2.1   
Hardware: x86_64   
OS: Linux   

Description Niklas Haas 2018-01-22 09:56:38 UTC
Instead of loading vulkan.so at runtime (which requires LOADSO support), it would be perfectly reasonable to link against libvulkan.so at compile time.

Would it be possible to add support for such a configuration? I don't see any reason to require loading it at runtime - it's not like dlopen() is going to be doing anything different than the platform's built-in loader, except possibly less securely so.
Comment 1 Niklas Haas 2018-01-22 10:39:41 UTC
Incidentally, while investing this further, I noticed the same scenario is the case for libGL.so - again, it doesn't really make sense to load this using dlopen at runtime. Can you add an option to link it at compile time?
Comment 2 Sam Lantinga 2018-01-24 01:01:29 UTC
We typically dynamically load all shared libraries at runtime, this allows us to ship SDL on a platform where some functionality may not be available, without rebuilding it. The LOADSO support is available on every platform SDL supports.

I'm not opposed to a patch that optionally links those libraries, however.
Comment 3 Ryan C. Gordon 2018-08-06 21:20:19 UTC
Hello, and sorry if you're getting dozens of copies of this message by email.

We are closing out bugs that appear to be abandoned in some form. This can happen for lots of reasons: we couldn't reproduce it, conversation faded out, the bug was noted as fixed in a comment but we forgot to mark it resolved, the report is good but the fix is impractical, we fixed it a long time ago without realizing there was an associated report, etc.

Individually, any of these bugs might have a better resolution (such as WONTFIX or WORKSFORME or INVALID) but we've added a new resolution of ABANDONED to make this easily searchable and make it clear that it's not necessarily unreasonable to revive a given bug report.

So if this bug is still a going concern and you feel it should still be open: please feel free to reopen it! But unless you respond, we'd like to consider these bugs closed, as many of them are several years old and overwhelming our ability to prioritize recent issues.

(please note that hundred of bug reports were sorted through here, so we apologize for any human error. Just reopen the bug in that case!)

Thanks,
--ryan.