Roland Ver. 4.5 Informações Técnicas Página 167
- Página / 212
- Índice
- MARCADORES
Avaliado. / 5. Com base em avaliações de clientes
Chapter 15: Makefile Conventions 157
‘srcdir’ The directory for the sources being compiled. The value of this variable is
normally inserted by the configure shell script. (If you are using Autoconf,
use ‘srcdir = @srcdir@’.)
For example:
# Common prefix for installation directories.
# NOTE: This directory must exist when you start the install.
prefix = /usr/local
datarootdir = $(prefix)/share
datadir = $(datarootdir)
exec_prefix = $(prefix)
# Where to put the executable for the command ‘gcc’.
bindir = $(exec_prefix)/bin
# Where to put the directories used by the compiler.
libexecdir = $(exec_prefix)/libexec
# Where to put the Info files.
infodir = $(datarootdir)/info
If your program installs a large number of files into one of the standard user-specified
directories, it might be useful to group them into a subdirectory particular to that program.
If you do this, you should write the install rule to create these subdirectories.
Do not expect the user to include the subdirectory name in the value of any of the
variables listed above. The idea of having a uniform set of variable names for installation
directories is to enable the user to specify the exact same values for several different GNU
packages. In order for this to be useful, all the packages must be designed so that they will
work sensibly when the user does so.
At times, not all of these variables may be implemented in the current release of Autoconf
and/or Automake; but as of Autoconf 2.60, we believe all of them are. When any are
missing, the descriptions here serve as specifications for what Autoconf will implement. As
a programmer, you can either use a development version of Autoconf or avoid using these
variables until a stable release is made which supports them.
15.6 Standard Targets for Users
All GNU programs should have the following targets in their Makefiles:
‘all’ Compile the entire program. This should be the default target. This target need
not rebuild any documentation files; Info files should normally be included in
the distribution, and DVI (and other documentation format) files should be
made only when explicitly asked for.
By default, the Make rules should compile and link with ‘-g’, so that executable
programs have debugging symbols. Otherwise, you are essentially helpless in
the face of a crash, and it is often far from easy to reproduce with a fresh build.
‘install’ Compile the program and copy the executables, libraries, and so on to the file
names where they should reside for actual use. If there is a simple test to verify
that a program is properly installed, this target should run that test.
Do not strip executables when installing them. This helps eventual debugging
that may be needed later, and nowadays disk space is cheap and dynamic loaders
typically ensure debug sections are not loaded during normal execution. Users
that need stripped binaries may invoke the install-strip target to do that.
- 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.044 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comentários a estes Manuais