FS#46431 - [vtk] 6.1.0-10 changes install location for includes and libs

Attached to Project: Community Packages
Opened by Antonio Cervone (capitalaslash) - Friday, 25 September 2015, 07:55 GMT
Last edited by Ray Rashif (schivmeister) - Wednesday, 30 September 2015, 19:44 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Ray Rashif (schivmeister)
Anatol Pomozov (anatolik)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The latest build explicitly changes the installation paths for includes and libraries.
Several packages (outside arch repos, such as petsc, libmesh) are no more able to properly find the modified locations.
Is there a reason for this change?
This task depends upon

Closed by  Ray Rashif (schivmeister)
Wednesday, 30 September 2015, 19:44 GMT
Reason for closing:  Duplicate
Additional comments about closing:  See related  FS#43378 
Comment by Ray Rashif (schivmeister) - Friday, 25 September 2015, 18:15 GMT
Yes, see  FS#43378 . Normally a rebuild should fix it, otherwise please report back if that doesn't help.
Comment by Antonio Cervone (capitalaslash) - Wednesday, 30 September 2015, 09:38 GMT
Unfortunately the packages search for the libvtkxxx-6.1 form, since that is the one generated from the vanilla package.
Is there any package that depends on vtk in the repos, or is it just to make vtk more "standard" in naming conventions?
Comment by Ray Rashif (schivmeister) - Wednesday, 30 September 2015, 13:28 GMT
Yes, that is a problem. Normally, search for libs are facilitated by a tool, and in most cases this tool is pkg-config.  FS#43378  was closed without much testing, so please reopen it with the details of any package that does not succeed in building. It was to make vtk follow standard conventions. There is not yet any package in the repos that depend on it, but there will be.
Comment by Antonio Cervone (capitalaslash) - Wednesday, 30 September 2015, 14:09 GMT
vtk does not offer a pc file, it is based on cmake.
the other packages that would build on vtk are not in the repos, and they are based on autotools with custom m4 files that recognize only vtk standard intsallation.
I will post in the other bug report, thanks.
Comment by Ray Rashif (schivmeister) - Wednesday, 30 September 2015, 19:42 GMT
It is up to a developer to ensure they find the proper libraries in the right way. For CMake, there' some documentation. [1] VTK itself may not provide a pc file, in which case either VTK upstream or the library/tool using it should take a look at how this can be done right.

Closing to continue discussion on the original task.

[1] https://cmake.org/Wiki/CMake:How_To_Find_Libraries#Piggybacking_on_pkg-config

Loading...