Roland Ver. 4.5 Technical Information Seite 163
- Seite / 212
- Inhaltsverzeichnis
- LESEZEICHEN
Bewertet. / 5. Basierend auf Kundenbewertungen
Chapter 15: Makefile Conventions 153
prefix A prefix used in constructing the default values of the variables listed below.
The default value of prefix should be /usr/local. When building the com-
plete GNU system, the prefix will be empty and /usr will be a symbolic link
to /. (If you are using Autoconf, write it as ‘@prefix@’.)
Running ‘make install’ with a different value of prefix from the one used to
build the program should not recompile the program.
exec_prefix
A prefix used in constructing the default values of some of the variables listed
below. The default value of exec_prefix should be $(prefix). (If you are
using Autoconf, write it as ‘@exec_prefix@’.)
Generally, $(exec_prefix) is used for directories that contain machine-specific
files (such as executables and subroutine libraries), while $(prefix) is used
directly for other directories.
Running ‘make install’ with a different value of exec_prefix from the one
used to build the program should not recompile the program.
Executable programs are installed in one of the following directories.
bindir The directory for installing executable programs that users can run. This should
normally be /usr/local/bin, but write it as $(exec_prefix)/bin. (If you are
using Autoconf, write it as ‘@bindir@’.)
sbindir The directory for installing executable programs that can be run from the shell,
but are only generally useful to system administrators. This should normally
be /usr/local/sbin, but write it as $(exec_prefix)/sbin. (If you are using
Autoconf, write it as ‘@sbindir@’.)
libexecdir
The directory for installing executable programs to be run by other programs
rather than by users. This directory should normally be /usr/local/libexec,
but write it as $(exec_prefix)/libexec. (If you are using Autoconf, write it
as ‘@libexecdir@’.)
The definition of ‘libexecdir’ is the same for all packages, so you should
install your data in a subdirectory thereof. Most packages install their data un-
der $(libexecdir)/package-name/, possibly within additional subdirectories
thereof, such as $(libexecdir)/package-name/machine/version.
Data files used by the program during its execution are divided into categories in two
ways.
• Some files are normally modified by programs; others are never normally modified
(though users may edit some of these).
• Some files are architecture-independent and can be shared by all machines at a site;
some are architecture-dependent and can be shared only by machines of the same kind
and operating system; others may never be shared between two machines.
This makes for six different possibilities. However, we want to discourage the use of
architecture-dependent files, aside from object files and libraries. It is much cleaner to
make other data files architecture-independent, and it is generally not hard.
- 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
Verwandte Produkte und Handbücher für Drucken & Scannen Roland Ver. 4.5
Drucken & Scannen Roland PC-12 Spezifikationen
(97 Seiten)
(97 Seiten)
Drucken & Scannen Roland AJ-1000 Bedienungsanleitung
(128 Seiten)
(128 Seiten)
Drucken & Scannen Roland VS-540i Bedienungsanleitung
(176 Seiten)
(176 Seiten)
© 2020, manymanuals.de. Alle Rechte vorbehalten. | 0.098 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Kommentare zu diesen Handbüchern