Roland Ver. 4.5 Informacje Techniczne Strona 162
- Strona / 212
- Spis treści
- BOOKMARKI
Oceniono. / 5. Na podstawie oceny klientów
152 GNU make
15.4 DESTDIR: Support for Staged Installs
DESTDIR is a variable prepended to each installed target file, like this:
$(INSTALL_PROGRAM) foo $(DESTDIR)$(bindir)/foo
$(INSTALL_DATA) libfoo.a $(DESTDIR)$(libdir)/libfoo.a
The DESTDIR variable is specified by the user on the make command line as an absolute
file name. For example:
make DESTDIR=/tmp/stage install
DESTDIR should be supported only in the install* and uninstall* targets, as those are
the only targets where it is useful.
If your installation step would normally install /usr/local/bin/foo and /usr/
local/lib/libfoo.a, then an installation invoked as in the example above would install
/tmp/stage/usr/local/bin/foo and /tmp/stage/usr/local/lib/libfoo.a instead.
Prepending the variable DESTDIR to each target in this way provides for staged installs,
where the installed files are not placed directly into their expected location but are instead
copied into a temporary location (DESTDIR). However, installed files maintain their relative
directory structure and any embedded file names will not be modified.
You should not set the value of DESTDIR in your Makefile at all; then the files are
installed into their expected locations by default. Also, specifying DESTDIR should not
change the operation of the software in any way, so its value should not be included in any
file contents.
DESTDIR support is commonly used in package creation. It is also helpful to users who
want to understand what a given package will install where, and to allow users who don’t
normally have permissions to install into protected areas to build and install before gaining
those permissions. Finally, it can be useful with tools such as stow, where code is installed
in one place but made to appear to be installed somewhere else using symbolic links or
special mount operations. So, we strongly recommend GNU packages support DESTDIR,
though it is not an absolute requirement.
15.5 Variables for Installation Directories
Installation directories should always be named by variables, so it is easy to install in a
nonstandard place. The standard names for these variables and the values they should
have in GNU packages are described below. They are based on a standard file system
layout; variants of it are used in GNU/Linux and other modern operating systems.
Installers are expected to override these values when calling make (e.g., make pre-
fix=/usr install or configure (e.g., configure --prefix=/usr). GNU packages should
not try to guess which value should be appropriate for these variables on the system they
are being installed onto: use the default settings specified here so that all GNU packages
behave identically, allowing the installer to achieve any desired layout.
All installation directories, and their parent directories, should be created (if necessary)
before they are installed into.
These first two variables set the root for the installation. All the other installation
directories should be subdirectories of one of these two, and nothing should be directly
installed into these two directories.
- 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
Powiązane produkty i podręczniki dla Drukuj i skanuj Roland Ver. 4.5
(26 strony)
Drukuj i skanuj Roland PC-12 Dokumentacja
(97 strony)
(97 strony)
© 2020, manymanuals.pl. Wszelkie prawa zastrzeżone. | 0.060 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Komentarze do niniejszej Instrukcji