Re: Orocos integration in buildroot

On Tue, Jan 29, 2013 at 1:56 PM, Willy Lambert <[email protected]> wrote:
> 2013/1/28 Charles Lesire-Cabaniols <[email protected]>:
>>
>>
>>
>> 2013/1/23 Willy Lambert <[email protected]>
>>>
>>> 2013/1/22 Philippe Hamelin <[email protected]>:
>>> > 2013/1/22 Willy Lambert <[email protected]>
>>> >>
>>> >> 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
>>> [email protected]
>>> 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-Dev mailing list
[email protected]
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev