Re: [jamboost] [BBv1] How's gCURRENT_TOOLSET supposed to be used?

From: Rene Rivera (grafik.list_at_[hidden])
Date: 2005-07-08 08:44:41

joaquintides wrote:
> I can't find much info about gCURRENT_TOOLSET, but from
> what I've gathered seems like this global var holds
> the name of the current toolset in the sequence of
> toolsets provided to bjam with -sTOOLS=...

Yes.

> However, seems I'm missing something. I've changed
> a simple Jamfile to echo the following at the beginning
> 
> ECHO $(gCURRENT_TOOLSET) ;
> 
> and then issued the bjam command
> 
> bjam "-sTOOLS=GCC msvc"
> 
> I'd expect to see gcc and msvc echoed in turn, yet what
> I get is:
> $ bjam "-sTOOLS=GCC msvc"
> msvc
> msvc
> ...found 424 targets...
> ...updating 16 targets...
> [rest of the process dealing with both gcc and msvc]
> 
> So, looks like gCURRENT_TOOLSET is not being
> updted properly on every toolset processed!
> Am I missing something? Thanks for your help,

Yes, you are missing something. That variable is only updated during the 
inclusion of the toolset files not the inclusion of the Jamfiles. The 
Jamfiles are read in first, the toolset files are read in when targets 
are created from "within" the Jamfiles. So you are seeing the lingering 
effects of that global getting set.

-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim - Grafik/jabber.org