|
Boost-Build : |
From: Konstantin M. Litvinenko (gclbb-jamboost_at_[hidden])
Date: 2003-05-27 04:04:54
Hello, Vladimir!
You wrote on Tue, 27 May 2003 11:47:36 +0400:
VP> Yes. The problem is rather simple. If you have
Maybe so, maybe not :)
VP> <library>@/boost/date_time/boost_date_time
VP> in usage requirements of "foo" then usage requirements of date_time
VP> will be applied only to targets that use "foo". The "foo" target
VP> will be built as usual. To achieve the effect you want, it's
VP> necessary to and
VP> <dependency>@/boost/date_time/boost_date_time
VP> to *requirements* section as well. That would signify that your
VP> library uses date_time library and usage requirement will be
VP> propagated.
All that you saying works as expect but .... What if I have three
targets lib tmp, lib foo, exe bar.
lib foo depends on lib tmp, and exe bar depends lib foo. If I add
<dependency>@/boost/date_time/boost_date_time
to lib tmp, than lib foo will build with boost/date_time defines. But
when I add to lib foo either <dependency> or <library> on lib tmp, lib foo
builds without boost/date_time defines. I don't want to add
<dependency>@/boost/date_time to lib foo explicitly. What am I doing wrong
?
VP> I've wrote a document which describe all this some time ago, but it
VP> never ended in docs :-(
I have found nothing about <dependency> in boost_build_v2.html form
cvs. Did I miss something?
With best regards, Konstantin M. Litvinenko aka Dark Angel. E-mail:
darkangel_at_[hidden]
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk