Boost logo

Boost-Build :

From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-09-01 02:17:19

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


If using many header only library, it will become highly reduntant
to specify them all.

> -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:


I've added this to

> That was for shortcomings in boost libraries.
> Also, I need the configuration to be global, I tried this as a site-
> config.jam :
> #
> # site-config.jam
> #
> import project ;
> project.initialize $(__name__) ; # Heu ? This is Chinese for me ...

1. $(__name__) is just the name of the current module.
2. You don't need the above two lines at all, in 1.33 version.

> project site-config ;
> # I have installed boost top dir in /usr/local/boost, The following
> line aims
> # to install a project id for the top level boost Jamfile
> use-project /boost : /usr/local/boost ;
> Unfortunatly, this didn't work either.. (probably due to my lack of
> knowledge of Jam language) and
> bjam isn't able to find sub Jamfiles/projects in the boost top dir,
> (even existing ones) ...

Should work. Can you try without "project.initialize" line?

- Volodya

Vladimir Prus
Boost.Build V2:

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at