[ros-users] Is it possible to "binary package" built stacks ?

[Willy Lambert]

2010/12/15 Willy Lambert <lambert.willy at gmail.com>

> Building debian package is not an easy thing, as every build thing is in
> Cmake  I am dreaming of "package_all_this_stuff()" command line :) Are you
> using Cpack ? I tested it but is seems to be quite experimental.
>
> Installing to the same location is fine. The root problem is to be
> copy-proof with no forgotten things, I don't care about messing my tagret
> filesystem (since I know where it goes of course). If I copy the tree after
> "resprotect" I'll also copy my sources files on my target ?
>
> ROS seems to be very good at cherry picking all the stuff from everyone in
> the world, subdividing your app in sub modules (packages and stacks) without
> having to do manage a complex building toolchain which manage dependencies.
> It seems to be done in a very easy way (rosdep, rosmake and go on).


It would be so a pity if it won't go until the publish state.
(I forgot a part ^^ )


>
> In searching I found this :
> http://www.ros.org/wiki/ros_release
> which sounds exactly like what I am looking for.
>
> Ken Coley, were you talking about these tools ? To what extends are only
> usable to Willow garage  ? If I only need to change my source organization
> don't care if I can benefit from an automated packaging tool. Are these
> tools only linked to ROS publications ? It's not that I don't want to
> publish my work, but I don't really think it is interessing anyone (yet).
>
> 2010/12/15 Tully Foote <tfoote at willowgarage.com>
>
> rosmake with the --mark-installed option will also drop those flags.
>>
>> Tully
>>
>>
>> On Tue, Dec 14, 2010 at 4:04 PM, Ken Conley <kwc at willowgarage.com> wrote:
>>
>>> Hi Willy,
>>>
>>> We release debian packages for our distributions. We are starting to
>>> include debian packages from external contributors, but we are still
>>> scaling our resources to handle this.
>>>
>>> For your own software, you could do this by building your binaries on
>>> the correct arch, and then creating a "ROS_NOBUILD" file in every
>>> package.  The 'rosprotect' tool in eros does just this:
>>>
>>> http://www.ros.org/wiki/eros_python_tools/rosprotect
>>>
>>> This makes sure it does not get built again.  If you wish to copy this
>>> tree to another system, you have to copy it into the same filesystem
>>> location.  We are current working on resolving this issue.
>>>
>>>  - Ken
>>>
>>> On Tue, Dec 14, 2010 at 3:54 PM, Willy Lambert <lambert.willy at gmail.com>
>>> wrote:
>>> > Thanks for this link.
>>> >
>>> > I don't need to cross compile, all are x86 Linux Systemes. It's like :
>>> > "okay, I finished my developpement, know I would like to publish
>>> precompiled
>>> > binaires". Somehow it's like a make install which separates binairies
>>> from
>>> > build tree.
>>> > I am sure something allows to do it in ROS, it seems to be a so common
>>> > problem. Currently, I build everything my cmake and make install
>>> binaries
>>> > (and conf files) in a separate folder, then I just have to copy this
>>> folder
>>> > on my target. Is there anything like this in ROS ?
>>> >
>>> > Let's take it differently. If I have dependencies, do I need to build
>>> all of
>>> > them, or may I catch pre-compile stacks like you will do with rosdep ?
>>> >
>>> > 2010/12/15 Sebastian Haug <sebhaug at gmail.com>
>>> >>
>>> >> Hi Willy,
>>> >>
>>> >> On Tue, Dec 14, 2010 at 2:50 PM, Willy Lambert <
>>> lambert.willy at gmail.com>
>>> >> wrote:
>>> >> > But after having built everything on my development computer, I'll
>>> want
>>> >> > to
>>> >> > download it to my embedded main board. I don't want to install ROS
>>> on it
>>> >> > in
>>> >> > order to pick everything and build it. Is it possible to generate a
>>> >> > "binary
>>> >> > package" that is easily installable on a different PC (like a debian
>>> >> > package
>>> >> > or a compressed archive of binaries) ? I didn't see anything about
>>> this
>>> >> > in
>>> >> > the docs.
>>> >> Maybe eros (http://www.ros.org/wiki/eros) is something that suits
>>> your
>>> >> needs. Its a toolchain for cross-compilation of ROS for embedded
>>> >> systems.
>>> >>
>>> >> Sebastian
>>> >> _______________________________________________
>>> >> ros-users mailing list
>>> >> ros-users at code.ros.org
>>> >> https://code.ros.org/mailman/listinfo/ros-users
>>> >
>>> >
>>> > _______________________________________________
>>> > ros-users mailing list
>>> > ros-users at code.ros.org
>>> > https://code.ros.org/mailman/listinfo/ros-users
>>> >
>>> >
>>> _______________________________________________
>>> ros-users mailing list
>>> ros-users at code.ros.org
>>> https://code.ros.org/mailman/listinfo/ros-users
>>>
>>
>>
>>
>> --
>> Tully Foote
>> Systems Engineer
>> Willow Garage, Inc.
>> tfoote at willowgarage.com
>> (650) 475-2827
>>
>> _______________________________________________
>> ros-users mailing list
>> ros-users at code.ros.org
>> https://code.ros.org/mailman/listinfo/ros-users
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ros.org/pipermail/ros-users/attachments/20101215/a2b024ee/attachment-0003.html>