On Fri, May 25, 2001 at 10:31:56AM -0400, Greg Hudson wrote:
> Moreover, having a single Makefile is less functional in that you
> can't run "make" in a subdirectory to build only targets in that
> subdirectory, as is often convenient. (And it's not just convenient
> to save runtime; it's convenient because (1) the world isn't an
> optimal place, and sometimes the build blows out in a directory you
> didn't care about, and it's easier to just build subcomponents than to
> fix the problem, and (2) you're often already in the subdir in a
> previously completed build tree, making some change, and don't want to
> jump back to the top level to test it.)
With recursive make, you can type make in a subdirectory and get just
that directory, and I agree that's useful, but when you are at the top
directory you cannot make specific targets in the recursive makefiles.
One makefile basically ignores directories, but recursive makefiles
artificially hide their contents. Personally, I have had much better
luck with a single makefile than with recursive makefiles, but a fair
amount probably depends on personal style.
Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:30 2006