Re: Seting up boost-enabled development environement

From: David Abrahams (dave_at_[hidden])
Date: 2005-09-01 13:28:01

Vladimir Prus <ghost_at_[hidden]> writes:

> On Wednesday 24 August 2005 21:52, anis_benyelloul wrote:
>> Essalam Alaikoum !
>
> Hi Anis,
>
>> I want my system to be readily boost-enabled for all my projects
>> (which themselves use Boost.Build V2), i.e.
>> I'd expect to be able to write Jamroot files like :
>>
>> myproj : a.cpp b.cpp
>> c.cpp /boost/utility//utility /boost/program_options//program_options
>> ;
>>
>> Without having to repeat some special configuration for every project
>> I start: /boost/utility//utility should just work.
>>
>> Unfortunately, I wasn't able to achieve that.
>> -1 There is no target named "utility" for Boost.Utility. Ok,
>> Boost.Utility is a header only library, but
>> it should nontheless have some Jamefile to enable
>> the /boost/utility//utility syntax.
>
> I assumed that for header-only libraries you'd just use
>
> /boost//headers
>
> If using many header only library, it will become highly reduntant
> to specify them all.

I would rather do that and gain some assurance that my project will
still work when the library stops being header-only. You can, after
all, use aliases to group them.

>> -2 Even for libraries actually possessing suitable Jamfiles.
>> Boost.ProgramOptions, for example,
>> defines a target named boost_program_options, forcing
>> some
>> highly
>> redundant /boost/program_oprions//boost_program_options, more then
>> what I can type.
>
> Point taken. I believe nothing prevents us from making nicer aliases, like:
>
> /boost//program_options
>
> I've added this to 
> http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl?Boost.Build_V2/Todo

Nice.

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