when CSparse is not installed in one of the locations hardcoded in the PATHS argument of find_path. For example, it would also fail if you compiled suitesparse inside a colcon workspace instead of installing it from binary .deb packages.
CMake's find_path offers the PATH_SUFFIXES option (already available in CMake 3.5 https://cmake.org/cmake/help/v3.5/command/find_path.html, minimum required version for this package). In theory we could remove the other arguments passed to PATHS, but as they do not hurt and leaving them minimize the risk of regressions, I think we can leave them.
Basic Info
Description of contribution in a few bullet points
The current version of
find_package(CSparse)
can fail with error:when CSparse is not installed in one of the locations hardcoded in the
PATHS
argument offind_path
. For example, it would also fail if you compiled suitesparse inside a colcon workspace instead of installing it from binary .deb packages.CMake's
find_path
offers thePATH_SUFFIXES
option (already available in CMake 3.5 https://cmake.org/cmake/help/v3.5/command/find_path.html, minimum required version for this package). In theory we could remove the other arguments passed toPATHS
, but as they do not hurt and leaving them minimize the risk of regressions, I think we can leave them.A similar fix done in g2o: https://github.com/RainerKuemmerle/g2o/commit/4f092a43e5214b979f9eca221f0f6f62781c2d5d .
Description of documentation updates required from your changes
Future work that may be required in bullet points