FS#43378 - [vtk] Libraries end with version number, not according to convention
Attached to Project:
Community Packages
Opened by Ng Oon-Ee (ngoonee) - Thursday, 08 January 2015, 08:57 GMT
Last edited by Bruno Pagani (ArchangeGabriel) - Wednesday, 21 July 2021, 22:46 GMT
Opened by Ng Oon-Ee (ngoonee) - Thursday, 08 January 2015, 08:57 GMT
Last edited by Bruno Pagani (ArchangeGabriel) - Wednesday, 21 July 2021, 22:46 GMT
|
Details
Description:
Current vtk package is full of libraries like /usr/lib/libvtkalglib-6.1.so. etc. This disallows linking vtk using -lvtkalglib as is common practice. Using -lvtkalglib-6.1 is a workaround but a slight hindrance when working between distros and OS. Debian, at least, uses the (IMHO) more sane /usr/lib/libvtkalglib.so.6.1 naming, as do most other libraries I'm aware off. Additional info: * package version(s) vtk-6.1.0-7 |
This task depends upon
Closed by Bruno Pagani (ArchangeGabriel)
Wednesday, 21 July 2021, 22:46 GMT
Reason for closing: Fixed
Additional comments about closing: Seems this was fixed long ago.
Wednesday, 21 July 2021, 22:46 GMT
Reason for closing: Fixed
Additional comments about closing: Seems this was fixed long ago.
Purely a gripe, this one wouldn't make as much of a difference as library naming.
If Andrzej doesn't get to it I'll make sure to see that the build sticks to upstream defaults, and if anything is out of the ordinary, we will be sure to file a ticket upstream and amend our build as necessary.
This one looks rather easily solvable but I'll prefer to update this along with or after the other less trivial vtk tickets have been resolved. Also, I think this is worthy of an upstream nudge.
Thanks for your continued support in testing this package!
EDIT: ah my bad, misread the messages. It was my pcl compile which hadn't been recompiled when I changed the library names. Ignore this message.
EDIT2: just an additional point to note that -DVTK_INSTALL_INCLUDE_DIR:PATH=include/vtk puts the headers in /usr/include/vtk.
https://packages.debian.org/jessie/amd64/libvtk6.1/filelist
@Ng and @Alex, any opinions in light of what Antonio has brought up? See
FS#46431.$ pacman -Ql vtk | grep libvtkalglib
vtk /usr/lib/libvtkalglib.so
vtk /usr/lib/libvtkalglib.so.1
vanilla vtk uses library version in library names and downstream software expects to find them.
I say that if downstream software cannot find the proper libs, then either the downstream or upstream build system is fundamentally broken. In most cases pkg-config (whether by itself or via cmake) does a fine job.
The hack here could be reverted and a general complaint filed upstream, or the build could be made to yield /usr/lib/libvtkalglib.so.6.1 naming (whether or not that requires a hack), which I believe would be much better.
I leave this up to Anatol now.
that way any downstream software that wants to use vtk should adapt.