-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! 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. Frank -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: keyserver x-hkp://pool.sks-keyservers.net iEYEARECAAYFAk80H0YACgkQhAOUmAZhnmpmRACfYuOgdsRCWb971ZVXR0Hed9FT Uz4AnjqL67MLeeFsZJHAfnR8XedUp7Hw =BJAZ -----END PGP SIGNATURE-----