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.
Pozdrawiam
Konrad Banachowicz
RTT_COMPONENT_PATH in ROS debs
| Submitted by Konrad Banachowicz on Sun, 2010-11-07 15:48 |
[ros-users] RTT_COMPONENT_PATH in ROS debs
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.
The orocos_toolchain_ros is 1.6GB on disk. This is insane. Can't we remove all
the build artifacts from the debian package, before packaging into debs ?
Peter
[ros-users] RTT_COMPONENT_PATH in ROS debs
I have already mentioned it on ros-users :
http://code.ros.org/lurker/message/20101031.123216.8ac464a8.en.html
Pozdrawiam
Konrad Banachowicz
2010/11/8 Peter Soetens <peter [..] ...>
> 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.
>
> The orocos_toolchain_ros is 1.6GB on disk. This is insane. Can't we remove
> all
> the build artifacts from the debian package, before packaging into debs ?
>
> Peter
>
[ros-users] RTT_COMPONENT_PATH in ROS debs
We are testing this on 'unstable'. We have not done this on cturtle
because several packages will break due to improper builds. We believe
we have fixed all of these, but we are testing on unstable first to
verify.
- Ken
On Mon, Nov 8, 2010 at 2:49 AM, Konrad Banachowicz <konradb3 [..] ...> wrote:
> I have already mentioned it on ros-users :
> http://code.ros.org/lurker/message/20101031.123216.8ac464a8.en.html
>
> Pozdrawiam
> Konrad Banachowicz
>
>
> 2010/11/8 Peter Soetens <peter [..] ...>
>>
>> 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.
>>
>> The orocos_toolchain_ros is 1.6GB on disk. This is insane. Can't we remove
>> all
>> the build artifacts from the debian package, before packaging into debs ?
>>
>> Peter
>
>
> _______________________________________________
> ros-users mailing list
> ros-users [..] ...
> https://code.ros.org/mailman/listinfo/ros-users
>
>
[ros-users] RTT_COMPONENT_PATH in ROS debs
As a followup, on unstable, the size of orocos_toolchain_ros is about
700MB. About 200MB of this are "test" executables in rtt/bin, so, if
you want to get this even smaller, that appears to be the main place
to look. There are some other inefficiencies (~100MB), though it
seems that the msg libraries themselves are pretty expensive. There
are 134MB worth of "librtt-ros" typekit and transport libraries in
rtt_ros_integration_std_msgs. As other msgs are added, this may become
a dominant cost.
- Ken
On Mon, Nov 8, 2010 at 4:48 AM, Ken Conley <kwc [..] ...> wrote:
> We are testing this on 'unstable'. We have not done this on cturtle
> because several packages will break due to improper builds. We believe
> we have fixed all of these, but we are testing on unstable first to
> verify.
>
> - Ken
>
> On Mon, Nov 8, 2010 at 2:49 AM, Konrad Banachowicz <konradb3 [..] ...> wrote:
>> I have already mentioned it on ros-users :
>> http://code.ros.org/lurker/message/20101031.123216.8ac464a8.en.html
>>
>> Pozdrawiam
>> Konrad Banachowicz
>>
>>
>> 2010/11/8 Peter Soetens <peter [..] ...>
>>>
>>> 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.
>>>
>>> The orocos_toolchain_ros is 1.6GB on disk. This is insane. Can't we remove
>>> all
>>> the build artifacts from the debian package, before packaging into debs ?
>>>
>>> Peter
>>
>>
>> _______________________________________________
>> ros-users mailing list
>> ros-users [..] ...
>> https://code.ros.org/mailman/listinfo/ros-users
>>
>>
>
[ros-users] RTT_COMPONENT_PATH in ROS debs
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
CMAKE_INSTALL_PREFIX macro.
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 ?)
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] RTT_COMPONENT_PATH in ROS debs
On Mon, Nov 8, 2010 at 2:21 AM, Peter Soetens <peter [..] ...> 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
> CMAKE_INSTALL_PREFIX macro.
>
> 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.
https://code.ros.org/trac/ros/ticket/3062
https://code.ros.org/trac/ros/ticket/3081
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.
https://code.ros.org/trac/ros/ticket/946
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 [..] ...
> https://code.ros.org/mailman/listinfo/ros-users
>