Re: Boost.Build V2, Milestone 9 released

From: Kirill Lapshin (klapshin_at_[hidden])
Date: 2003-11-07 21:41:31

Ok, I found what caused the problem, though still have no idea why 
upgrading to m9.1 triggered it. Apparently it was built incorrectly 
before, and m9.1 simply revealed that. Still I don't understand how to 
fix it.

Anyway, here is what happened. In my root project I have global 
requirement <define>BOOST_DISABLE_WIN32, also I use boost libraries via 
use-project. Apparently requirements are not transferred through 
use-project directive, so I end up linking with boost libraries compiled 
without <define>BOOST_DISABLE_WIN32 and linking them with my code where 
define is present. Recipe for disaster.

Now the question is, what is a correct way to use project, in such way 
that it will pick up requirements of my project? I can probably use 
build-project, but this will build all boost libraries even though I am 
using just a couple of them. I can edit boost/config/user.hpp, but it 
would be nice to be able to express this using build system.

--Kirill

PS: I attached test case, just in case if someone wants to take a look...
 --------------070703010902080208020100 Content-Type: application/octet-stream;
name="test-m9.1.tar.bz2"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="test-m9.1.tar.bz2"

[Attachment content not displayed.] --------------070703010902080208020100--