Lines Matching refs:commands

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
481 The Makefile commands should check whether the value of
658 The commands should create all the directories in which files are to be
698 commands into three categories: normal ones, @dfn{pre-installation}
699 commands and @dfn{post-installation} commands.  @xref{Install Command
727 The uninstallation commands are divided into three categories, just like
728 the installation commands.  @xref{Install Command Categories}.
807 To help make users aware of this, the commands for the special
957 @cindex pre-installation commands
958 @cindex post-installation commands
960 commands into three categories: normal ones, @dfn{pre-installation}
961 commands and @dfn{post-installation} commands.
963 Normal commands move files into their proper places, and set their
967 Pre-installation and post-installation commands may alter other files;
970 Pre-installation commands are typically executed before the normal
971 commands, and post-installation commands are typically run after the
972 normal commands.
981 Most programs don't need any pre-installation commands, but we have the
984 To classify the commands in the @code{install} rule into these three
986 specifies the category for the commands that follow.
999         $(PRE_INSTALL)     # @r{Pre-install commands follow.}
1000         $(POST_INSTALL)    # @r{Post-install commands follow.}
1001         $(NORMAL_INSTALL)  # @r{Normal commands follow.}
1005 rule, all the commands are classified as normal until the first category
1006 line.  If you don't use any category lines, all the commands are
1012         $(PRE_UNINSTALL)     # @r{Pre-uninstall commands follow.}
1013         $(POST_UNINSTALL)    # @r{Post-uninstall commands follow.}
1014         $(NORMAL_UNINSTALL)  # @r{Normal commands follow.}
1022 @emph{each} dependency's commands with a category line, and start the
1023 main target's commands with a category line also.  This way, you can
1027 Pre-installation and post-installation commands should not run any
1039 The reason for distinguishing the commands in this way is for the sake
1043 installation commands.  But installing the binary package does need to
1044 execute the pre-installation and post-installation commands.
1047 pre-installation and post-installation commands.  Here is one way of
1048 extracting the pre-installation commands (the @option{-s} option to