Date: 2001-11-22 08:37:25
--- In jamboost_at_y..., Thomas Witt <witt_at_i...> wrote:
> Dependency targets (<lib>) seem to be restricted to the current
> Currently errors like the following are generated for dependencies
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
> managed projects like
> exe a.out :
> : : ;
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
> might not like to introduce this tight coupling but its convenient
> smaller ones.
Why would this be inappropriate for large projects?
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