[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

libboost and asio



I don't understand how that works.  How do the target-specific flags get passed on to the compiler?

For example, when I build an application for an RTEMS-mvme3100 target I see compiler flags like:
	powerpc-rtems4.10-g++ -B/usr/local/rtems/rtems-4.10/powerpc-rtems4.10/mvme3100/lib/ -specs bsp_specs -qrtems -mcpu=powerpc -msoft-float
but if I build for an RTEMS-mvme2100 target I see
	powerpc-rtems4.10-g++ -B/usr/local/rtems/rtems-4.10/powerpc-rtems4.10/mvme2100/lib/ -specs bsp_specs -qrtems -mcpu=603e

So with the 'using' line shown below, what header files are used for building boost and for what CPU architecture are the objects built?

On Mar 16, 2011, at 12:41 AM, Sebastian Huber wrote:

> On 03/15/2011 09:42 PM, Eric Norum wrote:
>> Has anyone looked into proting the boost (http://www.boost.org/) and asio (http://think-async.com/) packages to RTEMS?
>> Merging the boost and RTEMS build systems looks like a lot of work -- I'm hoping that I'm mistaken in this, though.
>> 
>> Thanks,
> 
> It was quite easy to build boost for RTEMS.  You have to modify the file:
> 
> tools/build/v2/user-config.jam
> 
> Use something like this:
> 
> using gcc : 4.5.2 : powerpc-rtems4.11-g++ ;
> 
> A lot of modules work well after minor modifications in the config header.  I
> use mainly the header only parts.
> 
> -- 
> Sebastian Huber, embedded brains GmbH
> 
> Address : Obere Lagerstr. 30, D-82178 Puchheim, Germany
> Phone   : +49 89 18 90 80 79-6
> Fax     : +49 89 18 90 80 79-9
> E-Mail  : sebastian.huber at embedded-brains.de
> PGP     : Public key available on request.
> 
> Diese Nachricht ist keine gesch?ftliche Mitteilung im Sinne des EHUG.
> _______________________________________________
> rtems-users mailing list
> rtems-users at rtems.org
> http://www.rtems.org/mailman/listinfo/rtems-users

-- 
Eric Norum
wenorum at lbl.gov