1
Fork 0
mirror of https://git.savannah.gnu.org/git/guile.git synced 2025-04-30 03:40:34 +02:00

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.
This commit is contained in:
Greg J. Badros 2000-01-22 21:11:18 +00:00
parent 140b8e376b
commit b5f69988c1

12
HACKING
View file

@ -82,12 +82,12 @@ The Guile sources live in several modules:
There is a mailing list for CVS commit messages; see README for details. 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 - We check Makefile.am and configure.in files into CVS, but the
files they are built from (Makefile.am, configure.in); we do not check "autogen.sh" script must be run from the top-level to generate the
in Makefiles or header files generated by configuration scripts. The actual "configure" script that then must be run to create the various
general rule is that you should be able to check out a working Makefile-s to build guile. The general rule is that you should be able
directory of Guile from CVS, and then type "configure" and "make", to check out a working directory of Guile from CVS, and then type
without running any other tools. "./autogen.sh", then "configure", and finally "make".
- (Automake 1.4 only) Be sure to run automake at the top of the tree - (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 with no arguments. Do not use `automake Makefile' to regenerate