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
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
|
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
Wednesday, 30 September 2015, 19:44 GMT
Reason for closing: Duplicate
Additional comments about closing: See related
FS#43378. Normally a rebuild should fix it, otherwise please report back if that doesn't help.Is there any package that depends on vtk in the repos, or is it just to make vtk more "standard" in naming conventions?
FS#43378was 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.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.
Closing to continue discussion on the original task.
[1] https://cmake.org/Wiki/CMake:How_To_Find_Libraries#Piggybacking_on_pkg-config