2 ======= =======================================================================
4 ?MAKE: The ?MAKE: line records dependencies
6 ?MAKE:symbol list: dependency list [+optional]
8 This is the first dependency line. The first "symbol list"
9 should list all the symbols built by this unit (i.e. whose
10 value is computed by the shell section of the unit). Symbols
11 should be space separated. If a defined symbol is for internal
12 use only and should not appear in the generated "config.sh"
13 file, then it should be preceded by a '+' (not to be confused
14 with optional dependencies defined hereafter).
15 The second part of the list (after the middle ':') is the unit
16 dependency. It should list all the needed special units, as
17 well as all the symbols used by the shell implementation. If
18 a symbol is nedded but its configuration value is not critical,
19 it can be preceded by a '+', in which case it is called a
20 conditional dependency: its corresponding unit will be loaded
21 if, and only if, that symbol is otherwise really wanted;
22 otherwise the default value will be used.
26 There can be one or more command lines following the initial
27 dependency lines. Those commands will be executed when the
28 unit is wanted to load them into "Configure".
29 Note that the leading <tab> character is required before the
32 ?INIT: Initializations printed verbatim
34 ?LINT: Hints for metalint
36 set Listed variables are set
37 ?LINT:set d_getservprotos
38 describe Listed shell variables are described
39 ?LINT:describe awk ar bash bison byacc cat chgrp chmod chown
40 create Listed created files in regular units
42 known Listed C variables are described
44 change Shell variable ok to be changed
46 extern Variables known to be externally defined
48 usefile Files marked as being used
50 use Variables declared as used by unit
51 ?LINT:use PERL_CONFIG_SH
52 define Listed variables are defined
56 unclosed Unclosed here-documents
58 nothere Not a here-document name
59 nocomment OK if leading unit ': comment' missing
62 ?RCS: RCS comments are ignored
64 To be used for RCS comments, at the top of the unit.
70 ?D: Default value for conditional symbols
78 Defines what files are created by this module
80 Files produced in the UU directory and which are identified by the
81 convention ./filename. Files !filename are not produced, i.e. they are
82 temporary or externally provided.
84 ?F:cppstdin !testcpp.out !testcpp.c
86 ?H: Process the config.h lines
88 Defines the part to be included in the generated config_h.SH
90 To get #ifdefs in config_h.SH, you'll need strange constructs like
92 ?H:?%<:@if USE_SITECUSTOMIZE
93 ?H:?%<:#ifndef USE_SITECUSTOMIZE
94 ?H:?%<:#$usesitecustomize USE_SITECUSTOMIZE /**/
102 ?M: Process the confmagic.h lines
104 ?O: Unit obsolescence
106 ?P: Location of PD implementation file
110 ?S:symbol_name (obsolete symbol list)]:
112 Introduces a shell symbol. This first line names the symbol,
113 optionally followed by a list enclosed between parenthesis and
114 giving the obsolete equivalent. Those obsolete symbols will be
115 remapped to the new "symbol_name" if the -o option is given to
118 ?S: <tab> any text, for "Porting/Glossary"
120 Basically a comment describing the shell symbol, which will be
121 extracted by "makegloss" into the Glossary file.
125 Closes the shell symbol comment.
127 ?T: Shell temporaries used
129 What variables are used as temporary variables
131 ?V: Visible symbols like 'rp', 'dflt'
135 ?W: Wanted value for interpreter
137 ?X: User comment is ignored
139 General purpose comments. May appear anywhere in the unit but must be
140 left justfied. For RCS comments, please use the ?RCS: comment form.
142 ?Y: User-defined layout preference
144 Declare a layout directive for this unit. That directive may be one
145 of the strings "top", "default" or "bottom" (case does not matter,
146 recommended style is to spell them out uppercased). If omitted,
147 "default" is assumed.
149 This directive is only required if you wish to force a unit at the
150 top or the bottom of the generated "Configure" script, as unit
151 dependencies permit it. Important questions may thus be forced
152 at the beginning. Within the same layout class, units are sorted
153 alphabetically with two special cases for d_* and i_* units, forced
154 respectively at the top and bottom of their classes (but these
155 should belong to the default class).
157 It you force at the top a unit whose dependencies require all the
158 other unit to precede it, you achieve nothing interesting. Therefore,
159 that directive should really be used to increase the priority of
160 some interactive units that do not depend on many other user-visible
161 symbols, like path-related questions.
165 lines can be made conditional (see Config_sh.U)