2011/10/13 Willy Lambert <lambert [dot] willy [..] ...>:
>
> 011/10/6 Peter Soetens <peter [..] ...>
>>
>> The Orocos development team is proud to announce the fifth major release
>> of the Orocos Toolchain. It's a fat month late, partly due to your
>> maintainer
>> being loaded, partly due to the had-to-fix-show-stoppers that popped up
>> the last month. The end result is shining though. Here's the major
>> highlights:
>> * The toolchain and each Orocos package depending on it now supports the
>> OROCOS_TARGET environment variable. It's being picked up by the build
>> system and by the deployers in OCL.
>> * Some major issues in the CORBA transport have been fixed
>> * OCL got a revamped Reporting component
>> * Lua updates all over the place, giving you the juicy stuff described
>> in the Orocos Lua Cookbook
>> * The ROS integration for Electric has been restructured completely such
>> that the packages and stacks now follow consistent naming.[1]
>
> I had a quick look a the orocos_toolchain_ros/electric page. I would like to
> install all this stuff from sources (because I use debian). How I am
> supposed to proceed ?
> Do I need to get stacks one by one ?

Yes, following the links listed on each of the stack pages. You'll see
that the orocos toolchain is hosted on gitorious, the others are
hosted on git.mech.kuleuven.be/robotics

> Should I compile orocos_toolchain from ROS or like the standard installation
> ?

With this new stack layout, that shouldn't matter anymore AFAIK, as
both installations will result in the same structure.

> Is it a way to checkout the "metapackage" ? How can I do this ?

This is still WIP. But that metapackage is used for prebuild installs,
so I think you can't use it anyway.

Steven

>
>>
>> * The ROS integration now supports fixed-size types and produces smaller
>> typekits.
>> * Support for CPU affinity for threads (note: Xenomai is experimental)
>> There's also a caveat when you attached multiple callbacks to an
>> InputPort,
>> see the full list of caveats and release notes here:
>>
>>  http://www.orocos.org/stable/documentation/rtt/v2.5.x/doc-xml/orocos-rtt-changes.html
>> You'll also have to checkout our new rtt_dot_service which generates a
>> graph of your components and connections.[2] Any contribution is welcome
>> here to make this an indispensable tool for every user !
>> There are also numerous bugfixes, tracked down and fixed by contributors,
>> whose numbers are still increasing.. thanks a lot for improving the
>> experience
>> for all of us !
>> If you'd like to have the toolchain in an Ubuntu package, you can add the
>> ROS repositories[3] and install ros-electric-orocos-toolchain, which
>> depends on
>> very little of ROS. Full ROS support is available when installing
>> ros-electric-rtt-common-msgs, ros-electric-rtt-ros-comm and
>> ros-electric-rtt-ros-integration
>> (note: we expect a bugfix update for ROS Ubuntu packages the coming days,
>> so keep an eye on your Ubuntu software updates.)
>> If not keen on ROS, you can get it in the usual way from here
>>     http://www.orocos.org/wiki/orocos/toolchain/quick-start
>> or here
>>     http://people.mech.kuleuven.be/~orocos/pub/stable/toolchain/v2.5.0/
>> or just clone the orocos_toolchain git repository as described here
>>     http://www.gitorious.org/orocos-toolchain/orocos_toolchain
>> Peter
>> [1] http://www.ros.org/wiki/rtt_ros_integration and click on the
>> 'Electric' button
>> [2] http://gitorious.org/rtt_dot_service
>> [3] http://www.ros.org/wiki/ROS/Installation
>>
>> --
>> Orocos-Users mailing list
>> Orocos-Users [..] ...
>> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>>
>
>