[ros-users] RTT_COMPONENT_PATH in ROS debs

Jeremy Leibs leibs at willowgarage.com
Mon Nov 8 20:17:07 UTC 2010

On Mon, Nov 8, 2010 at 2:21 AM, Peter Soetens <peter at thesourceworks.com> wrote:
> On Sunday 07 November 2010 16:47:25 Konrad Banachowicz wrote:
>> Hi all,
>> I found that default RTT_COMPONENT_PATH is set to invalid value when orocos
>> is installed from ROS deb.
>> It point to directory where deb was build instead of that where will be
>> installed.
> Orocos uses the CMAKE_INSTALL_PREFIX directory to determine where to set this
> path to. Normally, this should have been set to
> /opt/ros/cturtle/stacks/orocos_toolchain_ros/rtt/install/lib/orocos and
> /opt/ros/cturtle/stacks/orocos_toolchain_ros/ocl/install/lib/orocos for OCL
> And *then* during the 'make install' step, the DEST_DIR variable is used to
> put everything in the /tmp dir and packagae from there on.
> I believe the debian packages use the /tmp directory directly in the
> I'm not sure if we need to nag the debian packagers for this issue, or maybe
> we can fix the make install step in the orocos_toolchain_ros too (by using
> destdir, Ruben ?)

Yes, we are well aware of this problem as it has similar
manifestations in a number of other stacks.

In summary, there is no way to fix this within the debian packaging
system.  The problem is a fundamental shortcoming of the ROS build
system and rosmake.

The entire rosbuild system needs to be modified to have a notion of
install_prefix and dest_dir, and rosmake needs to provide a means of
passing these through to the stacks being built.

Without a "rosmake install" target, the best standin we have is to
simply copy the built stacks from the build location to the final
install location, which obviously has some significant shortcomings.

> On the Orocos side, we're also working on 'ros package awareness' such that
> we're less dependent of the RTT_COMPONENT_PATH and can just use the
> ROS_PACKAGE_PATH to find all required plugins, typekits etc.
> Peter
> _______________________________________________
> ros-users mailing list
> ros-users at code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users

More information about the ros-users mailing list