We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In release 3.6, with -DSLEEF_BUILD_GNUABI_LIBS:BOOL=TRUE, CMake no longer produces the unversioned shared-library symlink libsleefgnuabi.so.
-DSLEEF_BUILD_GNUABI_LIBS:BOOL=TRUE
libsleefgnuabi.so
Only the library libsleefgnuabi.so.3.6 and the symbolic link libsleefgnuabi.so.3 are installed.
libsleefgnuabi.so.3.6
libsleefgnuabi.so.3
(See https://sleef.org/additional.xhtml#gnuabi for an example using -lsleefgnuabi: this requires libsleefgnuabi.so.)
-lsleefgnuabi
Both libsleef.so and libsleefquad.so have the correct unversioned symbolic links.
libsleef.so
libsleefquad.so
The text was updated successfully, but these errors were encountered:
It looks like 29391cc might affect this, but I haven’t tested it yet.
Sorry, something went wrong.
Thanks for the report. Will look into that as soon as I can.
You are right, it very well could solve that. But not 100% sure, haven't checked more closely yet.
It affects it, but the wrong way: now libsleef.so is also missing the unversioned symlink!
Note that libsleef.so/libsleefgnuabi.so are in the CMake build directory, but they are not installed anymore.
Successfully merging a pull request may close this issue.
In release 3.6, with
-DSLEEF_BUILD_GNUABI_LIBS:BOOL=TRUE
, CMake no longer produces the unversioned shared-library symlinklibsleefgnuabi.so
.Only the library
libsleefgnuabi.so.3.6
and the symbolic linklibsleefgnuabi.so.3
are installed.(See https://sleef.org/additional.xhtml#gnuabi for an example using
-lsleefgnuabi
: this requireslibsleefgnuabi.so
.)Both
libsleef.so
andlibsleefquad.so
have the correct unversioned symbolic links.The text was updated successfully, but these errors were encountered: