summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorKarl Berry <karl@freefriends.org>2008-07-28 07:27:55 -0700
committerKarl Berry <karl@freefriends.org>2008-07-28 07:27:55 -0700
commit27235dac13db81504b23c00e3e7429f8404057dd (patch)
tree93b1e1c696025c3d7f6600d2514da23dcbf17b11 /doc
parent0dfcde0c7d5d947b39269b6bb620614a0ed6be42 (diff)
downloadgnulib-27235dac13db81504b23c00e3e7429f8404057dd.tar.gz
autoupdate
Diffstat (limited to 'doc')
-rw-r--r--doc/standards.texi22
1 files changed, 15 insertions, 7 deletions
diff --git a/doc/standards.texi b/doc/standards.texi
index e28aa8f415..75205914e8 100644
--- a/doc/standards.texi
+++ b/doc/standards.texi
@@ -3,7 +3,7 @@
@setfilename standards.info
@settitle GNU Coding Standards
@c This date is automagically updated when you save this file:
-@set lastupdate June 10, 2008
+@set lastupdate July 25, 2008
@c %**end of header
@dircategory GNU organization
@@ -3774,15 +3774,23 @@ all GNU software.
Each GNU distribution should come with a shell script named
@code{configure}. This script is given arguments which describe the
kind of machine and system you want to compile the program for.
-
The @code{configure} script must record the configuration options so
that they affect compilation.
-One way to do this is to make a link from a standard name such as
-@file{config.h} to the proper configuration file for the chosen system.
-If you use this technique, the distribution should @emph{not} contain a
-file named @file{config.h}. This is so that people won't be able to
-build the program without configuring it first.
+The description here is the specification of the interface for the
+@code{configure} script in GNU packages. Many packages implement it
+using GNU Autoconf (@pxref{Top,, Introduction, autoconf, Autoconf})
+and/or GNU Automake (@pxref{Top,, Introduction, automake, Automake}),
+but you do not have to use these tools. You can implement it any way
+you like; for instance, by making @code{configure} be a wrapper around
+a completely different configuration system.
+
+Another way for the @code{configure} script to operate is to make a
+link from a standard name such as @file{config.h} to the proper
+configuration file for the chosen system. If you use this technique,
+the distribution should @emph{not} contain a file named
+@file{config.h}. This is so that people won't be able to build the
+program without configuring it first.
Another thing that @code{configure} can do is to edit the Makefile. If
you do this, the distribution should @emph{not} contain a file named