-
Notifications
You must be signed in to change notification settings - Fork 20
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
SONAME Configuration & Versioning Policy #49
Comments
This is likely invalid. |
This is expected to only be loaded at runtime, what more is needed to address the warning? |
The only additional change would be if we move |
Yes, we need to move Per https://github.com/KhronosGroup/Vulkan-Loader/blob/main/docs/LoaderInterfaceArchitecture.md there is no prescribed location and everything is configuration driven. |
Pending evaluation of https://gitlab.freedesktop.org/monado/monado/-/blob/main/doc/packaging-notes.md this might not be needed. https://gitlab.freedesktop.org/monado/monado/-/merge_requests/2193 was rejected based on the proposed standard. |
I've confirmed that libopenxr_wivrn.so (an OpenXR Runtime) will remain unversioned and visible to the linker. I'm currently in a review for a Fedora packaging policy that encodes this decision. The only change that we'll need to make for WiVRn will be the file system location and how the new location is exposed the linker. I'll open a new issue once we get to that point. |
We need to configure proper soname's and versioning for downstream packaging policy compliance. The goal is to provide an ABI guarantee for any given soname. This can be accomplished by soname versioning or library symbol versioning. The simpler solution is likely the right one. Soname bumps are usually more involved and will require rebuilding all linked packages.
Fedora: https://docs.fedoraproject.org/en-US/packaging-guidelines/C_and_C++/
Debian: https://www.debian.org/doc/manuals/maint-guide/advanced.en.html#library
Based on the fedora-review tool, there is one soname that needs addressing:
Upstream Monado addressed this in https://gitlab.freedesktop.org/monado/monado/-/issues/335
The text was updated successfully, but these errors were encountered: