From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-09-08 05:02:37
On Thursday 01 September 2005 22:28, David Abrahams wrote:
> >> 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.
Should we create a target for each subdirectory of "libs"? Should work fine,
except for algorithm/string and numeric/..., but that can be fixed manually.
> >> -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.Buil
Now implemented for all compiled libraries.
-- Vladimir Prus http://vladimir_prus.blogspot.com Boost.Build V2: http://boost.org/boost-build2
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk