These can
either be put into make??™s environment as part of its command line, or put into your
shell??™s environment. The first technique is used when you wish to condition one of
these variables just once or so. The second is useful when a variable setting is needed
over and over during a prolonged development session.
The first technique looks like this:
% make CONFIG="-Q Server" FLAGS="-c"
Here, the CONFIG variable is used to set the location for your m4 build file, and the
FLAGS variable is used to pass any other command-line switches you need to the
Build program.
The second technique begins by conditioning your shell??™s environment variables:
setenv CONFIG "-Q Server" ?†? the C shell and derivatives
CONFIG="-Q Server" ; export CONFIG ?†? the Bourne shell and derivatives
This is the Title of the Book, eMatter Edition
Copyright ?© 2007 O??™Reilly & Associates, Inc. All rights reserved.
2.3 What??™s Where in the Source | 51
setenv FLAGS "-c" ?†? the C shell and derivatives
FLAGS="-c" ; export FLAGS ?†? the Bourne shell and derivatives
You will see the result of declaring these two environment variables when you run
the make(1) program, this time without having to specify those two variables in the
command line:
% make all
See ?§10.1 on page 346 for an overview of how Build works, and what the -c and -Q
switches do.
Pages:
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114