Configuring for multiple toolsets

Hi,

We're trying to figure out how to deploy boost internally
so we can 
easily support multiple development toolsets.  We want to
configure 
some toolsets, like gcc, to use different Fortran compilers
with 
different versions of the C++ compilers.  Here's a brief
list of what 
we want to support on our Linux platforms.

using gcc : 3.4.3 ;	# use g77
using gcc : 4.0 ;	# use gfortran

using pgi : 5.2 ;	
using pgi : 6.0 ;	

using intel : 8.0 ;
using intel : 9.0 ;

using pathscale : 2.3.1 ;

How should we configure our boost/build to give our
developers the 
flexibility to build with whatever toolset they choose on
Linux?  
Should it be done through the site-config.jam and
user-config.jam files 
and, if so, how?  Note that we're thinking of having the
boost 
distribution on a networked file system so all users will
use the same 
boost build (easier to maintain I hope).

Thanks.

-- Noel


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

On Thursday 23 March 2006 21:23, Noel Belcourt wrote:

> We're trying to figure out how to deploy boost
internally so we can
> easily support multiple development toolsets.  We want
to configure
> some toolsets, like gcc, to use different Fortran
compilers with
> different versions of the C++ compilers.  Here's a
brief list of what
> we want to support on our Linux platforms.
>
> using gcc : 3.4.3 ;	# use g77
> using gcc : 4.0 ;	# use gfortran
>
> using pgi : 5.2 ;
> using pgi : 6.0 ;
>
> using intel : 8.0 ;
> using intel : 9.0 ;
>
> using pathscale : 2.3.1 ;
>
> How should we configure our boost/build to give our
developers the
> flexibility to build with whatever toolset they choose
on Linux?
> Should it be done through the site-config.jam and
user-config.jam files
> and, if so, how?  

If you want all developers to have those versions
configured, without manually 
adding user-config.jam to home directories, then
site-config.jam is the right 
solution. It must be placed to the /etc directory of every
development 
machine, and in that case will be automatically read by
Boost.Build on 
startup.

> Note that we're thinking of having the boost 
> distribution on a networked file system so all users
will use the same
> boost build (easier to maintain I hope).

In this case, you can probably add your customization to the
'site-config.jam' 
located inside Boost.Build distribution.

- Volodya

-- 
Vladimir Prus
http://vladimir_pru
s.blogspot.com
Boost.Build V2: http://boost.org/boost-
build2
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build