Re: [Boost-build] [v2] header-only libs still too difficult

From: David Abrahams (dave_at_[hidden])
Date: 2006-03-13 03:39:58

Vladimir Prus <ghost_at_[hidden]> writes:

> On Friday 10 March 2006 01:57, David Abrahams wrote:
>> So I am trying to build some simple tests using Boost components.  My
>> Jamroot is:
>>
>>   use-project /boost : c:/boost ;
>>   run mytest.cpp ;
>>
>> But boost headers aren't in the #include path, so its usage
>> requirements aren't picked up.
>>
>> Okay, I think, I can add <source>/boost// to my project requirements.
>> But that makes bjam take forever to do nothing and I kill it.
>
> Supposedly, this tries to build all of boost, including globbing for all 
> headers, and what not.

Globbing for /headers/ !?!  Why?

> How about 
>
>    run mytest.cpp /boost//headers ;
>
> which is supposed to work right now.

Okay, I could try that.

>> So I add
>>
>>   alias boost : : <include>c:/boost ;
>
> This means that 'boost' alias will be built with <include>c:/boost in build 
> properties. To propagate this include, it's has to be in usage requirements, 
> like this:
>
>    alias headers : : : : <include>c:/boost ;

...Riiight...

>> This needs to be simpler! 
>
> We discussed this in
>
>    http://thread.gmane.org/gmane.comp.lib.boost.build/11375
>
> and I'm not quite sure if the ball is on your side or on mine.

Probably mine.  But the fact that I'm so confused about this to begin
with makes me nervous about trying to write the code.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com