Roland Ver. 4.5 Informações Técnicas Página 172
- Página / 212
- Índice
- MARCADORES
Avaliado. / 5. Com base em avaliações de clientes
162 GNU make
installdirs
It’s useful to add a target named ‘installdirs’ to create the directories
where files are installed, and their parent directories. There is a script called
mkinstalldirs which is convenient for this; you can find it in the Gnulib
package. You can use a rule like this:
# Make sure all installation directories (e.g. $(bindir))
# actually exist by making them if necessary.
installdirs: mkinstalldirs
$(srcdir)/mkinstalldirs $(bindir) $(datadir) \
$(libdir) $(infodir) \
$(mandir)
or, if you wish to support DESTDIR (strongly encouraged),
# Make sure all installation directories (e.g. $(bindir))
# actually exist by making them if necessary.
installdirs: mkinstalldirs
$(srcdir)/mkinstalldirs \
$(DESTDIR)$(bindir) $(DESTDIR)$(datadir) \
$(DESTDIR)$(libdir) $(DESTDIR)$(infodir) \
$(DESTDIR)$(mandir)
This rule should not modify the directories where compilation is done. It should
do nothing but create installation directories.
15.7 Install Command Categories
When writing the install target, you must classify all the commands into three categories:
normal ones, pre-installation commands and post-installation commands.
Normal commands move files into their proper places, and set their modes. They may
not alter any files except the ones that come entirely from the package they belong to.
Pre-installation and post-installation commands may alter other files; in particular, they
can edit global configuration files or data bases.
Pre-installation commands are typically executed before the normal commands, and
post-installation commands are typically run after the normal commands.
The most common use for a post-installation command is to run install-info. This
cannot be done with a normal command, since it alters a file (the Info directory) which
does not come entirely and solely from the package being installed. It is a post-installation
command because it needs to be done after the normal command which installs the package’s
Info files.
Most programs don’t need any pre-installation commands, but we have the feature just
in case it is needed.
To classify the commands in the install rule into these three categories, insert category
lines among them. A category line specifies the category for the commands that follow.
A category line consists of a tab and a reference to a special Make variable, plus an
optional comment at the end. There are three variables you can use, one for each category;
the variable name specifies the category. Category lines are no-ops in ordinary execution
because these three Make variables are normally undefined (and you should not define them
in the makefile).
Here are the three possible category lines, each with a comment that explains what it
means:
- GNU Make 1
- Short Contents 5
- Table of Contents 7
- 1 Overview of make 11
- 2 An Introduction to Makefiles 13
- 2.2 A Simple Makefile 14
- 2.6 Another Style of Makefile 18
- 3 Writing Makefiles 21
- 3.1.1 Splitting Long Lines 22
- 3.3 Including Other Makefiles 23
- 3.4 The Variable MAKEFILES 24
- 3.5 How Makefiles Are Remade 24
- 3.7 How make Reads a Makefile 26
- Conditional Directives 27
- Rule Definition 27
- 3.8 Secondary Expansion 28
- 4 Writing Rules 31
- 4.2 Types of Prerequisites 32
- 4.3.1 Wildcard Examples 33
- 4.3.3 The Function wildcard 34
- 4.4.2 The vpath Directive 36
- 4.5 Phony Targets 39
- 4.11 Static Pattern Rules 46
- 4.12 Double-Colon Rules 48
- %.d: %.c 49
- @set -e; rm -f $@; \ 49
- 5 Writing Recipes in Rules 51
- 5.2 Recipe Echoing 53
- 5.3 Recipe Execution 54
- 5.3.2 Choosing the Shell 55
- 5.4 Parallel Execution 57
- 5.5 Errors in Recipes 59
- 5.7 Recursive Use of make 60
- 5.8 Defining Canned Recipes 66
- 5.9 Using Empty Recipes 67
- 6 How to Use Variables 69
- 6.3.1 Substitution References 72
- 6.3.2 Computed Variable Names 73
- 6.5 Setting Variables 75
- 6.7 The override Directive 78
- 6.9 Undefining Variables 79
- 6.13 Suppressing Inheritance 82
- 6.14 Other Special Variables 83
- 7.1 Example of a Conditional 87
- 7.2 Syntax of Conditionals 88
- 8.1 Function Call Syntax 93
- 8.3 Functions for File Names 97
- 8.5 The foreach Function 100
- 8.6 The file Function 101
- 8.7 The call Function 102
- 8.8 The value Function 103
- 8.9 The eval Function 103
- 8.10 The origin Function 104
- 8.11 The flavor Function 105
- 8.14 The guile Function 107
- 8.13 The shell Function 107
- 9 How to Run make 109
- 9.5 Overriding Variables 113
- 9.7 Summary of Options 114
- 10 Using Implicit Rules 121
- 10.4 Chains of Implicit Rules 127
- 10.5.2 Pattern Rule Examples 129
- 10.5.3 Automatic Variables 130
- 10.5.4 How Patterns Match 132
- 10.7 Old-Fashioned Suffix Rules 135
- 12 Extending GNU make 143
- 12.2 Loading Dynamic Objects 145
- 12.2.1 The load Directive 146
- Loaded Object Licensing 147
- Data Structures 148
- Registering Functions 148
- Registered Function Interface 148
- GNU make Facilities 148
- Memory Management 149
- 12.2.4 Example Loaded Object 149
- 13 Features of GNU make 153
- 15 Makefile Conventions 159
- 15.2 Utilities in Makefiles 160
- CFLAGS = -g 161
- ALL_CFLAGS = -I. $(CFLAGS) 161
- Appendix A Quick Reference 175
- Index of Concepts 201
- 192 GNU make 202
- Index of Concepts 193 203
- 194 GNU make 204
- Index of Concepts 195 205
- 196 GNU make 206
- Index of Concepts 197 207
- 198 GNU make 208
- 200 GNU make 210
Manuais e produtos relacionados com Digitalizar e Imprimir Roland Ver. 4.5
(26 páginas)
Digitalizar e Imprimir Roland PC-12 Especificações
(97 páginas)
(97 páginas)
© 2020, manymanuals-pt.com. Todos os direitos reservados. | 0.045 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comentários a estes Manuais