From: anis_benyelloul (anis_benyelloul_at_[hidden])
Date: 2005-08-24 12:52:47
Essalam Alaikoum !
Just after having downloaded release 1.33.0 of boost, I decided to
properly setup my
new boost-enabled development environment, using Boost.Build V2 as my
primary build system for my daily work.
I soon ran into some problems I want to share.
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.
-2 Even for libraries actually possessing suitable Jamfiles.
Boost.ProgramOptions, for example,
defines a target named boost_program_options, forcing
redundant /boost/program_oprions//boost_program_options, more then
what I can type.
That was for shortcomings in boost libraries.
Also, I need the configuration to be global, I tried this as a site-
import project ;
project.initialize $(__name__) ; # Heu ? This is Chinese for me ...
project site-config ;
# I have installed boost top dir in /usr/local/boost, The following
# 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) ...
I have described how I tried to setup my developement environement,
but I may just be heading the worng
-- Anis Benyelloul
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