diff options
author | Greg J. Badros <gjb@cs.washington.edu> | 2000-01-22 21:11:18 +0000 |
---|---|---|
committer | Greg J. Badros <gjb@cs.washington.edu> | 2000-01-22 21:11:18 +0000 |
commit | b5f69988c1a65fb6b7baa2c15403efd108f0353a (patch) | |
tree | 5c7430845df2f7880d941eeb55719cc055641d19 /HACKING | |
parent | 140b8e376b8fed83f110e97b91618d7713b91e60 (diff) |
HACKING: I've updated it a bit to reflect the need to run autogen.sh,
etc. Further changes may be needed, but my commit at least corrects
the most flagrant problems.
Diffstat (limited to 'HACKING')
-rw-r--r-- | HACKING | 12 |
1 files changed, 6 insertions, 6 deletions
@@ -82,12 +82,12 @@ The Guile sources live in several modules: There is a mailing list for CVS commit messages; see README for details. -- We check Makefile.in and configure files into CVS, as well as the -files they are built from (Makefile.am, configure.in); we do not check -in Makefiles or header files generated by configuration scripts. The -general rule is that you should be able to check out a working -directory of Guile from CVS, and then type "configure" and "make", -without running any other tools. +- We check Makefile.am and configure.in files into CVS, but the +"autogen.sh" script must be run from the top-level to generate the +actual "configure" script that then must be run to create the various +Makefile-s to build guile. The general rule is that you should be able +to check out a working directory of Guile from CVS, and then type +"./autogen.sh", then "configure", and finally "make". - (Automake 1.4 only) Be sure to run automake at the top of the tree with no arguments. Do not use `automake Makefile' to regenerate |