From: Zbynek Winkler (zw-bjam_at_[hidden])
Date: 2005-09-20 13:29:03
David Abrahams wrote:
>Zbynek Winkler <zw-bjam_at_[hidden]> writes:
>>> We recommend this approach: once you've set up a boost-build.jam
>>> file in a parent directory of the one in which you do most of
>>> your development, it should almost never be necessary to think
>>> about it again, and you won't be cluttering your environment
>>> with settings specific to a single tool.
>>To use bb2 I create a script in ~/bin directory (where my PATH points)
>>usually named "b" with this contents:
>>and use that to invoke bb2. It is hidden in the ~/bin dir along with a
>>bunch of other scripts of this kind so it clutters neither the
>>environment nor the home dir.
>Of course; It clutters the ~/bin directory instead ;-).
Something has to be cluttered ;-).
>I do something like that for BBv1, since there are so many
>command-line/env variables that can have an effect.
>Are you suggesting we add that recommendation to the docs, or are you
>just offering it up as a useful hint for other BB users, or...?
Primary as a useful hint. It allows to give different names to different
bb2 versions in order to have several installed at the same time. But if
you find it worth to be in the documentation, then go ahead :)
The nicest thing about it is that it always uses matching version of
bjam+bb2 (working with the assumption that the matching versions are in
the same tree). When I moved the bjam executable around I was never
sure, if it is m10, cvs from a half year ago or from yesterday...
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