Skip to content
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

Allow dynamically linking libvulkan.so #2809

Closed
SDLBugzilla opened this issue Feb 11, 2021 · 0 comments
Closed

Allow dynamically linking libvulkan.so #2809

SDLBugzilla opened this issue Feb 11, 2021 · 0 comments
Labels
abandoned Bug has been abandoned for various reasons

Comments

@SDLBugzilla
Copy link
Collaborator

This bug report was migrated from our old Bugzilla tracker.

Reported in version: HG 2.1
Reported for operating system, platform: Linux, x86_64

Comments on the original bug report:

On 2018-01-22 09:56:38 +0000, Niklas Haas wrote:

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.

On 2018-01-22 10:39:41 +0000, Niklas Haas wrote:

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?

On 2018-01-24 01:01:29 +0000, Sam Lantinga wrote:

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.

On 2018-08-06 21:20:19 +0000, Ryan C. Gordon wrote:

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.

@SDLBugzilla SDLBugzilla added abandoned Bug has been abandoned for various reasons bug labels Feb 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
abandoned Bug has been abandoned for various reasons
Projects
None yet
Development

No branches or pull requests

1 participant