Re: [Boost-build] Project requirements acting weird

From: Emil Dotchevski (emildotchevski_at_[hidden])
Date: 2006-05-13 14:44:58

Here is what the documentation has to say about this:

"Projects inherit all attributes (such as requirements) from their parents. 
Inherited requirements are combined with
any requirements specified by the sub-project."

I guess I incorrectly used the word "propagated" while I should have said 
"inherited". So let me perephrase my original question:

Here is my setup:

Jamroot
    |
    +--- Jamfile 1
            |
            +--- Jamfile 2
                       |
                       + Jamfile 3

And here is my problem:

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 *inherited*. Is this a 
bug? Am I doing something wrong?

Thanks,
Emil

----- Original Message ----- 
From: "Ilya Sokolov" <fal_delivery_at_[hidden]>
To: <boost-build_at_[hidden]>
Sent: Saturday, May 13, 2006 12:13 AM
Subject: Re: [Boost-build] Project requirements acting weird

> 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?
>
> _______________________________________________
> Unsubscribe & other changes: 
> http://lists.boost.org/mailman/listinfo.cgi/boost-build
>