Boost logo

Boost-Build :

Subject: Re: [Boost-build] Using target alternatives
From: Phil Bass (Phil.Bass_at_[hidden])
Date: 2008-09-17 06:23:59

Steven Watanabe wrote:
> Phil Bass wrote:
>> obj Stub_Types_obj : Stub_Types_i386.cpp : <toolset>gcc-x86 ;
>> obj Stub_Types_obj : Stub_Types_ppc.cpp : <toolset>gcc-ppc ;
> Try this:
> obj Stub_Types_obj : Stub_Types_i386.cpp : <toolset>gcc
> <toolset-gcc:version>x86 ;

Thanks, Steven. I did discover the correct toolset version syntax by
chance in another posting to this list and it's partially working. We
only use the one toolset here so I now have:

   obj Stub_Types_obj : Stub_Types_i386.cpp : <toolset-gcc:version>x86 ;
   obj Stub_Types_obj : Stub_Types_ppc.cpp : <toolset-gcc:version>ppc ;

As we only build static libraries from our own code ATM I usually do
'bjam link=static' and that just works. (I also have <link>static as a
project-wide default build option in Jamroot.) However, if I omit the
link property from the command line I still get the errors I mentioned
in my first email.

Presumably Boost.Build is only having a problem trying to work out how
to build my library as a shared library, but I can't see why.

>> ... is it possible to select by toolset
>> version? (I haven't been able to find anything in the docs on this.)

I still haven't found anything in the docs. Have I missed it or should
something be added to the docs?

Phil Bass (pab_at_[hidden])
     The views expressed in this e-mail/posting are those of the author
     and do not necessarily reflect those of Isotek Electronics Ltd.

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at