| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
Hello,
what is the easiest way to use the current experimental version of the PCL together with ROS Fuerte (which includes PCL 1.5 by default)? There are some features I would like to use which aren't available in version 1.5.
I found this directory but I don't know what these files are for, since there is no official PCL 1.5.2.
Thanks in advance!
Fuerte uses pcl 1.5 as default. This link in mailing list could be of help: http://code.ros.org/lurker/message/20120618.220556.be95ed89.en.html
Your question is answered by Bhaskara. I am reproducing it here
We've been using pcl trunk with fuerte:
https://bitbucket.org/bhaskara/perception_pcl_fuerte_unstable
It puts the pcl trunk code into a 'pcl16' namespace, so that it can
coexist with fuerte's pcl 1.5. Using it basically involves replacing
the pcl and pcl_ros namespaces with pcl16 and pcl16_ros respectively.
- Bhaskara
Thank you! How does this work? I cloned the git repository, but it doesn't contain the PCL trunk code, so I assume I have to merge them somehow. But how can this package change the c++ namespace to "pcl16" if it does not even contain the (modified) pcl header files?
I used "hg clone https://bitbucket.org/bhaskara/perception_pcl_fuerte_unstable", but I doesn't actually contain the pcl header and source files, so I think I have to get these from http://svn.pointclouds.org/pcl/trunk and merge them with perception_pcl_fuerte_unstable in some way!?
I did exactly what you said, but unfortunately when it comes to executing pcl16/Makefile, I get "CMake Error: The source directory "~/workspace/perception_pcl_fuerte_unstable/pcl16/build/pcl_trunk" does not appear to contain CMakeLists.txt". Apparently, the pcl trunk is not checked out at all. :(
Thanks! The build dir in pcl16 had to be deleted in order for the respective makefile target to be executed. Thank you for fixing this :) Just one further question: What would be the best way to upgrade to a new trunk? Just change the revision in the Makefile and recompile or to do a fresh install?
I don't believe changing the revision will trigger a new build. You'll have to do an rm -rf build in the pcl16 directory as well. It would be nice to be able to svn update pcl and just remake the changed bits, but the problem is that we're patching pretty much all the files after checking them out.
Asked: 2012-06-19 10:03:25 -0500
Seen: 1,329 times
Last updated: Jun 19 '12
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.