From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-05-19 08:42:03
On Thursday 18 May 2006 21:07, Ryan Gallagher wrote:
> Vladimir Prus <ghost <at> cs.msu.su> writes:
> > Do you have one main app that compiles all files in your project? That
> > would explain it -- it typically have one (or even several) libraries per
> > directory so the problem does not arise for me.
> This case actually arises mainly for libraries for me (but libraries are
> mainly what I write). I sometimes have one library that spans a couple
> directories, which correspond to namespaces. I suppose that I just don't
> get quite as fine-grained in these as you do.
> I admit though that this may be the result of being used to lesser
> build systems like MSVS that this fine grained nature causes much more
> pain to maintain. Perhaps with more experience using bbv2 I'd move to
> a finer grained approach, but currently the library layout I have choosen
> seems most natural to me.
> That being said, currently at least, I (and some others, obviously) still
> view this as a valuable feature.
Ehm... another bad corner case is this:
exe a : ../../a.cpp ../../foo/b.cpp ;
It's not apparent what target directories should be used in this case in order
for things to work sanely. I guess we need to outlaw this use-case.
-- Vladimir Prus http://vladimir_prus.blogspot.com Boost.Build V2: http://boost.org/boost-build2
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