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

Missing file libopen62541.so for debian linking #6485

Closed
3 tasks done
keba-estr opened this issue May 17, 2024 · 4 comments
Closed
3 tasks done

Missing file libopen62541.so for debian linking #6485

keba-estr opened this issue May 17, 2024 · 4 comments

Comments

@keba-estr
Copy link
Contributor

Description

The file lobopen62541.so has been removed from the libopen62541-dev package with commit 9e0b766.
The argument was that the so file is already available in the libopen62541 package.
But the name of the so file in the libopen62541 package is libopen62541.so.1, and the linker only looks for files with the extension .so.

Checklist

Please provide the following information:

  • open62541 Version (release number or git tag): 1.4
  • Operating system: Linux (debian)
  • Critical issue
@keba-estr
Copy link
Contributor Author

keba-estr commented May 17, 2024

The correct solution is adding the so file to the dev package (again).
If the SO_VERSION is increased due to imcompatiblity, the library containing an so-file would not be installable in parallel with different versions.

@keba-estr
Copy link
Contributor Author

Created PR #6486

@jpfr
Copy link
Member

jpfr commented May 19, 2024

The Debian package generated on my box generates both the .so.1 and also a symbolic link to the .so.

Maybe you generate packages differently.
I use ./tools/prepare_packaging.py and then ‘debuild’ from the source root folder.

@keba-estr
Copy link
Contributor Author

The Debian package generated on my box generates both the .so.1 and also a symbolic link to the .so.

Maybe you generate packages differently. I use ./tools/prepare_packaging.py and then ‘debuild’ from the source root folder.

I also use ./tools/prepare_packaging.py, but then I use a KEBA specific function 'buildpackage'.
So I will have to handle the topic within my KEBA specific build part.

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

No branches or pull requests

2 participants