From: Austin Bingham (abingham_at_[hidden])
Date: 2003-10-15 09:17:19
> The problem is that "use-project" is allowed in Jamfile, too, and I think it's
> a good idea. It's still possible to make "use-project" work, anyway. I was
> wondering about use-cases for "use-project" where used project does not have
> a separate project-root.jam. In my settings, I use "use-project" for
> dependedies on boost, and some local, relatively standalone libraries, which
> all have their own project-root.jam. So I wonder if other case is reasonable/
> needed.
I used use-project fairly extensively to point to targets with the same
project-root to give flexibility when I was organizing my source files. It
gave me the freedom to move things around freely while minimizing the
ripple of changes. So, I guess that's one use case. It could also be
argued that, in the case of particularly deep project hierarchies,
use-project provides the best way to give make building those targets easy
(i.e. by giving them easy names).
> Of course, it is possible to delay processing of "use-project" directives
> until
Yes, that was sort of what I had in mind. Whatever module does the Jamfile
loading could always remember what it has already loaded...if a
use-project directive asks for it to be loaded again, it could just be
ignored. I worry that I'm missing some subtlety about Jamfile load order,
though.
Austin