jkammerl / pcl-unstable-release

ROS unstable release of pcl trunk
0 stars 1 forks source link

Make it work with ROS Groovy #1

Open kalectro opened 11 years ago

kalectro commented 11 years ago

I started off by forking this repo and fixing things to make it compile with groovy. Unfortunately I got the bright idea to change its name and remove all but one branch, so I was not able to issue a pull request. I wanted to create this issue for other people looking for pcl unstable in groovy which seems to work fine now. You can find the repo here https://github.com/kalectro/pcl_groovy

jkammerl commented 11 years ago

Thanks a lot Kai!

There is one important step missing. In order to enable the coexistence of ros-groovy-pcl and ros-groovy-pcl-unstable, all header needs to be installed in a separate folder and all libs needs to have an 1.6.1 extension. I'll look into this asap. It would be great to release pcl-unstable in near future.

kalectro commented 11 years ago

Julius,

I hope someone has a script for renaming everything. Since I am working on an ARM architecture, I do not care about binaries too much. I just installed ROS from source by removing the 1.6.0 package from the src folder and replaced it with my own. I will add a note saying that it is not meant to be used in combination with the other PCL, thanks for the heads up.

jkammerl commented 11 years ago

Hi Kai,

I just patched PCL trunk to fix the USE_ROS option within groovy. This way, no extra patches will be needed (only an additional package.xml and USE_ROS=ON flag). I don't think that we have to rename the namespace since it will be installed under pcl 1.7 anyways.

I'll update this repository to the current trunk shortly.

Best, Julius

kalectro commented 11 years ago

if you name the package pcl_1.7 in the package.xml file and the CMakeLists.txt this should work. If not you will not be able to install it next to the stable release (1.6)

bbferka commented 11 years ago

Hi,

I am just wondering, in the end, is there a way of using the latest pcl with groovy?...even if this means having package names like pcl16 or pcl17 like the ones in fuerte?

Cheers, Ferenc