From: davidljung (jungdl_at_[hidden])
Date: 2004-02-17 17:36:11
I'm just trying to learn bjam and Boost.Build for
my own moderate sized project (~50Klines) - which doesn't use boost.
I've gotten it to build, but there are numerous things I can't figure
out how to do from the various docs scattered around (and I've limited
success at understanding the .jam sources in boost-build thus far).
Q1: Currently, bjam builds everything in the source tree. How can I
put something in project-root.jam (or whereever) to have everything
built in an entirely different directory?
I've tried every combination of ALL_LOCATE_TARGETS as a target var,
env variable etc. etc. (with only enough knowledge to be dangerous),
but nothing changes.
(a search of this group only turns up some messages about it being
broken at some time - I assume there is an alternative)
If you feeling generous & have some time, I've got some other
Q2: what's the best way to specify custom build options, paths etc.
Currently I'm using variable like
path-constant pname : /pathcomp/pathcomp
in project-root.jam. Is that a good approach?
Q3: Some library sets allow the appropriate cflags & ldflags to be
obtained by running shell commands like:
pkg-config gtkmm-2.0 --cflags
which gives (in my case):
-I/usr/include/pango-1.0 -I/usr/X11R6/include -I/usr/include/freetype2
is there an easy way to get that into the <includes> spec for a
(currently, I've just hard coded it (!))
Similarly for libraries to search & link.
Thanks for any help.
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