Re: [Boost-build] Forcing STLport for a given toolset

From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-05-17 09:08:12

On Monday 15 May 2006 20:00, Pedro Lamarão wrote:
> David Abrahams escreveu:
> > # in user-config.jam or site-config.jam
> >
> > using msvc : : : <stdlib>stlport ;
>
> The zipped test case doesn't compile with the attached use-config.jam.
> The $(I6_SDK_PATH) is a path-constant defined in site-config.jam.
>
> I get:
> >bjam toolset=msvc
>
> ...found 9 targets...
> ...updating 2 targets...
> msvc.compile.c++ bin\msvc-6.0\debug\test.obj
> 'cl' is not recognized as an internal or external command,

Hi Pedro,
this specific issue is now fixed. The problem was that specifying any toolset 
options (like <stdlib>stlport), would wipe away any information about 
compiler path, so "cl.exe" would not be found.

But anyway, I'm not sure this style of specifying standard library is 
supported at all.

> The test works as expected if I declare the toolset simply as:
>
>   using msvc : 6.0 ;
>
> and build with
>
>   bjam toolset=msvc-6.0 stdlib=stlport

Yea, this is the standard style of building with stlport. Is that fine with 
you, or you need something else? If you want to always build with SLTPort, 
you can put the following in your user-config.jam:

  project : requirements <toolset-msvc:version>7.1:<stdlib>stlport ;

Sorry for a bit ugly syntax of specifying toolset version, we'll improve on it 
later.

- Volodya

-- 
Vladimir Prus
http://vladimir_prus.blogspot.com
Boost.Build V2: http://boost.org/boost-build2