binutils/etc/make-stds.texi

44 * Install Command Categories::  Three categories of commands in the `install'
145 Write the Makefile commands (and any shell scripts, such as
210 Makefiles should provide variables for overriding certain commands, options,
237 compilation commands or by defining an implicit rule, like this:
266 commands for actual installation, for executables and nonexecutables
288 the installation commands.  Use a separate command for each file to be
471 The Makefile commands should check whether the value of
589 The commands should create all the directories in which files are to be
629 commands into three categories: normal ones, @dfn{pre-installation}
630 commands and @dfn{post-installation} commands.  @xref{Install Command
640 The uninstallation commands are divided into three categories, just like
641 the installation commands.  @xref{Install Command Categories}.
711 To help make users aware of this, the commands for the special
844 @cindex pre-installation commands
845 @cindex post-installation commands
847 commands into three categories: normal ones, @dfn{pre-installation}
848 commands and @dfn{post-installation} commands.
850 Normal commands move files into their proper places, and set their
854 Pre-installation and post-installation commands may alter other files;
857 Pre-installation commands are typically executed before the normal
858 commands, and post-installation commands are typically run after the
859 normal commands.
868 Most programs don't need any pre-installation commands, but we have the
871 To classify the commands in the @code{install} rule into these three
873 specifies the category for the commands that follow.
886         $(PRE_INSTALL)     # @r{Pre-install commands follow.}
887         $(POST_INSTALL)    # @r{Post-install commands follow.}
888         $(NORMAL_INSTALL)  # @r{Normal commands follow.}
892 rule, all the commands are classified as normal until the first category
893 line.  If you don't use any category lines, all the commands are
899         $(PRE_UNINSTALL)     # @r{Pre-uninstall commands follow.}
900         $(POST_UNINSTALL)    # @r{Post-uninstall commands follow.}
901         $(NORMAL_UNINSTALL)  # @r{Normal commands follow.}
909 @emph{each} dependency's commands with a category line, and start the
910 main target's commands with a category line also.  This way, you can
914 Pre-installation and post-installation commands should not run any
926 The reason for distinguishing the commands in this way is for the sake
930 installation commands.  But installing the binary package does need to
931 execute the pre-installation and post-installation commands.
934 pre-installation and post-installation commands.  Here is one way of
935 extracting the pre-installation commands:
954 The resulting file of pre-installation commands is executed as a shell