[...]

>>
>> I've pushed a fixed for this to the orocos_toolchain_ros_0.2 branch.
>> Other branches will be updated when Ruben triggers a new release.
>
> Ok thanks. I am a bit lost with versionning and compatibility.
> May I have a proper install with cturtle or diamonback with the
> orocos_toolchain_ros_0.2  ? Or should I only wait for next release (if so I
> would be glad to have a goal of it, with no guarantee of course, but i'll
> help my scheduling)

Ruben did a new release of the orocos_toolchain_ros packages this
morning. It will take some time before the software is available, as
it needs to pass some tests on the ROS build farm first. It then
should be available for installation when a new release is triggered
at willowgarage (no idea when this will be).

In the meantime you can of course work on the git repositories. We're
deleting the orocos_toolchain_ros_0.2 branch and continue development
on master (as they both serve the same purpose anyway). This
development is diamondback based. If you work with cturtle - use the
cturtle_next branch.

regards,

Steven

>
>
>>
>> Steven
>>
>> >
>> >
>> >
>> >>
>> >>
>> >>>
>> >>>
>> >>>>>
>> >>>>> regards,
>> >>>>>
>> >>>>> Steven
>> >>>>>
>> >>>>>
>> >>>>> >
>> >>>>> >
>> >>>>> >
>> >>>>> >
>> >>>>> >>
>> >>>>> >> > At the end it seems to have work properly as I have this in the
>> >>>>> >> > folder
>> >>>>> >> > (and
>> >>>>> >> > succeed a build yesterday) :
>> >>>>> >> >
>> >>>>> >> >
>> >>>>> >> > ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
>> >>>>> >> > ls
>> >>>>> >> > CMakeLists.txt  env.sh    ocl     rosdep.yaml  rtt_exercises
>> >>>>> >> > rtt_ros_integration_example   stack.xml  utilmm
>> >>>>> >> > env.mk          Makefile  orogen  rtt
>> >>>>> >> > rtt_ros_integration
>> >>>>> >> > rtt_ros_integration_std_msgs  typelib    utilrb
>> >>>>> >> >
>> >>>>> >> > ard@ard-host-v5:/media/DD_data/home/ard/ros/orocos_toolchain_ros$
>> >>>>> >> >
>> >>>>> >> >
>> >>>>> >> >
>> >>>>> >> > _______________________________________________
>> >>>>> >> > ros-users mailing list
>> >>>>> >> > ros-users@code.ros.org
>> >>>>> >> > https://code.ros.org/mailman/listinfo/ros-users
>> >>>>> >> >
>> >>>>> >> >
>> >>>>> >> --
>> >>>>> >> Orocos-Users mailing list
>> >>>>> >> Orocos-Users@lists.mech.kuleuven.be
>> >>>>> >> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>> >>>>> >
>> >>>>> >
>> >>>>> > _______________________________________________
>> >>>>> > ros-users mailing list
>> >>>>> > ros-users@code.ros.org
>> >>>>> > https://code.ros.org/mailman/listinfo/ros-users
>> >>>>> >
>> >>>>> >
>> >>>>> _______________________________________________
>> >>>>> ros-users mailing list
>> >>>>> ros-users@code.ros.org
>> >>>>> https://code.ros.org/mailman/listinfo/ros-users
>> >>>>
>> >>>
>> >>
>> >
>> >
>> > _______________________________________________
>> > ros-users mailing list
>> > ros-users@code.ros.org
>> > https://code.ros.org/mailman/listinfo/ros-users
>> >
>> >
>> --
>> Orocos-Users mailing list
>> Orocos-Users@lists.mech.kuleuven.be
>> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>
>
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>
>