| Summary: | sci-libs/ceres-solver-1.12.0 - CMake Error at CMakeModules/AddLibMacros.cmake:420 (find_package): Found package configuration file: /usr/lib64/cmake/Ceres/CeresConfig.cmake but it set Ceres_FOUND to FALSE so package "Ceres" is considered to be NOT FOUND. | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | kavol |
| Component: | Current packages | Assignee: | Gentoo Science Related Packages <sci> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | Keywords: | PATCH |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Is this still a problem in 1.14.0? upstream bug tracker: https://gitlab.kitware.com/cmake/cmake/-/issues I can't reproduce this with 1.14.0 so I'm going to close |
Trying to compile a project depending on ceres, I'm getting the following error: CMake Error at CMakeModules/AddLibMacros.cmake:420 (find_package): Found package configuration file: /usr/lib64/cmake/Ceres/CeresConfig.cmake but it set Ceres_FOUND to FALSE so package "Ceres" is considered to be NOT FOUND. Simply adding this variable makes it go away: --- CeresConfig.cmake~ 2019-11-17 10:59:35.202103311 +0100 +++ /usr/lib64/cmake/Ceres/CeresConfig.cmake 2019-11-17 10:59:54.007102035 +0100 @@ -392,3 +392,4 @@ # Ceres_FOUND is not (explicitly, i.e. undefined does not count) set # to FALSE. set(CERES_FOUND TRUE) +set(Ceres_FOUND TRUE) Reproducible: Always This should probably go to upstream, however I can't find any upstream issue tracker ... BTW, looks like the authors of the project I'm trying to compile are aware about the issue, there is some code trying to make Ceres_FOUND and CERES_FOUND equivalent, however the code is obviously after FindPackage call, and as the package is REQUIRED, cmake bails out in FindPackage before it even reaches that code. So, might be also cmake issue, that it changed behaviour, but I'm no cmake expert ... after all, it might be better to report downstream, to have another pair of eyes to take a look where the problem lies, whether my patch isn't touching something completely different than what should be fixed ...