On 9 February 2012 19:32, Frank Birbacher <bloodymir.crap@gmx.net> wrote:
Am 06.01.12 00:06, schrieb Mateusz Loskot:
Then I have to wipe out C:\usr, go to branches/release/tools/build/v2 and run the BBv2 installation again:
I don't even "install" BBv2. I just run the engine/build.sh or .bat to build the bjam executable. Running this anywhere inside boost will automatically find the boost-build.jam file on top level. This way it will find the current BBv2 files.
When building my stuff against one or the other boost version I simply switch the BOOST_ROOT environment variable to the respective boost folder. The bjam executables may reside in the same path using a different name like "bjam_1_48". This should reduce the hassle of repeatedly installing BBv2.
Sounds like a good idea too. The only minor hassle is to make bjam/b2 executables visible findable in the PATH or one has to locate them using relative/absolute paths. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net