Orocos integration in buildroot

Hi all,

for some time ago, Philippe Hamelin pointed me to his git repo with
Orocos integrated in Buildroot in the aim to fit in a low performance
devices :
https://github.com/phamelin/buildroot/tree/2011.05-sm

I spent some time to play with Buildroot with the aim of reducing my
rootfs from 2GB to something like 200Mb.

I'm now ready with buildroot and I'm attacking the Orocos packaging
from Philippe's work. I would like to post patches to buildroot about
Orocos integration. Does anyone care about this ?

@Philippe, was there any reason why you did not post you work back to
Buildroot ? (Technical problems ? Time ? Paches refused ? )

I have improved a bit the boost integration to be able to choose your
version from the config menu. I was only able to take 1.40 to 1.44
boost versions as jam as been reworked after. Does anyone know a bit
about that here ?

Orocos integration in buildroot

2013/1/22 Willy Lambert <lambert [dot] willy [..] ...>

> Hi all,
>
> for some time ago, Philippe Hamelin pointed me to his git repo with
> Orocos integrated in Buildroot in the aim to fit in a low performance
> devices :
> https://github.com/phamelin/buildroot/tree/2011.05-sm
>
> I spent some time to play with Buildroot with the aim of reducing my
> rootfs from 2GB to something like 200Mb.
>
> I'm now ready with buildroot and I'm attacking the Orocos packaging
> from Philippe's work. I would like to post patches to buildroot about
> Orocos integration. Does anyone care about this ?
>
>
I'm glad to hear that it serves someone else.

> @Philippe, was there any reason why you did not post you work back to
> Buildroot ? (Technical problems ? Time ? Paches refused ? )
>
>
Time as usual :-)

Philippe

Orocos integration in buildroot

2013/1/22 Philippe Hamelin <philippe [dot] hamelin [..] ...>:
> 2013/1/22 Willy Lambert <lambert [dot] willy [..] ...>
>>
>> Hi all,
>>
>> for some time ago, Philippe Hamelin pointed me to his git repo with
>> Orocos integrated in Buildroot in the aim to fit in a low performance
>> devices :
>> https://github.com/phamelin/buildroot/tree/2011.05-sm
>>
>> I spent some time to play with Buildroot with the aim of reducing my
>> rootfs from 2GB to something like 200Mb.
>>
>> I'm now ready with buildroot and I'm attacking the Orocos packaging
>> from Philippe's work. I would like to post patches to buildroot about
>> Orocos integration. Does anyone care about this ?
>>
>
> I'm glad to hear that it serves someone else.
>
>>
>> @Philippe, was there any reason why you did not post you work back to
>> Buildroot ? (Technical problems ? Time ? Paches refused ? )
>>
>
> Time as usual :-)
>
> Philippe
>

I seems that boost is now existing in new buildroot versions.

In order to pur Orocos in Buildroot I need a way to get Orocos
sources. The options are :
_ a git link to a .git file (would be :
git://gitorious.org/orocos-toolchain/rtt.git for instance, but is this
branch stable ?)
_ a direct link to a source tarball (would be :
http://people.mech.kuleuven.be/~orocos/pub/stable/toolchain/, but what
about minor patches ...)

Any idea about the best solution ?

Orocos integration in buildroot

2013/1/23 Willy Lambert <lambert [dot] willy [..] ...>

> 2013/1/22 Philippe Hamelin <philippe [dot] hamelin [..] ...>:
> > 2013/1/22 Willy Lambert <lambert [dot] willy [..] ...>
> >>
> >> Hi all,
> >>
> >> for some time ago, Philippe Hamelin pointed me to his git repo with
> >> Orocos integrated in Buildroot in the aim to fit in a low performance
> >> devices :
> >> https://github.com/phamelin/buildroot/tree/2011.05-sm
> >>
> >> I spent some time to play with Buildroot with the aim of reducing my
> >> rootfs from 2GB to something like 200Mb.
> >>
> >> I'm now ready with buildroot and I'm attacking the Orocos packaging
> >> from Philippe's work. I would like to post patches to buildroot about
> >> Orocos integration. Does anyone care about this ?
> >>
> >
> > I'm glad to hear that it serves someone else.
> >
> >>
> >> @Philippe, was there any reason why you did not post you work back to
> >> Buildroot ? (Technical problems ? Time ? Paches refused ? )
> >>
> >
> > Time as usual :-)
> >
> > Philippe
> >
>
> I seems that boost is now existing in new buildroot versions.
>
>
>
> In order to pur Orocos in Buildroot I need a way to get Orocos
> sources. The options are :
> _ a git link to a .git file (would be :
> git://gitorious.org/orocos-toolchain/rtt.git for instance, but is this
> branch stable ?)
>

You have to point to the last stable release. Today it's toolchain-2.6. Bug
fixes are directly applied to this branch when needed.

> _ a direct link to a source tarball (would be :
> http://people.mech.kuleuven.be/~orocos/pub/stable/toolchain/, but what
> about minor patches ...)
>
> Any idea about the best solution ?
> --
> Orocos-Dev mailing list
> Orocos-Dev [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev
>

Orocos integration in buildroot

2013/1/28 Charles Lesire-Cabaniols <charles [dot] lesire [..] ...>:
>
>
>
> 2013/1/23 Willy Lambert <lambert [dot] willy [..] ...>
>>
>> 2013/1/22 Philippe Hamelin <philippe [dot] hamelin [..] ...>:
>> > 2013/1/22 Willy Lambert <lambert [dot] willy [..] ...>
>> >>
>> >> Hi all,
>> >>
>> >> for some time ago, Philippe Hamelin pointed me to his git repo with
>> >> Orocos integrated in Buildroot in the aim to fit in a low performance
>> >> devices :
>> >> https://github.com/phamelin/buildroot/tree/2011.05-sm
>> >>
>> >> I spent some time to play with Buildroot with the aim of reducing my
>> >> rootfs from 2GB to something like 200Mb.
>> >>
>> >> I'm now ready with buildroot and I'm attacking the Orocos packaging
>> >> from Philippe's work. I would like to post patches to buildroot about
>> >> Orocos integration. Does anyone care about this ?
>> >>
>> >
>> > I'm glad to hear that it serves someone else.
>> >
>> >>
>> >> @Philippe, was there any reason why you did not post you work back to
>> >> Buildroot ? (Technical problems ? Time ? Paches refused ? )
>> >>
>> >
>> > Time as usual :-)
>> >
>> > Philippe
>> >
>>
>> I seems that boost is now existing in new buildroot versions.
>>
>>
>>
>> In order to pur Orocos in Buildroot I need a way to get Orocos
>> sources. The options are :
>> _ a git link to a .git file (would be :
>> git://gitorious.org/orocos-toolchain/rtt.git for instance, but is this
>> branch stable ?)
>
>
> You have to point to the last stable release. Today it's toolchain-2.6. Bug
> fixes are directly applied to this branch when needed.
>
>>
>> _ a direct link to a source tarball (would be :
>> http://people.mech.kuleuven.be/~orocos/pub/stable/toolchain/, but what
>> about minor patches ...)
>>
>> Any idea about the best solution ?
>> --
>> Orocos-Dev mailing list
>> Orocos-Dev [..] ...
>> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev
>
>

I managed to get sources and start building them.

I currently have a build error in rtt/ExecutionEngine.cpp, that's
certainly due to the -fno-exeption option given to gcc. The are 2
questions around this :
_ is it possible to build Orocos without exeptions ?
_ is there any other code that could rely on exeptions that compiled
that I could take as an example to propose a patch if this is an
unexpected error.

[ 12%] Building C object
rtt/CMakeFiles/orocos-rtt-gnulinux_dynamic.dir/os/tlsf/tlsf.c.o
cd /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt &&
/wix/buildroot/output/host/usr/bin/i686-buildroot-linux-uclibc-gcc
-DRTT_DLL_EXPORT -DOROCOS_TARGET=gnulinux -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -pipe -O2
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
-pipe -O2 -Os -DNDEBUG -fPIC
-I/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/os/gnulinux
-I/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/os
-I/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt
-I/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt
-I/wix/buildroot/output/host/usr/i686-buildroot-linux-uclibc/sysroot/usr/include
-Wall -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
-D_FILE_OFFSET_BITS=64 -pipe -O2 -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -pipe -O2
-fmessage-length=0 -fno-exceptions -ffunction-sections -fdata-sections
-o CMakeFiles/orocos-rtt-gnulinux_dynamic.dir/os/tlsf/tlsf.c.o -c
/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/os/tlsf/tlsf.c
/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:
In member function 'void RTT::ExecutionEngine::processChildren()':
/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:332:47:
error: exception handling disabled, use -fexceptions to enable
/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:334:43:
error: 'e' was not declared in this scope
/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:332:19:
error: '...' handler must be the last handler for its try block
/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:347:43:
error: 'e' was not declared in this scope
/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:345:19:
error: '...' handler must be the last handler for its try block
/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:365:43:
error: 'e' was not declared in this scope
/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:363:19:
error: '...' handler must be the last handler for its try block
/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:376:43:
error: 'e' was not declared in this scope
/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:374:19:
error: '...' handler must be the last handler for its try block
make[3]: *** [rtt/CMakeFiles/orocos-rtt-gnulinux_dynamic.dir/ExecutionEngine.cpp.o]
Error 1
make[3]: *** Waiting for unfinished jobs....
/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/OperationInterface.cpp:
In member function 'bool RTT::OperationInterface::isSynchronous(const
std::string&) const':
/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/OperationInterface.cpp:99:13:
error: exception handling disabled, use -fexceptions to enable
make[3]: *** [rtt/CMakeFiles/orocos-rtt-gnulinux_dynamic.dir/OperationInterface.cpp.o]
Error 1
/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/Service.cpp: In
member function 'RTT::Service::shared_ptr RTT::Service::provides()':
/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/Service.cpp:108:37:
error: exception handling disabled, use -fexceptions to enable
make[3]: *** [rtt/CMakeFiles/orocos-rtt-gnulinux_dynamic.dir/Service.cpp.o]
Error 1

Orocos integration in buildroot

On Tue, Jan 29, 2013 at 1:56 PM, Willy Lambert <lambert [dot] willy [..] ...> wrote:
> 2013/1/28 Charles Lesire-Cabaniols <charles [dot] lesire [..] ...>:
>>
>>
>>
>> 2013/1/23 Willy Lambert <lambert [dot] willy [..] ...>
>>>
>>> 2013/1/22 Philippe Hamelin <philippe [dot] hamelin [..] ...>:
>>> > 2013/1/22 Willy Lambert <lambert [dot] willy [..] ...>
>>> >>
>>> >> Hi all,
>>> >>
>>> >> for some time ago, Philippe Hamelin pointed me to his git repo with
>>> >> Orocos integrated in Buildroot in the aim to fit in a low performance
>>> >> devices :
>>> >> https://github.com/phamelin/buildroot/tree/2011.05-sm
>>> >>
>>> >> I spent some time to play with Buildroot with the aim of reducing my
>>> >> rootfs from 2GB to something like 200Mb.
>>> >>
>>> >> I'm now ready with buildroot and I'm attacking the Orocos packaging
>>> >> from Philippe's work. I would like to post patches to buildroot about
>>> >> Orocos integration. Does anyone care about this ?
>>> >>
>>> >
>>> > I'm glad to hear that it serves someone else.
>>> >
>>> >>
>>> >> @Philippe, was there any reason why you did not post you work back to
>>> >> Buildroot ? (Technical problems ? Time ? Paches refused ? )
>>> >>
>>> >
>>> > Time as usual :-)
>>> >
>>> > Philippe
>>> >
>>>
>>> I seems that boost is now existing in new buildroot versions.
>>>
>>>
>>>
>>> In order to pur Orocos in Buildroot I need a way to get Orocos
>>> sources. The options are :
>>> _ a git link to a .git file (would be :
>>> git://gitorious.org/orocos-toolchain/rtt.git for instance, but is this
>>> branch stable ?)
>>
>>
>> You have to point to the last stable release. Today it's toolchain-2.6. Bug
>> fixes are directly applied to this branch when needed.
>>
>>>
>>> _ a direct link to a source tarball (would be :
>>> http://people.mech.kuleuven.be/~orocos/pub/stable/toolchain/, but what
>>> about minor patches ...)
>>>
>>> Any idea about the best solution ?
>>> --
>>> Orocos-Dev mailing list
>>> Orocos-Dev [..] ...
>>> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev
>>
>>
>
> I managed to get sources and start building them.
>
> I currently have a build error in rtt/ExecutionEngine.cpp, that's
> certainly due to the -fno-exeption option given to gcc. The are 2
> questions around this :
> _ is it possible to build Orocos without exeptions ?

No. Boost depends on it too heavily, last time I checked. I abandoned
supporting this compiler flag after this fact. Older boost versions
(like 1.32 ? 1.36 ?) still allowed this but even so, there would still
be some work to do.

> _ is there any other code that could rely on exeptions that compiled
> that I could take as an example to propose a patch if this is an
> unexpected error.

As you might have found out, it's
#ifdef OROBLD_OS_NOEXCEPTIONS
//bail out
#else
// existing exception code
#endif

But boost will be your first target...

Peter

Orocos integration in buildroot

2013/2/1 Peter Soetens <peter [..] ...>:
> On Tue, Jan 29, 2013 at 1:56 PM, Willy Lambert <lambert [dot] willy [..] ...> wrote:
>> 2013/1/28 Charles Lesire-Cabaniols <charles [dot] lesire [..] ...>:
>>>
>>>
>>>
>>> 2013/1/23 Willy Lambert <lambert [dot] willy [..] ...>
>>>>
>>>> 2013/1/22 Philippe Hamelin <philippe [dot] hamelin [..] ...>:
>>>> > 2013/1/22 Willy Lambert <lambert [dot] willy [..] ...>
>>>> >>
>>>> >> Hi all,
>>>> >>
>>>> >> for some time ago, Philippe Hamelin pointed me to his git repo with
>>>> >> Orocos integrated in Buildroot in the aim to fit in a low performance
>>>> >> devices :
>>>> >> https://github.com/phamelin/buildroot/tree/2011.05-sm
>>>> >>
>>>> >> I spent some time to play with Buildroot with the aim of reducing my
>>>> >> rootfs from 2GB to something like 200Mb.
>>>> >>
>>>> >> I'm now ready with buildroot and I'm attacking the Orocos packaging
>>>> >> from Philippe's work. I would like to post patches to buildroot about
>>>> >> Orocos integration. Does anyone care about this ?
>>>> >>
>>>> >
>>>> > I'm glad to hear that it serves someone else.
>>>> >
>>>> >>
>>>> >> @Philippe, was there any reason why you did not post you work back to
>>>> >> Buildroot ? (Technical problems ? Time ? Paches refused ? )
>>>> >>
>>>> >
>>>> > Time as usual :-)
>>>> >
>>>> > Philippe
>>>> >
>>>>
>>>> I seems that boost is now existing in new buildroot versions.
>>>>
>>>>
>>>>
>>>> In order to pur Orocos in Buildroot I need a way to get Orocos
>>>> sources. The options are :
>>>> _ a git link to a .git file (would be :
>>>> git://gitorious.org/orocos-toolchain/rtt.git for instance, but is this
>>>> branch stable ?)
>>>
>>>
>>> You have to point to the last stable release. Today it's toolchain-2.6. Bug
>>> fixes are directly applied to this branch when needed.
>>>
>>>>
>>>> _ a direct link to a source tarball (would be :
>>>> http://people.mech.kuleuven.be/~orocos/pub/stable/toolchain/, but what
>>>> about minor patches ...)
>>>>
>>>> Any idea about the best solution ?
>>>> --
>>>> Orocos-Dev mailing list
>>>> Orocos-Dev [..] ...
>>>> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev
>>>
>>>
>>
>> I managed to get sources and start building them.
>>
>> I currently have a build error in rtt/ExecutionEngine.cpp, that's
>> certainly due to the -fno-exeption option given to gcc. The are 2
>> questions around this :
>> _ is it possible to build Orocos without exeptions ?
>
> No. Boost depends on it too heavily, last time I checked. I abandoned
> supporting this compiler flag after this fact. Older boost versions
> (like 1.32 ? 1.36 ?) still allowed this but even so, there would still
> be some work to do.
>
>> _ is there any other code that could rely on exeptions that compiled
>> that I could take as an example to propose a patch if this is an
>> unexpected error.
>
> As you might have found out, it's
> #ifdef OROBLD_OS_NOEXCEPTIONS
> //bail out
> #else
> // existing exception code
> #endif

Thanks for pointing (and no I didn't find that ^^). Should I have a
look at correcting it, or is should I clean this option out ?
>
> But boost will be your first target...
>
> Peter

Orocos integration in buildroot

2013/1/29 Willy Lambert <lambert [dot] willy [..] ...>:
> 2013/1/28 Charles Lesire-Cabaniols <charles [dot] lesire [..] ...>:
>>
>>
>>
>> 2013/1/23 Willy Lambert <lambert [dot] willy [..] ...>
>>>
>>> 2013/1/22 Philippe Hamelin <philippe [dot] hamelin [..] ...>:
>>> > 2013/1/22 Willy Lambert <lambert [dot] willy [..] ...>
>>> >>
>>> >> Hi all,
>>> >>
>>> >> for some time ago, Philippe Hamelin pointed me to his git repo with
>>> >> Orocos integrated in Buildroot in the aim to fit in a low performance
>>> >> devices :
>>> >> https://github.com/phamelin/buildroot/tree/2011.05-sm
>>> >>
>>> >> I spent some time to play with Buildroot with the aim of reducing my
>>> >> rootfs from 2GB to something like 200Mb.
>>> >>
>>> >> I'm now ready with buildroot and I'm attacking the Orocos packaging
>>> >> from Philippe's work. I would like to post patches to buildroot about
>>> >> Orocos integration. Does anyone care about this ?
>>> >>
>>> >
>>> > I'm glad to hear that it serves someone else.
>>> >
>>> >>
>>> >> @Philippe, was there any reason why you did not post you work back to
>>> >> Buildroot ? (Technical problems ? Time ? Paches refused ? )
>>> >>
>>> >
>>> > Time as usual :-)
>>> >
>>> > Philippe
>>> >
>>>
>>> I seems that boost is now existing in new buildroot versions.
>>>
>>>
>>>
>>> In order to pur Orocos in Buildroot I need a way to get Orocos
>>> sources. The options are :
>>> _ a git link to a .git file (would be :
>>> git://gitorious.org/orocos-toolchain/rtt.git for instance, but is this
>>> branch stable ?)
>>
>>
>> You have to point to the last stable release. Today it's toolchain-2.6. Bug
>> fixes are directly applied to this branch when needed.
>>
>>>
>>> _ a direct link to a source tarball (would be :
>>> http://people.mech.kuleuven.be/~orocos/pub/stable/toolchain/, but what
>>> about minor patches ...)
>>>
>>> Any idea about the best solution ?
>>> --
>>> Orocos-Dev mailing list
>>> Orocos-Dev [..] ...
>>> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev
>>
>>
>
> I managed to get sources and start building them.
>
> I currently have a build error in rtt/ExecutionEngine.cpp, that's
> certainly due to the -fno-exeption option given to gcc. The are 2
> questions around this :
> _ is it possible to build Orocos without exeptions ?
> _ is there any other code that could rely on exeptions that compiled
> that I could take as an example to propose a patch if this is an
> unexpected error.
>
>
> [ 12%] Building C object
> rtt/CMakeFiles/orocos-rtt-gnulinux_dynamic.dir/os/tlsf/tlsf.c.o
> cd /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt &&
> /wix/buildroot/output/host/usr/bin/i686-buildroot-linux-uclibc-gcc
> -DRTT_DLL_EXPORT -DOROCOS_TARGET=gnulinux -D_LARGEFILE_SOURCE
> -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -pipe -O2
> -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
> -pipe -O2 -Os -DNDEBUG -fPIC
> -I/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/os/gnulinux
> -I/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/os
> -I/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt
> -I/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt
> -I/wix/buildroot/output/host/usr/i686-buildroot-linux-uclibc/sysroot/usr/include
> -Wall -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
> -D_FILE_OFFSET_BITS=64 -pipe -O2 -D_LARGEFILE_SOURCE
> -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -pipe -O2
> -fmessage-length=0 -fno-exceptions -ffunction-sections -fdata-sections
> -o CMakeFiles/orocos-rtt-gnulinux_dynamic.dir/os/tlsf/tlsf.c.o -c
> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/os/tlsf/tlsf.c
> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:
> In member function 'void RTT::ExecutionEngine::processChildren()':
> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:332:47:
> error: exception handling disabled, use -fexceptions to enable
> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:334:43:
> error: 'e' was not declared in this scope
> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:332:19:
> error: '...' handler must be the last handler for its try block
> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:347:43:
> error: 'e' was not declared in this scope
> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:345:19:
> error: '...' handler must be the last handler for its try block
> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:365:43:
> error: 'e' was not declared in this scope
> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:363:19:
> error: '...' handler must be the last handler for its try block
> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:376:43:
> error: 'e' was not declared in this scope
> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:374:19:
> error: '...' handler must be the last handler for its try block
> make[3]: *** [rtt/CMakeFiles/orocos-rtt-gnulinux_dynamic.dir/ExecutionEngine.cpp.o]
> Error 1
> make[3]: *** Waiting for unfinished jobs....
> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/OperationInterface.cpp:
> In member function 'bool RTT::OperationInterface::isSynchronous(const
> std::string&) const':
> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/OperationInterface.cpp:99:13:
> error: exception handling disabled, use -fexceptions to enable
> make[3]: *** [rtt/CMakeFiles/orocos-rtt-gnulinux_dynamic.dir/OperationInterface.cpp.o]
> Error 1
> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/Service.cpp: In
> member function 'RTT::Service::shared_ptr RTT::Service::provides()':
> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/Service.cpp:108:37:
> error: exception handling disabled, use -fexceptions to enable
> make[3]: *** [rtt/CMakeFiles/orocos-rtt-gnulinux_dynamic.dir/Service.cpp.o]
> Error 1

I oppened a bugtracker for this part, as I found that standard
gnulinux install has the same problem.

I successfully built log4cpp and rtt. But ocl has some difficulties to
find rtt. cmake says at the same time :

Orocos integration in buildroot

On Thu, Jan 31, 2013 at 2:50 AM, Willy Lambert <lambert [dot] willy [..] ...> wrote:
> 2013/1/29 Willy Lambert <lambert [dot] willy [..] ...>:
>> 2013/1/28 Charles Lesire-Cabaniols <charles [dot] lesire [..] ...>:
>>>
>>>
>>>
>>> 2013/1/23 Willy Lambert <lambert [dot] willy [..] ...>
>>>>
>>>> 2013/1/22 Philippe Hamelin <philippe [dot] hamelin [..] ...>:
>>>> > 2013/1/22 Willy Lambert <lambert [dot] willy [..] ...>
>>>> >>
>>>> >> Hi all,
>>>> >>
>>>> >> for some time ago, Philippe Hamelin pointed me to his git repo with
>>>> >> Orocos integrated in Buildroot in the aim to fit in a low performance
>>>> >> devices :
>>>> >> https://github.com/phamelin/buildroot/tree/2011.05-sm
>>>> >>
>>>> >> I spent some time to play with Buildroot with the aim of reducing my
>>>> >> rootfs from 2GB to something like 200Mb.
>>>> >>
>>>> >> I'm now ready with buildroot and I'm attacking the Orocos packaging
>>>> >> from Philippe's work. I would like to post patches to buildroot about
>>>> >> Orocos integration. Does anyone care about this ?
>>>> >>
>>>> >
>>>> > I'm glad to hear that it serves someone else.
>>>> >
>>>> >>
>>>> >> @Philippe, was there any reason why you did not post you work back to
>>>> >> Buildroot ? (Technical problems ? Time ? Paches refused ? )
>>>> >>
>>>> >
>>>> > Time as usual :-)
>>>> >
>>>> > Philippe
>>>> >
>>>>
>>>> I seems that boost is now existing in new buildroot versions.
>>>>
>>>>
>>>>
>>>> In order to pur Orocos in Buildroot I need a way to get Orocos
>>>> sources. The options are :
>>>> _ a git link to a .git file (would be :
>>>> git://gitorious.org/orocos-toolchain/rtt.git for instance, but is this
>>>> branch stable ?)
>>>
>>>
>>> You have to point to the last stable release. Today it's toolchain-2.6. Bug
>>> fixes are directly applied to this branch when needed.
>>>
>>>>
>>>> _ a direct link to a source tarball (would be :
>>>> http://people.mech.kuleuven.be/~orocos/pub/stable/toolchain/, but what
>>>> about minor patches ...)
>>>>
>>>> Any idea about the best solution ?
>>>> --
>>>> Orocos-Dev mailing list
>>>> Orocos-Dev [..] ...
>>>> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev
>>>
>>>
>>
>> I managed to get sources and start building them.
>>
>> I currently have a build error in rtt/ExecutionEngine.cpp, that's
>> certainly due to the -fno-exeption option given to gcc. The are 2
>> questions around this :
>> _ is it possible to build Orocos without exeptions ?
>> _ is there any other code that could rely on exeptions that compiled
>> that I could take as an example to propose a patch if this is an
>> unexpected error.
>>
>>
>> [ 12%] Building C object
>> rtt/CMakeFiles/orocos-rtt-gnulinux_dynamic.dir/os/tlsf/tlsf.c.o
>> cd /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt &&
>> /wix/buildroot/output/host/usr/bin/i686-buildroot-linux-uclibc-gcc
>> -DRTT_DLL_EXPORT -DOROCOS_TARGET=gnulinux -D_LARGEFILE_SOURCE
>> -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -pipe -O2
>> -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
>> -pipe -O2 -Os -DNDEBUG -fPIC
>> -I/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/os/gnulinux
>> -I/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/os
>> -I/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt
>> -I/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt
>> -I/wix/buildroot/output/host/usr/i686-buildroot-linux-uclibc/sysroot/usr/include
>> -Wall -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
>> -D_FILE_OFFSET_BITS=64 -pipe -O2 -D_LARGEFILE_SOURCE
>> -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -pipe -O2
>> -fmessage-length=0 -fno-exceptions -ffunction-sections -fdata-sections
>> -o CMakeFiles/orocos-rtt-gnulinux_dynamic.dir/os/tlsf/tlsf.c.o -c
>> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/os/tlsf/tlsf.c
>> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:
>> In member function 'void RTT::ExecutionEngine::processChildren()':
>> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:332:47:
>> error: exception handling disabled, use -fexceptions to enable
>> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:334:43:
>> error: 'e' was not declared in this scope
>> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:332:19:
>> error: '...' handler must be the last handler for its try block
>> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:347:43:
>> error: 'e' was not declared in this scope
>> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:345:19:
>> error: '...' handler must be the last handler for its try block
>> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:365:43:
>> error: 'e' was not declared in this scope
>> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:363:19:
>> error: '...' handler must be the last handler for its try block
>> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:376:43:
>> error: 'e' was not declared in this scope
>> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:374:19:
>> error: '...' handler must be the last handler for its try block
>> make[3]: *** [rtt/CMakeFiles/orocos-rtt-gnulinux_dynamic.dir/ExecutionEngine.cpp.o]
>> Error 1
>> make[3]: *** Waiting for unfinished jobs....
>> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/OperationInterface.cpp:
>> In member function 'bool RTT::OperationInterface::isSynchronous(const
>> std::string&) const':
>> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/OperationInterface.cpp:99:13:
>> error: exception handling disabled, use -fexceptions to enable
>> make[3]: *** [rtt/CMakeFiles/orocos-rtt-gnulinux_dynamic.dir/OperationInterface.cpp.o]
>> Error 1
>> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/Service.cpp: In
>> member function 'RTT::Service::shared_ptr RTT::Service::provides()':
>> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/Service.cpp:108:37:
>> error: exception handling disabled, use -fexceptions to enable
>> make[3]: *** [rtt/CMakeFiles/orocos-rtt-gnulinux_dynamic.dir/Service.cpp.o]
>> Error 1
>
> I oppened a bugtracker for this part, as I found that standard
> gnulinux install has the same problem.
>
>
> I successfully built log4cpp and rtt. But ocl has some difficulties to
> find rtt. cmake says at the same time :

Orocos integration in buildroot

2013/2/1 Peter Soetens <peter [..] ...>:
> On Thu, Jan 31, 2013 at 2:50 AM, Willy Lambert <lambert [dot] willy [..] ...> wrote:
>> 2013/1/29 Willy Lambert <lambert [dot] willy [..] ...>:
>>> 2013/1/28 Charles Lesire-Cabaniols <charles [dot] lesire [..] ...>:
>>>>
>>>>
>>>>
>>>> 2013/1/23 Willy Lambert <lambert [dot] willy [..] ...>
>>>>>
>>>>> 2013/1/22 Philippe Hamelin <philippe [dot] hamelin [..] ...>:
>>>>> > 2013/1/22 Willy Lambert <lambert [dot] willy [..] ...>
>>>>> >>
>>>>> >> Hi all,
>>>>> >>
>>>>> >> for some time ago, Philippe Hamelin pointed me to his git repo with
>>>>> >> Orocos integrated in Buildroot in the aim to fit in a low performance
>>>>> >> devices :
>>>>> >> https://github.com/phamelin/buildroot/tree/2011.05-sm
>>>>> >>
>>>>> >> I spent some time to play with Buildroot with the aim of reducing my
>>>>> >> rootfs from 2GB to something like 200Mb.
>>>>> >>
>>>>> >> I'm now ready with buildroot and I'm attacking the Orocos packaging
>>>>> >> from Philippe's work. I would like to post patches to buildroot about
>>>>> >> Orocos integration. Does anyone care about this ?
>>>>> >>
>>>>> >
>>>>> > I'm glad to hear that it serves someone else.
>>>>> >
>>>>> >>
>>>>> >> @Philippe, was there any reason why you did not post you work back to
>>>>> >> Buildroot ? (Technical problems ? Time ? Paches refused ? )
>>>>> >>
>>>>> >
>>>>> > Time as usual :-)
>>>>> >
>>>>> > Philippe
>>>>> >
>>>>>
>>>>> I seems that boost is now existing in new buildroot versions.
>>>>>
>>>>>
>>>>>
>>>>> In order to pur Orocos in Buildroot I need a way to get Orocos
>>>>> sources. The options are :
>>>>> _ a git link to a .git file (would be :
>>>>> git://gitorious.org/orocos-toolchain/rtt.git for instance, but is this
>>>>> branch stable ?)
>>>>
>>>>
>>>> You have to point to the last stable release. Today it's toolchain-2.6. Bug
>>>> fixes are directly applied to this branch when needed.
>>>>
>>>>>
>>>>> _ a direct link to a source tarball (would be :
>>>>> http://people.mech.kuleuven.be/~orocos/pub/stable/toolchain/, but what
>>>>> about minor patches ...)
>>>>>
>>>>> Any idea about the best solution ?
>>>>> --
>>>>> Orocos-Dev mailing list
>>>>> Orocos-Dev [..] ...
>>>>> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev
>>>>
>>>>
>>>
>>> I managed to get sources and start building them.
>>>
>>> I currently have a build error in rtt/ExecutionEngine.cpp, that's
>>> certainly due to the -fno-exeption option given to gcc. The are 2
>>> questions around this :
>>> _ is it possible to build Orocos without exeptions ?
>>> _ is there any other code that could rely on exeptions that compiled
>>> that I could take as an example to propose a patch if this is an
>>> unexpected error.
>>>
>>>
>>> [ 12%] Building C object
>>> rtt/CMakeFiles/orocos-rtt-gnulinux_dynamic.dir/os/tlsf/tlsf.c.o
>>> cd /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt &&
>>> /wix/buildroot/output/host/usr/bin/i686-buildroot-linux-uclibc-gcc
>>> -DRTT_DLL_EXPORT -DOROCOS_TARGET=gnulinux -D_LARGEFILE_SOURCE
>>> -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -pipe -O2
>>> -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
>>> -pipe -O2 -Os -DNDEBUG -fPIC
>>> -I/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/os/gnulinux
>>> -I/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/os
>>> -I/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt
>>> -I/wix/buildroot/output/build/orocos-rtt-2.5.0/rtt
>>> -I/wix/buildroot/output/host/usr/i686-buildroot-linux-uclibc/sysroot/usr/include
>>> -Wall -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
>>> -D_FILE_OFFSET_BITS=64 -pipe -O2 -D_LARGEFILE_SOURCE
>>> -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -pipe -O2
>>> -fmessage-length=0 -fno-exceptions -ffunction-sections -fdata-sections
>>> -o CMakeFiles/orocos-rtt-gnulinux_dynamic.dir/os/tlsf/tlsf.c.o -c
>>> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/os/tlsf/tlsf.c
>>> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:
>>> In member function 'void RTT::ExecutionEngine::processChildren()':
>>> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:332:47:
>>> error: exception handling disabled, use -fexceptions to enable
>>> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:334:43:
>>> error: 'e' was not declared in this scope
>>> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:332:19:
>>> error: '...' handler must be the last handler for its try block
>>> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:347:43:
>>> error: 'e' was not declared in this scope
>>> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:345:19:
>>> error: '...' handler must be the last handler for its try block
>>> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:365:43:
>>> error: 'e' was not declared in this scope
>>> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:363:19:
>>> error: '...' handler must be the last handler for its try block
>>> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:376:43:
>>> error: 'e' was not declared in this scope
>>> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/ExecutionEngine.cpp:374:19:
>>> error: '...' handler must be the last handler for its try block
>>> make[3]: *** [rtt/CMakeFiles/orocos-rtt-gnulinux_dynamic.dir/ExecutionEngine.cpp.o]
>>> Error 1
>>> make[3]: *** Waiting for unfinished jobs....
>>> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/OperationInterface.cpp:
>>> In member function 'bool RTT::OperationInterface::isSynchronous(const
>>> std::string&) const':
>>> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/OperationInterface.cpp:99:13:
>>> error: exception handling disabled, use -fexceptions to enable
>>> make[3]: *** [rtt/CMakeFiles/orocos-rtt-gnulinux_dynamic.dir/OperationInterface.cpp.o]
>>> Error 1
>>> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/Service.cpp: In
>>> member function 'RTT::Service::shared_ptr RTT::Service::provides()':
>>> /wix/buildroot/output/build/orocos-rtt-2.5.0/rtt/rtt/Service.cpp:108:37:
>>> error: exception handling disabled, use -fexceptions to enable
>>> make[3]: *** [rtt/CMakeFiles/orocos-rtt-gnulinux_dynamic.dir/Service.cpp.o]
>>> Error 1
>>
>> I oppened a bugtracker for this part, as I found that standard
>> gnulinux install has the same problem.
>>
>>
>> I successfully built log4cpp and rtt. But ocl has some difficulties to
>> find rtt. cmake says at the same time :

Orocos integration in buildroot

[snip]

I managed to build rtt and ocl. I still have one issue : my ROS_ROOT
is defined because I have my standard developpment toolchain there in
a ROS build system. But when I build with Buildroot, I have my
CMAKE_INSTALL_PREFIX that is "forced" by this (in rtt/CmakeLists.txt)
:

# We force it in case of ROS builds because the UseOrocos.cmake
scripts will always look
# in this path, also during an autoproj/bootstrap build.
IF(ROS_ROOT)
SET(CMAKE_INSTALL_PREFIX
${PROJECT_SOURCE_DIR}/../install CACHE PATH "Orocos install prefix
for ROS builds" FORCE
)
[snip] ...

endif()
ENDIF(ROS_ROOT)

In the best world, I would like to set something in CMake cache to ask
it not to take ROS_ROOT into account, are you interested in such a
feature ?
In the worst world, I have to unset ROS_ROOT locally before building
with Buildroot. The problem is that I don't really have a way to
automate this, so if someone use buildroot with ros it will fail.

Orocos integration in buildroot

i, Feb 1, 2013 at 1:47 PM, Willy Lambert <lambert [dot] willy [..] ...> wrote:
> [snip]
>
> I managed to build rtt and ocl. I still have one issue : my ROS_ROOT
> is defined because I have my standard developpment toolchain there in
> a ROS build system. But when I build with Buildroot, I have my
> CMAKE_INSTALL_PREFIX that is "forced" by this (in rtt/CmakeLists.txt)
> :
>
> # We force it in case of ROS builds because the UseOrocos.cmake
> scripts will always look
> # in this path, also during an autoproj/bootstrap build.
> IF(ROS_ROOT)
> SET(CMAKE_INSTALL_PREFIX
> ${PROJECT_SOURCE_DIR}/../install CACHE PATH "Orocos install prefix
> for ROS builds" FORCE
> )
> [snip] ...
>
> endif()
> ENDIF(ROS_ROOT)
>
>
> In the best world, I would like to set something in CMake cache to ask
> it not to take ROS_ROOT into account, are you interested in such a
> feature ?

We currently use the flag IS_ROS_PACKAGE which is only true if
ROS_ROOT is set and the current directory is in the ROS_PACKAGE_PATH.

However, this flag is 'calculated' in the UseOrocos.cmake file, which
is not used by RTT itself. OCL and all others do use it. So it's only
an issue for RTT, so there you could force ROS out with a cmake flag.

> In the worst world, I have to unset ROS_ROOT locally before building
> with Buildroot. The problem is that I don't really have a way to
> automate this, so if someone use buildroot with ros it will fail.

That would break importing ROS packages in 2.6, since in 2.6, RTT has
the component loading code and depends on the ROS_ROOT variable to see
if roslib/rospack is available.

Peter

Orocos integration in buildroot

2013/2/1 Willy Lambert <lambert [dot] willy [..] ...>:
> [snip]
>
> I managed to build rtt and ocl. I still have one issue : my ROS_ROOT
> is defined because I have my standard developpment toolchain there in
> a ROS build system. But when I build with Buildroot, I have my
> CMAKE_INSTALL_PREFIX that is "forced" by this (in rtt/CmakeLists.txt)
> :
>
> # We force it in case of ROS builds because the UseOrocos.cmake
> scripts will always look
> # in this path, also during an autoproj/bootstrap build.
> IF(ROS_ROOT)
> SET(CMAKE_INSTALL_PREFIX
> ${PROJECT_SOURCE_DIR}/../install CACHE PATH "Orocos install prefix
> for ROS builds" FORCE
> )
> [snip] ...
>
> endif()
> ENDIF(ROS_ROOT)
>
>
> In the best world, I would like to set something in CMake cache to ask
> it not to take ROS_ROOT into account, are you interested in such a
> feature ?
> In the worst world, I have to unset ROS_ROOT locally before building
> with Buildroot. The problem is that I don't really have a way to
> automate this, so if someone use buildroot with ros it will fail.

I think I'm done for review. Before sending this to Buildroot dev
list, I would like to publish my work here to have some comments.
There are very few file (mainly makefile wrappers and kernel type
configuration menus)
Here is my github clone :
https://github.com/wixiw/buildroot

The only things to checks are 3 directories :
package/orocos-log4cpp
package/orocos-rtt
package/orocos-ocl

The Config.in is the file that describe the menu that will be used by
buildroot users to select Orocos, so I need a reviews on this to check
if my comments are good, and if option selection are ok.
The *.mk are the makefile wrappers that will do the build. There is
little thing to review as it is mainly Buildroot stuff.

It's currently freezed on the 2.5 version, but of course, there is
nothing blocking this except that it is the working version on my
robot so I prefer setting up all this before updating to more recent
one. I'll post this to Buildroot in a week, let me know if you are
willing more time to review or just don't care.

Orocos integration in buildroot

2013/1/22 Willy Lambert <lambert [dot] willy [..] ...>:
> Hi all,
>
> for some time ago, Philippe Hamelin pointed me to his git repo with
> Orocos integrated in Buildroot in the aim to fit in a low performance
> devices :
> https://github.com/phamelin/buildroot/tree/2011.05-sm
>
> I spent some time to play with Buildroot with the aim of reducing my
> rootfs from 2GB to something like 200Mb.
>
> I'm now ready with buildroot and I'm attacking the Orocos packaging
> from Philippe's work. I would like to post patches to buildroot about
> Orocos integration. Does anyone care about this ?
>
> @Philippe, was there any reason why you did not post you work back to
> Buildroot ? (Technical problems ? Time ? Paches refused ? )
>
>
> I have improved a bit the boost integration to be able to choose your
> version from the config menu. I was only able to take 1.40 to 1.44
> boost versions as jam as been reworked after. Does anyone know a bit
> about that here ?

Patch enclosed FYI, but it's not really Orocos related (and yes it is
not a git patch because I'm still not at ease with it ;p). The git
repo seems to be quite sleepy, is it usefull that I provide patches
for it or you just don't care if you can get this stuff with newer
buildroot versions