[Gc]: Dependency tracking for configuration macros

Petter Urkedal urkedal at nbi.dk
Fri Sep 25 12:52:57 PDT 2009


On 2009-09-25, Boehm, Hans wrote:
> I think the usual policy is to check in enough files that both:
> 
> 1) Developers can regenerate everything that's not manually written, provided they install the appropriate autottools packages.
> 
> 2) Users can type configure; make and have the collector build.  In the case cp Makefile.direct Makefile; make should also work.

Or type "make -f Makefile.direct".  I attach a documentation patch, but
you may want to rewrite it yourself.
 
> I think we want the latter to work from a direct cvs check-out as well, since we want users to be able to build the CVS version without installing autotools.

Okay.  In that case I think we need to keep most of the files.  The
generated *.m4 files (aclocal.m4 and libtools.m4) could be removed
according to that policy, but I'm not sure what the common practice is.
-------------- next part --------------
diff --git a/README.QUICK b/README.QUICK
index 5ffa505..d7fed67 100644
--- a/README.QUICK
+++ b/README.QUICK
@@ -28,7 +28,8 @@ INSTALLATION:
 Under UN*X, Linux:
 Alternative 1 (the old way): type "make test" in this directory.
 	Link against gc.a.  With the most recent GC distributions
-	you may have to copy Makefile.direct to Makefile first.
+	you may have to type "make -f Makefile.direct test" or
+	copy Makefile.direct to Makefile first.
 
 Alternative 2 (the new way): type
 	"./configure --prefix=<dir>; make; make check; make install".


More information about the Gc mailing list