blob: 31dcdf16404b608d4382fa17ebde3e17d4544630 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
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
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
|
<!--
__COPYRIGHT__
This file is processed by the bin/SConsDoc.py module.
See its __doc__ string for a discussion of the format.
-->
<tool name="msvc">
<summary>
Sets construction variables for the Microsoft Visual C/C++ compiler.
</summary>
<sets>
CCPDBFLAGS
CCPCHFLAGS
<!--CCCOMFLAGS-->
CC
CCFLAGS
CFLAGS
CCCOM
SHCC
SHCCFLAGS
SHCFLAGS
SHCCCOM
CXX
CXXFLAGS
CXXCOM
SHCXX
SHCXXFLAGS
SHCXXCOM
CPPDEFPREFIX
CPPDEFSUFFIX
INCPREFIX
INCSUFFIX
<!--STATIC_AND_SHARED_OBJECTS_ARE_THE_SAME-->
RC
RCFLAGS
RCCOM
BUILDERS
OBJPREFIX
OBJSUFFIX
SHOBJPREFIX
SHOBJSUFFIX
CFILESUFFIX
CXXFILESUFFIX
PCHPDBFLAGS
PCHCOM
</sets>
<uses>
CCCOMSTR
SHCCCOMSTR
CXXCOMSTR
SHCXXCOMSTR
PCH
PCHSTOP
PDB
</uses>
</tool>
<builder name="PCH">
<summary>
Builds a Microsoft Visual C++ precompiled header.
Calling this builder method
returns a list of two targets: the PCH as the first element, and the object
file as the second element. Normally the object file is ignored.
This builder method is only
provided when Microsoft Visual C++ is being used as the compiler.
The PCH builder method is generally used in
conjuction with the PCH construction variable to force object files to use
the precompiled header:
<example>
env['PCH'] = env.PCH('StdAfx.cpp')[0]
</example>
</summary>
</builder>
<builder name="RES">
<summary>
Builds a Microsoft Visual C++ resource file.
This builder method is only provided
when Microsoft Visual C++ or MinGW is being used as the compiler. The
<filename>.res</filename>
(or
<filename>.o</filename>
for MinGW) suffix is added to the target name if no other suffix is given.
The source
file is scanned for implicit dependencies as though it were a C file.
Example:
<example>
env.RES('resource.rc')
</example>
</summary>
</builder>
<cvar name="CCPCHFLAGS">
<summary>
Options added to the compiler command line
to support building with precompiled headers.
The default value expands expands to the appropriate
Microsoft Visual C++ command-line options
when the &cv-link-PCH; construction variable is set.
</summary>
</cvar>
<cvar name="CCPDBFLAGS">
<summary>
Options added to the compiler command line
to support storing debugging information in a
Microsoft Visual C++ PDB file.
The default value expands expands to appropriate
Microsoft Visual C++ command-line options
when the &cv-link-PDB; construction variable is set.
The Visual C++ compiler option that SCons uses by default
to generate PDB information is <option>/Z7</option>.
This works correctly with parallel (<option>-j</option>) builds
because it embeds the debug information in the intermediate object files,
as opposed to sharing a single PDB file between multiple object files.
This is also the only way to get debug information
embedded into a static library.
Using the <option>/Zi</option> instead may yield improved
link-time performance,
although parallel builds will no longer work.
You can generate PDB files with the <option>/Zi</option>
switch by overriding the default &cv-link-CCPDBFLAGS; variable as follows:
<example>
env['CCPDBFLAGS'] = ['${(PDB and "/Zi /Fd%s" % File(PDB)) or ""}']
</example>
An alternative would be to use the <option>/Zi</option>
to put the debugging information in a separate <filename>.pdb</filename>
file for each object file by overriding
the &cv-link-CCPDBFLAGS; variable as follows:
<example>
env['CCPDBFLAGS'] = '/Zi /Fd${TARGET}.pdb'
</example>
</summary>
</cvar>
<cvar name="MSVC_BATCH">
<summary>
When set to any true value,
specifies that &SCons; should batch
compilation of object files
when calling the Microsoft Visual C/C++ compiler.
All compilations of source files from the same source directory
that generate target files in a same output directory
and were configured in &SCons; using the same construction environment
will be built in a single call to the compiler.
Only source files that have changed since their
object files were built will be passed to each compiler invocation
(via the &cv-link-CHANGED_SOURCES; construction variable).
Any compilations where the object (target) file base name
(minus the <filename>.obj</filename>)
does not match the source file base name
will be compiled separately.
</summary>
</cvar>
<cvar name="PCH">
<summary>
The Microsoft Visual C++ precompiled header that will be used when compiling
object files. This variable is ignored by tools other than Microsoft Visual C++.
When this variable is
defined SCons will add options to the compiler command line to
cause it to use the precompiled header, and will also set up the
dependencies for the PCH file.
Example:
<example>
env['PCH'] = 'StdAfx.pch'
</example>
</summary>
</cvar>
<cvar name="PCHCOM">
<summary>
The command line used by the
&b-PCH;
builder to generated a precompiled header.
</summary>
</cvar>
<cvar name="PCHCOMSTR">
<summary>
The string displayed when generating a precompiled header.
If this is not set, then &cv-link-PCHCOM; (the command line) is displayed.
</summary>
</cvar>
<cvar name="PCHPDBFLAGS">
<summary>
A construction variable that, when expanded,
adds the <literal>/yD</literal> flag to the command line
only if the &cv-PDB; construction variable is set.
</summary>
</cvar>
<cvar name="PCHSTOP">
<summary>
This variable specifies how much of a source file is precompiled. This
variable is ignored by tools other than Microsoft Visual C++, or when
the PCH variable is not being used. When this variable is define it
must be a string that is the name of the header that
is included at the end of the precompiled portion of the source files, or
the empty string if the "#pragma hrdstop" construct is being used:
<example>
env['PCHSTOP'] = 'StdAfx.h'
</example>
</summary>
</cvar>
<cvar name="RC">
<summary>
The resource compiler used to build
a Microsoft Visual C++ resource file.
</summary>
</cvar>
<cvar name="RCCOM">
<summary>
The command line used to build
a Microsoft Visual C++ resource file.
</summary>
</cvar>
<cvar name="RCCOMSTR">
<summary>
The string displayed when invoking the resource compiler
to build a Microsoft Visual C++ resource file.
If this is not set, then &cv-link-RCCOM; (the command line) is displayed.
</summary>
</cvar>
<cvar name="RCFLAGS">
<summary>
The flags passed to the resource compiler by the RES builder.
</summary>
</cvar>
<cvar name="RCINCFLAGS">
<summary>
An automatically-generated construction variable
containing the command-line options
for specifying directories to be searched
by the resource compiler.
The value of &cv-RCINCFLAGS; is created
by appending &cv-RCINCPREFIX; and &cv-RCINCSUFFIX;
to the beginning and end
of each directory in &cv-CPPPATH;.
</summary>
</cvar>
<cvar name="RCINCPREFIX">
<summary>
The prefix (flag) used to specify an include directory
on the resource compiler command line.
This will be appended to the beginning of each directory
in the &cv-CPPPATH; construction variable
when the &cv-RCINCFLAGS; variable is expanded.
</summary>
</cvar>
<cvar name="RCINCSUFFIX">
<summary>
The suffix used to specify an include directory
on the resource compiler command line.
This will be appended to the end of each directory
in the &cv-CPPPATH; construction variable
when the &cv-RCINCFLAGS; variable is expanded.
</summary>
</cvar>
|