Roland Ver. 4.5 Informações Técnicas Página 173

  • Descarregar
  • Adicionar aos meus manuais
  • Imprimir
  • Página
    / 212
  • Índice
  • MARCADORES
  • Avaliado. / 5. Com base em avaliações de clientes
Vista de página 172
Chapter 15: Makefile Conventions 163
$(PRE_INSTALL) # Pre-install commands follow.
$(POST_INSTALL) # Post-install commands follow.
$(NORMAL_INSTALL) # Normal commands follow.
If you don’t use a category line at the beginning of the install rule, all the commands
are classified as normal until the first category line. If you don’t use any category lines, all
the commands are classified as normal.
These are the category lines for uninstall:
$(PRE_UNINSTALL) # Pre-uninstall commands follow.
$(POST_UNINSTALL) # Post-uninstall commands follow.
$(NORMAL_UNINSTALL) # Normal commands follow.
Typically, a pre-uninstall command would be used for deleting entries from the Info
directory.
If the install or uninstall target has any dependencies which act as subroutines of
installation, then you should start each dependency’s commands with a category line, and
start the main target’s commands with a category line also. This way, you can ensure
that each command is placed in the right category regardless of which of the dependencies
actually run.
Pre-installation and post-installation commands should not run any programs except for
these:
[ basename bash cat chgrp chmod chown cmp cp dd diff echo
egrep expand expr false fgrep find getopt grep gunzip gzip
hostname install install-info kill ldconfig ln ls md5sum
mkdir mkfifo mknod mv printenv pwd rm rmdir sed sort tee
test touch true uname xargs yes
The reason for distinguishing the commands in this way is for the sake of making binary
packages. Typically a binary package contains all the executables and other files that need
to be installed, and has its own method of installing them—so it does not need to run the
normal installation commands. But installing the binary package does need to execute the
pre-installation and post-installation commands.
Programs to build binary packages work by extracting the pre-installation and post-
installation commands. Here is one way of extracting the pre-installation commands (the
-s option to make is needed to silence messages about entering subdirectories):
make -s -n install -o all \
PRE_INSTALL=pre-install \
POST_INSTALL=post-install \
NORMAL_INSTALL=normal-install \
| gawk -f pre-install.awk
where the file pre-install.awk could contain this:
$0 ~ /^(normal-install|post-install)[ \t]*$/ {on = 0}
on {print $0}
$0 ~ /^pre-install[ \t]*$/ {on = 1}
Vista de página 172
1 2 ... 168 169 170 171 172 173 174 175 176 177 178 ... 211 212

Comentários a estes Manuais

Sem comentários