I'm going to merge new stuff into master, causing an effective deviation from
the toolchain-2.4 branches and preparing 2.5.
For RTT, these topics are for merge:
- Use IS_ROS_PACKAGE macro instead of ROS_ROOT in useorocos.cmake macros. This
will fix building RTT,OCL, etc in non-ros package trees on systems where ROS is
installed and autoproj is used
- Removing the RTT::internal::Signal from ports. You'll be able to register
only one callback to a port, and the getNewDataEvent() function is gone. This
gives us a 10% reduction in code size and compensates the 2.3->2.4 regression
(but doesn't fix it !)
- Merge type primitives branch. This allows typekits to choose if a type is a
'full' type or a 'primitive' type. A primitive type can not be sent over a flow
port, for example, all int_xy_t types and sequence [] types in ROS-like
environments. This will reduce the compilation time of ROS typekits by about
30%. The ros typekits need to be adapted to use these new type info classes.
- Add support for fixed size arrays in the type system. ROS typekits need this
with fixed size messages.
- I also succeeded in building RTT + omniorb with clang 2.9
- We will also create an orocos_toolchain.git repository which has all the
orocos toolchain git repos as submodules.
I'm also looking at these branches, please reply with OK or comment if it is
for merging:
- snrkiwi/toolchain-next
- phamelin/v2.3.1-sm-win32-fixes
- lua stuff from markus, possible fixes for the type system not being able to
handle types as reported on the ML
For the other repositories, take a look at the master-ros-refactoring, which
changes how packages are built in ROS, using the same layout as autoproj.
These will be merged in their respective master branches as well.
I'm also a bit worried about all the tooling going on, being announced on the
ML and then not being included in releases, and not being easily found on the
website. We need a system similar/identical to the ROS package trees for
tracking this content. I wonder how easy it would be to (literally) copy the
ROS infrastructure and add 'Orocos' package repositories. We could also talk
to the ROS guys and ask them how they feel about it... using their
infrastructure directly (with an Orocos logo/branding) or copying it to our
own servers...
I looked at the rock package directory, but I'm missing the concepts of a
stack and a wiki to online edit the documentation. It would be neat if the
rock package directory could be part of this scheme though.
Peter
Re: Merging new branches in Orocos Toolchain/master branches
Hello.
I try to manage my project with submodules and it's a bit tricky IMHO.
I know that Sylvain works on autoproj and i would like to ask him if he plan to integrate the submodule feature ?
At the first clone of a repository, there should not be too many problems.
But when we need to update, i see some differents options : (1) the user don't make any changes int the project
(2) the user is a developer and will make some changes use --rebase or --merge with submodule update ?I don't find any good documentation that explain the submodules workflow with git (i find only complains on its usage...).
How will you use this feature ?