automake: Use Cases

1 
1 2.2 Use Cases for the GNU Build System
1 ======================================
1 
1 In this section we explore several use cases for the GNU Build System.
1 You can replay all of these examples on the ‘amhello-1.0.tar.gz’ package
1 distributed with Automake.  If Automake is installed on your system, you
1 should find a copy of this file in
1 ‘PREFIX/share/doc/automake/amhello-1.0.tar.gz’, where PREFIX is the
1 installation prefix specified during configuration (PREFIX defaults to
1 ‘/usr/local’, however if Automake was installed by some GNU/Linux
1 distribution it most likely has been set to ‘/usr’).  If you do not have
1 a copy of Automake installed, you can find a copy of this file inside
1 the ‘doc/’ directory of the Automake package.
1 
1    Some of the following use cases present features that are in fact
1 extensions to the GNU Build System.  Read: they are not specified by the
1 GNU Coding Standards, but they are nonetheless part of the build system
1 created by the Autotools.  To keep things simple, we do not point out
1 the difference.  Our objective is to show you many of the features that
1 the build system created by the Autotools will offer to you.
1 

Menu

1 
· Basic Installation          Common installation procedure
· Standard Targets            A list of standard Makefile targets
· Standard Directory Variables  A list of standard directory variables
· Standard Configuration Variables  Using configuration variables
· config.site                 Using a config.site file
· VPATH Builds                Parallel build trees
· Two-Part Install            Installing data and programs separately
· Cross-Compilation           Building for other architectures
· Renaming                    Renaming programs at install time
· DESTDIR                     Building binary packages with DESTDIR
· Preparing Distributions     Rolling out tarballs
· Dependency Tracking         Automatic dependency tracking
· Nested Packages             The GNU Build Systems can be nested
1