[Boost-build] Changing default toolset for a project

From: K. Noel Belcourt (kbelco_at_[hidden])
Date: 2007-03-22 02:22:56

Hi,

 From this Jamfile fragment you can see in the project requirements  
section, that when I compile this project with the pgi toolset, I  
want this Jamfile's targets to be built with the gcc toolset  
instead.  I want this ability to handle cross-compiling correctly.   
In some cases I have cross compilers that generate code for both the  
host and target os, and other cases where the host compiler only  
generates code for the (different) target os.

Does anyone know if you can do this sort of thing (having the pgi  
toolset forward to gcc)?

# scms Jamfile
project 2.04
   : requirements
     <include>$(scms-root)/include
     # eventually, sigh..
     # <host-os>linux,<toolset>pgi:<target-os>catamount
     # any reason why can't I do this (when building for pgi, build  
with gcc instead)?
     <toolset>pgi:<toolset>gcc
   : usage-requirements
     <include>$(scms-root)/include
   : build-dir $(prebuilt-tpl-dir)/$(scms-home)
   ;

In the case above, I have a pgi toolset that generates code for the  
target os, not for the host os.  Most of the code we generate targets  
the catamount os, but some executables in scms need to run on the  
host os and this pgi compiler can't generate code for the host os.  I  
should add that I've tried this kind of forwarding with other  
toolsets like gcc as the host toolset and it doesn't work that way  
either.  If you're interested, the bjam back trace is attached.

Thanks.

-- Noel