Re: [jamboost] tooset flags problem

From: Vladimir Prus (ghost_at_[hidden])
Date: 2003-01-15 06:44:51

David Abrahams wrote:

>>$bjam gcc-3.2
>>...found 9 targets...
>>...updating 5 targets...
>>MkDir1 bin
>>MkDir1 bin/gcc-3.2
>>MkDir1 bin/gcc-3.2/debug
>>gcc.compile bin/gcc-3.2/debug/hello.o
>>hello.cpp:8:2: warning: no newline at end of file
>>gcc.link bin/gcc-3.2/debug/hello
>>
>>Isn't it the coolness?
> 
> 
> It *is* the coolness. However, I'm a bit surprised it worked, since
> the whole reason I changed gcc.jam was that it was still reporting
> <toolset-version> as invalid.

I though that your intention was not to make <toolset-version> valid,
but to make <toolset>gcc-3.2 valid. Now, toolset.flags accepts
<toolset>gcc-3.2, verifies that it's valid, and converts it into
normalized form, <toolset>gcc/<toolset-version>3.2
Therefore, there's no need to make <toolset-version>3.2 to be valid.

>>However, we've one problem still. Assume, that gcc-3.2 is never declared.
>>If you run
>>
>> bjam gcc-3.2
>>
>>in examples-v2/hello, you won't be told that property is invalid, but that
>>./hello cannot be build. Adding "--debug-generators" to the command line
>>shows that <toolset>gcc-3.2 is in build request. I guess the error
>>should be reported after calling build-request.expand, which call is on
>>build-system.jam, line 63.
>>
>>Dave, what do you think?
> 
> 
> I'm inclined to think that build-request.expand or one of the rules it
> calls ought to be validating properties as it goes along.

Oh, property.validate-property-set appears to be exactly what's needed.

- Volodya