bjam's need of boost-build.jam
Hi, Is there a way of specifying the boost-build dir in the top-level Jamfile of a project? It seems like it can only be done in the boost-build.jam file (using environment var is not an option here). Seems like a bit of a cludge to have to use yet another file to specify that. Thanks, Oliver
Oliver Schoenborn wrote:
Hi, Is there a way of specifying the boost-build dir in the top-level Jamfile of a project?
Not currently.
It seems like it can only be done in the boost-build.jam file (using environment var is not an option here). Seems like a bit of a cludge to have to use yet another file to specify that.
It's better than the previous kludge of specifying an environment variable. Although it will likely be possible in the future, we just have to drop support for Perforce/Jam and the current v1 of Boost.Build. The later is going to happen after the 1.33 release, and I wouldn't mind if we also did the former. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org
Rene Rivera wrote:
Oliver Schoenborn wrote:
Hi, Is there a way of specifying the boost-build dir in the top-level Jamfile of a project?
Not currently.
It seems like it can only be done in the boost-build.jam file (using environment var is not an option here). Seems like a bit of a cludge to have to use yet another file to specify that.
It's better than the previous kludge of specifying an environment variable.
Why is it better? An environment variable seems easier, unless you have two installations of Boost.Build. Jonathan
Jonathan Turkanis wrote:
Rene Rivera wrote:
Oliver Schoenborn wrote:
Hi, Is there a way of specifying the boost-build dir in the top-level Jamfile of a project?
Not currently.
It seems like it can only be done in the boost-build.jam file (using environment var is not an option here). Seems like a bit of a cludge to have to use yet another file to specify that.
It's better than the previous kludge of specifying an environment variable.
Why is it better? An environment variable seems easier, unless you have two installations of Boost.Build.
It's better because you can drop a "build" directory to your project, and put boost-build build ; to the boost-build.jam file. It will work without having all users of the software download Boost.Build and set environment variable. OTOH, environment variable is better if you have many projects using Boost.Build, and all users have Boost.Build already installed. - Volodya
Vladimir Prus wrote:
Jonathan Turkanis wrote:
Rene Rivera wrote:
Oliver Schoenborn wrote:
Hi, Is there a way of specifying the boost-build dir in the top-level Jamfile of a project?
It seems like it can only be done in the boost-build.jam file
It's better than the previous kludge of specifying an environment variable.
Why is it better? An environment variable seems easier, unless you have two installations of Boost.Build.
It's better because you can drop a "build" directory to your project, and put
boost-build build ;
to the boost-build.jam file. It will work without having all users of the software download Boost.Build and set environment variable.
OTOH, environment variable is better if you have many projects using Boost.Build, and all users have Boost.Build already installed.
Okay, thanks.
- Volodya
Jonathan
Vladimir Prus <ghost@cs.msu.su> writes:
Jonathan Turkanis wrote:
Rene Rivera wrote:
Oliver Schoenborn wrote:
Hi, Is there a way of specifying the boost-build dir in the top-level Jamfile of a project?
Not currently.
It seems like it can only be done in the boost-build.jam file (using environment var is not an option here). Seems like a bit of a cludge to have to use yet another file to specify that.
It's better than the previous kludge of specifying an environment variable.
Why is it better? An environment variable seems easier, unless you have two installations of Boost.Build.
It's better because you can drop a "build" directory to your project, and put
boost-build build ;
to the boost-build.jam file. It will work without having all users of the software download Boost.Build and set environment variable.
OTOH, environment variable is better if you have many projects using Boost.Build, and all users have Boost.Build already installed.
Not if they way they installed Boost.Build was to put a boost-build.jam file in their home or root directory, above where all their projects live. That's a very convenient arrangement and asking those people to set up an environment variable and maintain it is just an inconvenience. -- Dave Abrahams Boost Consulting www.boost-consulting.com
participants (5)
-
David Abrahams -
Jonathan Turkanis -
Oliver Schoenborn -
Rene Rivera -
Vladimir Prus