Skip to content

[XPTIFW][CMake] Set SONAME to the library major version (#23031) - #23058

Merged
KornevNikita merged 1 commit into
sycl-rel-7_1from
cp-9dbd3e7e0d2de09053ae104fbb3b82c61da75c00
Aug 31, 2026
Merged

[XPTIFW][CMake] Set SONAME to the library major version (#23031)#23058
KornevNikita merged 1 commit into
sycl-rel-7_1from
cp-9dbd3e7e0d2de09053ae104fbb3b82c61da75c00

Conversation

@KornevNikita

Copy link
Copy Markdown
Contributor

xptifw sets only the library VERSION (1.0.1) and no SOVERSION, so the generated SONAME is libxptifw.so.1.0.1. This churns the SONAME on every point release, forcing needless rebuilds of consumers that link against libxptifw, and it does not follow the usual shared-library convention.

Set SOVERSION to the project major version so the SONAME becomes libxptifw.so.1, which stays stable across the 1.x series.

This is something I ran into while packaging v7.0.0 of the compiler for Ubuntu 26.10. I have this change in a patch for the packaging but wanted to go ahead and contribute it so ideally we don't need to maintain the patch for future releases.

cc @dvrogozh @sarnex


cherry-pick: 9dbd3e7

xptifw sets only the library VERSION (1.0.1) and no SOVERSION, so the
generated SONAME is libxptifw.so.1.0.1. This churns the SONAME on every
point release, forcing needless rebuilds of consumers that link against
libxptifw, and it does not follow the usual shared-library convention.

Set SOVERSION to the project major version so the SONAME becomes
libxptifw.so.1, which stays stable across the 1.x series.

This is something I ran into while packaging v7.0.0 of the compiler for
Ubuntu 26.10. I have this change in a patch for the packaging but wanted
to go ahead and contribute it so ideally we don't need to maintain the
patch for future releases.

cc @dvrogozh @sarnex
@KornevNikita

Copy link
Copy Markdown
Contributor Author

@KornevNikita
KornevNikita merged commit 880399f into sycl-rel-7_1 Aug 31, 2026
35 of 39 checks passed
@KornevNikita
KornevNikita deleted the cp-9dbd3e7e0d2de09053ae104fbb3b82c61da75c00 branch August 31, 2026 12:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants