Skip to content

pystring meson build system generates library with wrong soname #64

Description

@ametzler

When building with classic make system one gets:

ametzler@argenau:/tmp/PYSTRING$ objdump -p path/to/libpystring.so.0.0 | grep -i soname
  SONAME               libpystring.so.0

while the meson build creates

objdump -p path/to/libpystring.so.1.2.0  | grep -i soname
  SONAME               libpystring.so.1

For debian we are using this patch by Sébastien Noel to fix this:

Description: Set the library version to "0.0.0", the same as it used to be
 when using the handwritten Makefile

--- a/meson.build
+++ b/meson.build
@@ -37,7 +37,7 @@
         srcs,
         implicit_include_directories: false,
         include_directories: inc,
-        version: meson.project_version(),
+        version: '0.0.0',
         install: true,
     )

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions