Re: Dependency targets

From: david.abrahams_at_[hidden]
Date: 2001-11-22 08:37:25

--- In jamboost_at_y..., Thomas Witt <witt_at_i...> wrote:
> 
> Hi,
> 
> Dependency targets (<lib>) seem to be restricted to the current 
project. 
> Currently errors like the following are generated for dependencies 
from other 
> projects. 

Hi Thomas,

Absolutely! That's part of my intention for the rewrite. It /would/ 
require setting up some notion of project identity, so that built 
targets could be segregated by which project they belong to, but I 
think that might be a good idea for other reasons.

> 
> I think they could be a convenient way to add libs from other 
boost build 
> managed projects like
> 
> exe a.out : 
> main.cpp 
> <lib>$(BOOST_ROOT)/libs/regex/build/libboost_regex$(SUFLIB)
> : : ;

Agreed, the system should work that way.

> This way always the correct lib is selected without the user 
having to fiddle 
> with the "neverending" path generated by the build system. Large 
projects 
> might not like to introduce this tight coupling but its convenient 
for 
> smaller ones.

Why would this be inappropriate for large projects?

-Dave