|
|
|||||||||||||||||||||||||||||
![]() |
![]() |
||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||
|
|
|
|
|||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||
|
|
|
|
|||||||||||||||||||||||||||
|
4.1 Notices in
|
||||||||||||||||||||||||||||
AC_PREREQ(2.52) |
This macro is the only macro that may be used before AC_INIT, but
for consistency, you are invited not to do so.
configure are covered by the
copyright-notice.
The copyright-notice will show up in both the head of
configure and in `configure --version'.
configure
script, with any dollar signs or double-quotes removed. This macro lets
you put a revision stamp from `configure.ac' into configure
without RCS or cvs changing it when you check in
configure. That way, you can determine easily which revision of
`configure.ac' a particular configure corresponds to.
For example, this line in `configure.ac':
AC_REVISION($Revision: 1.30 $) |
produces this in configure:
#! /bin/sh # From configure.ac Revision: 1.30 |