PCLConfig.cmake fails to find pcl due to usrmerge
Bug #1896118 reported by
Lucas D. Cagle
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pcl (Debian) |
Fix Released
|
Unknown
|
|||
pcl (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
1) 20.04 LTS
2) 1.10.0+
3) cmake's find_package() finds pcl for project build
4) cmake's find_package() fails to find pcl
On fresh installs of 20.04, /lib is symlinked to /usr/lib by default. This seems to cause problems with the relative paths used at line 401 in PCLConfig.cmake.in to set PCL_ROOT. cmake seems to be searching /lib first for the cmake config files. This causes the relative path used in line 401 to resolve to / instead of the intended /usr, which then cause subsequent lines to fail to find pcl.
For full disclosure, I encountered this while using a Singularity container, but I am largely confident this isn't a container-specific issue.
Changed in pcl (Debian): | |
status: | Unknown → Fix Released |
To post a comment you must log in.
I failed to reproduce this using:
1. Fresh installed 20.4
2. sudo apt install g++ cmake libpcl-dev
3. echo "find_package(PCL)" > CMakeLists.txt
4- cmake .
Can you try it again and maybe post your CMakeCache.txt?