1763 |
@section Outputting Files |
@section Outputting Files |
1764 |
|
|
1765 |
Every Autoconf script, e.g., @file{configure.ac}, should finish by |
Every Autoconf script, e.g., @file{configure.ac}, should finish by |
1766 |
calling @code{AC_OUTPUT}. That is the macro that generates |
calling @code{AC_OUTPUT}. That is the macro that generates and runs |
1767 |
@file{config.status}, which will create the @file{Makefile}s and any |
@file{config.status}, which will create the @file{Makefile}s and any |
1768 |
other files resulting from configuration. This is the only required |
other files resulting from configuration. This is the only required |
1769 |
macro besides @code{AC_INIT} (@pxref{Input}). |
macro besides @code{AC_INIT} (@pxref{Input}). |
1782 |
@ref{Configuration Links}, macro @code{AC_CONFIG_LINKS}), subdirectories |
@ref{Configuration Links}, macro @code{AC_CONFIG_LINKS}), subdirectories |
1783 |
to configure (see @ref{Subdirectories}, macro @code{AC_CONFIG_SUBDIRS}) |
to configure (see @ref{Subdirectories}, macro @code{AC_CONFIG_SUBDIRS}) |
1784 |
are honored. |
are honored. |
1785 |
|
|
1786 |
|
The location of your @code{AC_OUTPUT} invocation is the exact point |
1787 |
|
where configuration actions are taken: any code afterwards will be |
1788 |
|
executed by @code{configure} once @command{config.status} was run. If |
1789 |
|
you want to bind actions to @command{config.status} itself |
1790 |
|
(independently of whether @command{configure} is being run), see |
1791 |
|
@ref{Configuration Commands, , Running Arbitrary Configuration |
1792 |
|
Commands}. |
1793 |
@end defmac |
@end defmac |
1794 |
|
|
1795 |
Historically, the usage of @code{AC_OUTPUT} was somewhat different. |
Historically, the usage of @code{AC_OUTPUT} was somewhat different. |