Re: [Boost-build] Project requirements acting weird

From: Ilya Sokolov (fal_delivery_at_[hidden])
Date: 2006-05-13 10:00:42

Ilya Sokolov wrote:
> Emil Dotchevski wrote:
> 
>>The problem with user-config or site-config is that the <cflags> I need 
>>propagated are warnings, and that they differe for release and debug.
>>
>>Besides, I think you're incorrect when you say that <cflags> are not 
>>propagated, because like I said in my original post, with my setup they are 
>>propagated sometimes. Here is my setup:
>>
>>Jamroot
>>    |
>>    +--- Jamfile 1
>>            |
>>            +--- Jamfile 2
>>                       |
>>                       + Jamfile 3
>>
>>If I put the <cflags> that disable warnings in the project defined in 
>>Jamroot, or in Jamfile2, or in Jamfile3, it all works fine, and I can see
>>the flags on the command line when compiling Jamfile3 .cpp files.
>>
>>But if I put them in Jamfile1, then they don't get propagated. Am I 
>>experiencing a bug? What's the correct behavior here, are you sure that the 
>>intention was not to propagate <cflags>?
> 
> 
> from builtin.jam:
> 
> feature cflags : : free ;
> feature cxxflags : : free ;
> 
> it's quite possible that you found a bug.
> what version of bb2?
> can you create a test case?

i was confused. feature propagation (to dependencies) is differ from 
project attributes propagation (to child projects). where you put 
<cflags> in your jamfile1?