Revision history [back]

Have you recompiled all pkgs that depend on PCL (pcl_conversions, pcl_ros, etc) from source using your custom PCL version (in /usr/local)? If not, it could be your mixing PCL 1.7 with 1.8.x lib sets.

Have you recompiled all pkgs that depend on PCL (pcl_conversions, pcl_ros, etc) from source using your custom PCL version (in /usr/local)? If not, it could be your mixing PCL 1.7 with 1.8.x lib sets.

Have you recompiled all pkgs that depend on PCL (pcl_conversions, pcl_ros, etc) from source using your custom PCL version (in /usr/local/home/baxterpc/Tools/pcl/release)? If not, it could be your mixing PCL 1.7 with 1.8.x lib sets.

No. I haven't. Can you please tell me the steps to recompiled all packages that depend on PCL?

The most fool-proof method I know is:

1. deinstall all packages that depend on libpcl-1.7-all and all libpcl-*-1.7 packages themselves (removing libpcl-1.7-all will probably already take those pkgs with it)
2. create a catkin workspace (or reuse what you already have), clone the perception_pcl repository in it
3. make sure to install all dependencies (but make sure to ask rosdep to ignore the libpcl-all-dev dependency (as it will try to make apt install v1.7, which we don't want)
4. build the workspace (regular catkin_make or catkin build)

If you have any packages you deinstalled in step 1 but do still want/need, you'll have to build those from source in your catkin workspace as well (as all binary pkgs will try to use PCL 1.7).

See also #q252478 for the general workflow for building pkgs from sources.

Have you recompiled all pkgs that depend on PCL (pcl_conversions, pcl_ros, etc) from source using your custom PCL version (in /home/baxterpc/Tools/pcl/release)? If not, it could be your mixing PCL 1.7 with 1.8.x lib sets.

No. I haven't. Can you please tell me the steps to recompiled all packages that depend on PCL?

The most fool-proof method I know is:

1. deinstall all packages that depend on libpcl-1.7-all and all libpcl-*-1.7 packages themselves (removing libpcl-1.7-all will probably already take those pkgs with it)
2. create a catkin workspace (or reuse what you already have), clone the perception_pcl repository in it
3. make sure to install all dependencies (but make sure to ask rosdep to ignore the libpcl-all-dev dependency (as it will try to make apt install v1.7, which we don't want)
4. build the workspace (regular catkin_make or catkin build)

If you have any packages you deinstalled in step 1 but do still want/need, you'll have to build those from source in your catkin workspace as well (as all binary pkgs will try to use PCL 1.7).

See also #q252478 for the general workflow for building pkgs from sources.

Have you recompiled all pkgs that depend on PCL (pcl_conversions, pcl_ros, etc) from source using your custom PCL version (in /home/baxterpc/Tools/pcl/release)? If not, it could be your mixing PCL 1.7 with 1.8.x lib sets.

No. I haven't. Can you please tell me the steps to recompiled all packages that depend on PCL?

The most fool-proof method I know is:

1. deinstall all packages that depend on libpcl-1.7-all and all libpcl-*-1.7 packages themselves (removing libpcl-1.7-all will probably already take those pkgs with it)
2. create a catkin workspace (or reuse what you already have), clone the perception_pcl repository in it
3. make sure to install all dependencies (but make sure to ask rosdep to ignore the libpcl-all-dev dependency (as it will try to make apt install v1.7, which we don't want)
4. build the workspace (regular catkin_make or catkin build)

If you have any packages you deinstalled in step 1 but do still want/need, you'll have to build those from source in your catkin workspace as well (as all binary pkgs will try to use PCL 1.7).

See also #q252478 for the general workflow for building pkgs from sources.

Note that you'll have to make sure that /home/baxterpc/Tools/pcl/release is on the library/pkg search path, or you'll get errors on step 4, as no PCL can be found.