From: Tom Tromey <tromey@redhat.com>
Date: Fri, 17 Nov 1995 08:55:52 +0000 (+0000)
Subject: *** empty log message ***
X-Git-Tag: Release-0-25~282
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=cc299c217be65e910afca3704384169adaaada1d;p=thirdparty%2Fautomake.git

*** empty log message ***
---

diff --git a/automake.texi b/automake.texi
index 710c976e1..6eaf62bd8 100644
--- a/automake.texi
+++ b/automake.texi
@@ -153,7 +153,7 @@ A good example of a single directory package is AutoMake itself.
 A good example of a multiple directory package is GNU cpio.
 
 @node Programs
-@node Which Programs Are Built
+@section Which Programs Are Built
 
 In a directory containing source that gets built into a program (as
 opposed to a library), the @samp{PROGRAMS} variable is used:
@@ -190,7 +190,7 @@ You can do this using the @code{AM_PROGRAMS} variable.  Here is the
 relevant code from cpio:
 
 @example
-PROGRAMS = @PROGS@
+PROGRAMS = @@PROGS@@
 AM_PROGRAMS = cpio pax mt rmt
 @end example
 
@@ -210,41 +210,56 @@ Although there appears to be support in @code{automake} to allow a
 currently not recommended.  This support is still preliminary, and does
 not work.
 
+Eventually @code{automake} will be modified to ignore header files
+listed in ``_SOURCE'' definitions.  At that time the @samp{HEADERS}
+macro will go away.
+
 
 @node Scripts
+@section Programs Which are Scripts
 
 La.
 
 @node Libraries
+@section Building Libraries
 
 La.
 
 @node Libstuff
+@section Programs which are not User-Visible
 
 La.
 
 @node Docs
+@section Texinfo and Man Pages
 
-Note that @TeXinfo source must end in the @file{.texi} extension
+Note that Texinfo source must end in the @file{.texi} extension
 (@file{.texinfo} won't work)
 
 
 @node ANSI
+@section Automatic de-ANSI-fication of Source
 
 For.
 
+@node Install
+@section What Gets Installed
+
 @node Distribution
+@section Building a Release
 
 Today.
 
 @node Tags
+@section Interfacing to @code{etags}
 
 @node Extending
+@section When AutoMake Isn't Enough
 
 Sometimes AutoMake isn't enough.  Then you just lose.
 
 
-@node Invoking `automake'
+@node Invoking automake
 @chapter Using @code{automake} to Create @file{Makefile.in}
 
 There are basically two modes in which @code{automake} can be run.
@@ -262,5 +277,6 @@ notices that a @code{Makefile.in} is out of date.
 
 
 @node Some index
+@chapter Nothing yet
 
 @bye