Re: [Boost-build] Local platform architecture not represented?

Subject: Re: [Boost-build] Local platform architecture not represented?
From: John Bito (jwbito_at_[hidden])
Date: 2009-04-27 17:35:56

Thanks for the pointer.  I provided a patch in a new Trac ticket.  My
(legacy) code is sensitive to byte-order, and I'd like to write bjam
code to determine the property automatically.  It seems that the jam.h
checks match the gcc pre-defined macros.  I'm only working with the
Sun compiler and gcc, so I can't say if the other checks are
up-to-date.

On Sat, Apr 25, 2009 at 6:38 AM, Vladimir Prus <ghost_at_[hidden]> wrote:
> On Friday 24 April 2009 04:01:00 John Bito wrote:
>> I was happily assuming that the OSPLAT variable described in the
>> Boost.Jam reference would allow me to set up my build to be sensitive
>> to the platform without having logic my Jamfiles (or the script that
>> launches bjam).  I was disappointed that there doesn't appear to be a
>> value for this variable in the build of I bjam I made for Solaris10.
>> The executable I downloaded for Windows does provide a value (only if
>> I access it using modules.peek : OSPLAT - I still struggle with
>> variable scoping).  Does this indicate a problem with the way I built
>> bjam on Solaris?
>
> What exactly are you trying to test? If host OS, you may use the <host-os>
> feature or the OS variable. If the target is, then <target-os> feature.
> OSPLAT appears to  specify the processor, and I'm not sure how up-to-date
> or correct that logic is. It's all in jam.h -- you can check yourself.
>
> - Volodya
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
>