On 6 January 2012 01:58, Robert Ramey <ramey@rrsd.com> wrote:
Mateusz Loskot wrote:
On 22 December 2011 01:49, Robert Ramey <ramey@rrsd.com> wrote: I have additional question to the testing against release branch approach.
I assume you work with trunk and branches/release in the same machine/system. How do you switch between Boost.Build from trunk and from branches/release?
On Windows, I build and install BBv2 this way:
bootstrap.bat .\b2 --prefix=C:\usr install
If C:\usr contains BBv2 from trunk (C:\usr\bin is in PATH) and I try to run b2 command inside branches/release, I sometimes get BBv2 errors (e.g. from .jam files).
Then I have to wipe out C:\usr, go to branches/release/tools/build/v2 and run the BBv2 installation again:
bootstrap.bat .\b2 --prefix=C:\usr install
It is quite a hassle. Is there any convenient way to have different version of BBv2 installed?
hmmm - I'm not aware of this issue. Here is what I do:
a) I have svn checked out from the release branch to a directory. On my windows system its c:\BoostRelease. b) Then I use svn switch to switch the serialization directories to the trunk. For the serialization library this is three directories. c:\BoostRelease\boost\archive, c:\BoostRelease\boost\serialization, c:\BoostRelease\libs\serialization
Yes, this is what I now do too, following your instructions: http://mateusz.loskot.net/?p=2887
c) if necessary, one can build using boost build v2 - I forget the procedure. But basically boost build is indifferent to whether it's the release or trunk.
When I have boost build v2 installed form trunk and I try to use it to test (any) libraries from branches/release, then I'm getting this: d:\dev\boost\_svn\branches\release\libs\serialization\test>b2 D:/dev/boost/_svn/branches/release/tools/build/v2/build\project.jam:266: unbalanced parentheses So, I have to reinstall boost build v2 from branches/release, then everything works.
I'm sure there are other ways to do this but that's how I do it. As I said before boost build and other tools work the same regardless of the branch
Perhaps there is a temporary issue in the trunk or simply it is my environment fault. Thanks for all your comments Robert, very helpful. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net