|
1 <?xml version="1.0" encoding="utf-8"?> |
|
2 <!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. --> |
|
3 <!-- This component and the accompanying materials are made available under the terms of the License |
|
4 "Eclipse Public License v1.0" which accompanies this distribution, |
|
5 and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". --> |
|
6 <!-- Initial Contributors: |
|
7 Nokia Corporation - initial contribution. |
|
8 Contributors: |
|
9 --> |
|
10 <!DOCTYPE concept |
|
11 PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> |
|
12 <concept id="GUID-E4447BEF-33D2-5099-BCC1-C72FBB3B0463" xml:lang="en"><title>BUILDROM</title><prolog><metadata><keywords/></metadata></prolog><conbody> |
|
13 <p>BUILDROM is the Symbian platform ROM configuration tool. It is |
|
14 a unified ROM building front end to prepare the configurations. It |
|
15 then invokes the ROMBUILD to generate the ROM image or ROFSBUILD to |
|
16 generate the ROFS image. </p> |
|
17 <section id="GUID-3E50F8DA-36D3-5E3D-B229-F841EF4AC47D"><title>BUILDROM |
|
18 command syntax</title><p>If the OBY files are encoded in UTF-8 with |
|
19 non-ASCII character support, use the following the BUILDROM command |
|
20 syntax:</p><codeblock id="GUID-379818BF-A17B-5CAF-A311-3EE4142EE51D-GENID-1-2-1-8-1-1-6-1-1-4-1-2-2-3" xml:space="preserve">BUILDROM [options] <–oby-charset=utf-8 obyfile > [<obeyfile2> [obeyfile3 [...</codeblock><p>If the OBY files are encoded in local character set |
|
21 with non-ASCII character support, use the following the BUILDROM command |
|
22 syntax:</p><codeblock id="GUID-379818BF-A17B-5CAF-A311-3EE4142EE51D-GENID-1-2-1-8-1-1-6-1-1-4-1-2-2-5" xml:space="preserve">BUILDROM [options] <obeyfile1> [<obeyfile2> [obeyfile3 [...</codeblock><p> <codeph>options</codeph> can be one or more of the following: </p> <table id="GUID-F50B15E9-AA5A-5946-9FD5-024287F2FD6C"> |
|
23 <tgroup cols="2"><colspec colname="col0" colwidth="1.00*"/><colspec colname="col1" colwidth="1.00*"/> |
|
24 <tbody> |
|
25 <row> |
|
26 <entry><p> <codeph>–argfile=<parameter file></codeph> </p> </entry> |
|
27 <entry><p>Accepts a parameter file, which contains a list of command-line |
|
28 parameters specific to the ROM tools, as input. </p></entry> |
|
29 </row> |
|
30 <row> |
|
31 <entry><p> <codeph> -Dxxx </codeph> </p> </entry> |
|
32 <entry><p>C++ preprocessor arguments. A common, but not exhaustive |
|
33 set is: </p><p><table id="GUID-0FD13125-051C-515A-B595-525B6C03CEA7"> |
|
34 <tgroup cols="2"><colspec colname="col0"/><colspec colname="col1"/> |
|
35 <tbody> |
|
36 <row> |
|
37 <entry><p> <codeph>-D_DEBUG</codeph> </p></entry> |
|
38 <entry><p>Selects debug versions of some files. </p></entry> |
|
39 </row> |
|
40 <row> |
|
41 <entry><p> <codeph> -D_FULL_DEBUG</codeph> </p></entry> |
|
42 <entry><p>Selects debug versions of all files. </p></entry> |
|
43 </row> |
|
44 <row> |
|
45 <entry><p> <codeph>-D_ARM4T</codeph> </p></entry> |
|
46 <entry><p>Specifies the target platform. </p></entry> |
|
47 </row> |
|
48 <row> |
|
49 <entry><p> <codeph>-D_KABI=xxxx</codeph> </p> </entry> |
|
50 <entry><p>Specifies the target platform for the kernel (for example, |
|
51 ARMv5). </p></entry> |
|
52 </row> |
|
53 <row> |
|
54 <entry><p> <codeph>-D_EABI=xxxx</codeph> </p> </entry> |
|
55 <entry><p>Specifies the target for all files (for example, ARMv5). </p></entry> |
|
56 </row> |
|
57 <row> |
|
58 <entry><p> <codeph>-DFEATUREVARIANT=xxxx</codeph> </p> </entry> |
|
59 <entry><p>Specifies the name of feature-based variant (for example, |
|
60 myvar). </p> <p>BUILDROM automatically looks for the binary names |
|
61 and properties of the selected variant, using the data generated by |
|
62 build system. </p></entry> |
|
63 </row> |
|
64 <row> |
|
65 <entry><p>-D_NAND2 </p> </entry> |
|
66 <entry><p>Specifies to generate the image for NAND flash. </p></entry> |
|
67 </row> |
|
68 <row> |
|
69 <entry><p>-D_ONENAND </p> </entry> |
|
70 <entry><p>Specifies to generate the image for ONENAND flash. </p></entry> |
|
71 </row> |
|
72 </tbody> |
|
73 </tgroup> |
|
74 </table> </p></entry> |
|
75 </row> |
|
76 <row> |
|
77 <entry><p> <codeph>-lowmem</codeph> </p></entry> |
|
78 <entry><p>Reduces the physical memory consumption during image generation. </p></entry> |
|
79 </row> |
|
80 <row> |
|
81 <entry><p> <codeph>-loglevel<level></codeph> </p> </entry> |
|
82 <entry><p>Level of information to log file. The following valid log |
|
83 levels are available: </p> <p><table id="GUID-8275A5E1-141E-56B3-8202-51377AD7CAA4"> |
|
84 <tgroup cols="2"><colspec colname="col0"/><colspec colname="col1"/> |
|
85 <tbody> |
|
86 <row> |
|
87 <entry><p> <codeph>0</codeph> </p> </entry> |
|
88 <entry><p>Default level of information to log file. </p> </entry> |
|
89 </row> |
|
90 <row> |
|
91 <entry><p> <codeph>1</codeph> </p> </entry> |
|
92 <entry><p>Logs the host or the ROM filenames, the file size, and the |
|
93 hidden attribute in addition to the <codeph>loglevel 0</codeph> information. </p> </entry> |
|
94 </row> |
|
95 <row> |
|
96 <entry><p> <codeph>2</codeph> </p> </entry> |
|
97 <entry><p>Logs the E32 file header attributes such as UIDs, data size, |
|
98 heap size, stack size, VID, SID, and priority in addition to the <codeph>loglevel 1</codeph> information. </p> </entry> |
|
99 </row> |
|
100 </tbody> |
|
101 </tgroup> |
|
102 </table> </p></entry> |
|
103 </row> |
|
104 <row> |
|
105 <entry><p> <codeph>-nospi </codeph> </p> </entry> |
|
106 <entry><p>Instructs <codeph>BUILDROM</codeph> not to produce any static |
|
107 plug-in information (<codeph>.spi</codeph>) files. See the <xref href="GUID-A27BD4D8-8B0E-57C8-9C15-736109297DEA.dita#GUID-A27BD4D8-8B0E-57C8-9C15-736109297DEA/GUID-92EAD7F7-6524-57BF-9417-B455AF469C7A">__ECOM_PLUGIN</xref> keyword for details of these files. The default |
|
108 is to produce <codeph>.spi</codeph> files. </p></entry> |
|
109 </row> |
|
110 <row> |
|
111 <entry><p> <codeph>-noimage</codeph> </p> </entry> |
|
112 <entry><p>Instructs <codeph>BUILDROM</codeph> to suppress only the |
|
113 generation of any ROM or ROFS images, while allowing generation of |
|
114 all other relevant files. </p></entry> |
|
115 </row> |
|
116 <row> |
|
117 <entry><p> <codeph> -o<image name> </codeph> </p> </entry> |
|
118 <entry><p>The name of the ROM image. This overrides any name specified |
|
119 using the <xref href="GUID-43852F38-4841-5E6F-927B-A38ED4424F0C.dita#GUID-43852F38-4841-5E6F-927B-A38ED4424F0C/GUID-29BEF45C-2361-5245-9184-0261B99B6FB1">romname</xref> keyword in an Obey file. </p></entry> |
|
120 </row> |
|
121 <row> |
|
122 <entry><p> <codeph> -s </codeph> </p> </entry> |
|
123 <entry><p>The strict option. Specifying this means that any missing |
|
124 files will stop <codeph>BUILDROM</codeph> without generating a ROM |
|
125 image. </p> <p>If this option is not specified, then it is possible |
|
126 to generate a ROM image with missing files. </p></entry> |
|
127 </row> |
|
128 <row> |
|
129 <entry><p> <codeph>-p</codeph> </p> </entry> |
|
130 <entry><p>Preserves the intermediate files and folders (data drive |
|
131 and <codeph>Z</codeph> drive) generated by BUILDROM. </p></entry> |
|
132 </row> |
|
133 <row> |
|
134 <entry><p> <codeph>-e</codeph> </p> </entry> |
|
135 <entry><p>Specifies the external tools that need to be invoked. These |
|
136 are the names of the Perl modules (without the .pm extension). Multiple |
|
137 modules names must be separated by commas. This is an optional parameter. </p> <p>Alternatively, external tools can be invoked by using IBY file |
|
138 keyword <xref href="GUID-A27BD4D8-8B0E-57C8-9C15-736109297DEA.dita#GUID-A27BD4D8-8B0E-57C8-9C15-736109297DEA/GUID-A71135A8-C6A6-50DB-8081-8CCD5B6AC0CB">externaltool</xref>. </p></entry> |
|
139 </row> |
|
140 <row> |
|
141 <entry><p> <codeph>-fm</codeph> =<<varname>feature_manager_database_file</varname> ><filepath>.xml</filepath> </p> </entry> |
|
142 <entry><p>Parses the specified feature manager database XML files |
|
143 and generates the features data file(s) (<filepath>features.dat</filepath>) in the present working directory. The number of <filepath>features.dat</filepath> files generated depends on the total number of ROM image partitions |
|
144 specified in the OBEY file that is used to create the ROM image. </p> <p> <b>Notes</b> </p> <ul> |
|
145 <li id="GUID-F229ED73-75AF-519F-9121-62E2D340D945"><p>You can provide |
|
146 multiple feature manager database XML files delimited by commas. </p> </li> |
|
147 <li id="GUID-885CB92B-7F41-5C55-B251-5955AC1B8D5C"><p>If a feature |
|
148 manager option (<codeph>-fm</codeph> or <codeph>-nofm</codeph>) is |
|
149 not passed to <codeph>BUILDROM</codeph> explicitly, the <codeph>-fm</codeph> option is used internally to generate a feature data file using |
|
150 the default <filepath>featuredatabase.xml</filepath> file in <filepath>\epoc32\rom\include</filepath>. For more information, refer to <xref href="GUID-66708290-1472-5A2C-B6D2-191454ECFE66.dita">Enabling feature |
|
151 data file generation</xref>. </p> </li> |
|
152 </ul></entry> |
|
153 </row> |
|
154 <row> |
|
155 <entry><p> <codeph>-nofm</codeph> =<<varname>Existing_features_data_file_name</varname> ><filepath>.dat</filepath> </p> </entry> |
|
156 <entry><p>Includes the specified features data file in the ROM image. </p> <p> <b>Note:</b> This option is ignored by <codeph>BUILDROM</codeph> if used with the <codeph>-fm</codeph> option. </p></entry> |
|
157 </row> |
|
158 <row> |
|
159 <entry><p> <codeph> -z=xxx or -zdrivepath=xxx </codeph> </p> </entry> |
|
160 <entry><p>Specifies the location to create the Z drive directory. </p> <p>By default, a Z drive directory is created in the location from |
|
161 where BUILDROM was invoked. </p></entry> |
|
162 </row> |
|
163 <row> |
|
164 <entry><p> <codeph> -d=xxx or -datadrivepath=xxx </codeph> </p> </entry> |
|
165 <entry><p>Specifies the location to create data drive directory. </p> <p>By default, the data drive directory is created in the location |
|
166 from where BUILDROM was invoked. </p></entry> |
|
167 </row> |
|
168 <row> |
|
169 <entry><p> <codeph>-k or -keepgoing </codeph> </p> </entry> |
|
170 <entry><p>Enables BUILDROM to continue to create the data drive image |
|
171 even if the SIS file(s), non-SIS file(s), or the Z drive image file(s) |
|
172 are missing or corrupted. </p></entry> |
|
173 </row> |
|
174 <row> |
|
175 <entry><p> <codeph>-zdriveimage="<image_1.img>,[...,<image_n.img>]" |
|
176 </codeph> </p></entry> |
|
177 <entry><p>Specifies the Z drive image (ROM, ROFS, and CORE image). </p></entry> |
|
178 </row> |
|
179 <row> |
|
180 <entry><p> <codeph> –r or -retainfolder </codeph> </p></entry> |
|
181 <entry><p>Instructs BUILDROM not to delete any pre-existing data drive |
|
182 folder. </p></entry> |
|
183 </row> |
|
184 <row> |
|
185 <entry><p> <codeph>-pfile=xxx</codeph> </p></entry> |
|
186 <entry><p>Specifies a parameter file for INTERPRETSIS to take additional |
|
187 parameters. </p></entry> |
|
188 </row> |
|
189 <row> |
|
190 <entry><p> <codeph>-l=<logfile.txt> or -logimageentry=<logfile.txt></codeph> </p></entry> |
|
191 <entry><p>Logs all stub-sis and SWI certificate file(s) that are part |
|
192 of the Z drive image onto a log file. </p></entry> |
|
193 </row> |
|
194 <row> |
|
195 <entry><p> <codeph>-argforinterpretsis </codeph> </p> </entry> |
|
196 <entry><p>Specifies the command-line argument for the InterpretSIS |
|
197 tool. These command-line arguments take precedence over the arguments |
|
198 in the parameter file. </p></entry> |
|
199 </row> |
|
200 <row> |
|
201 <entry><p> <codeph>-i=<optional path></codeph> </p> </entry> |
|
202 <entry><p>Specifies an optional path in which the IBY files are stored. |
|
203 This option is case-sensitive. </p> <p> <b>Notes:</b> </p> <ul> |
|
204 <li id="GUID-549E1869-8D18-5828-A167-F2757AA476FA"><p>If the IBY files |
|
205 are found both in the default path (<filepath>\epoc32\rom\include</filepath>), and the <optional path>, <codeph>BUILDROM</codeph> uses the |
|
206 IBY files in the <optional path>. </p> </li> |
|
207 <li id="GUID-35ABE65C-91A1-54D9-A221-8AE8DE1B8D5E"><p>If the IBY files |
|
208 are not found in the default path, <codeph>BUILDROM</codeph> uses |
|
209 the IBY files in the <optional path>. </p> </li> |
|
210 </ul></entry> |
|
211 </row> |
|
212 <row> |
|
213 <entry><p> <codeph>-j<NUM_OF_WORKING_THREADS></codeph> </p> </entry> |
|
214 <entry><p>Specifies the number of working threads that can run concurrently |
|
215 to create a ROM image. The <codeph><NUM_OF_WORKING_THREADS></codeph> must be an integer in the range 1-128. </p><p>If the <codeph>-j</codeph> option is not specified or an invalid value is specified, BUILDROM |
|
216 automatically takes the number of working threads in the following |
|
217 ways: </p><ul> |
|
218 <li id="GUID-918C5655-3D9C-5D55-A0A2-D817ABD8049D"><p>If the <codeph>NUMBER_OF_PROCESSORS</codeph> environment variable is set properly, |
|
219 BUILDROM uses the number of processors as the number of working threads. </p> </li> |
|
220 <li id="GUID-A892D1A3-2054-5DE8-98E8-D023C41F5D18"><p>If the <codeph>NUMBER_OF_PROCESSORS</codeph> environment variable is not set or |
|
221 is invalid, the default value <codeph>8</codeph> is used as the number |
|
222 of working threads. </p> </li> |
|
223 </ul></entry> |
|
224 </row> |
|
225 <row> |
|
226 <entry><p> <codeph>-compress</codeph> </p> </entry> |
|
227 <entry><p>Compresses the ROM image. It supports three types of compression:</p><ul> |
|
228 <li><p><codeph>-compress</codeph>: Compresses the entire ROM image.</p></li> |
|
229 <li><p><codeph>-compress=paged</codeph>: Compresses the paged section |
|
230 in the ROM image.</p></li> |
|
231 <li><p><codeph>-compress=unpaged</codeph>: Compresses the unpaged |
|
232 section in the ROM image.</p></li> |
|
233 </ul></entry> |
|
234 </row> |
|
235 <row> |
|
236 <entry><p><codeph>—w</codeph></p></entry> |
|
237 <entry><p>Warns if an incorrect input file is selected. For example, |
|
238 a warning is displayed, if an incorrect binary file is selected when |
|
239 binary variant is enabled.</p></entry> |
|
240 </row> |
|
241 <row> |
|
242 <entry><p><codeph>-nosymbols</codeph></p></entry> |
|
243 <entry><p>Suppresses the generation of any ROM or ROFS symbol file. |
|
244 This option generates all the relevant files except symbol files.</p></entry> |
|
245 </row> |
|
246 <row> |
|
247 <entry><p><codeph>-geninc</codeph></p></entry> |
|
248 <entry><p>Generates an INC file of ROM image. The INC file contains |
|
249 size information of the paged and the unpaged section within the ROM |
|
250 image. The name of the output file is the same as that of the output |
|
251 ROM image, with <codeph>.inc</codeph> as extension. </p></entry> |
|
252 </row> |
|
253 <row> |
|
254 <entry><p><codeph>-spi</codeph></p></entry> |
|
255 <entry><p>Creates an SPI file.</p></entry> |
|
256 </row> |
|
257 <row> |
|
258 <entry><p><codeph>-spiplacement</codeph></p></entry> |
|
259 <entry><p>Enables positioning of the SPI file.</p></entry> |
|
260 </row> |
|
261 <row> |
|
262 <entry><p> <codeph>-compressionmethod [none | inflate | bytepair]</codeph> </p> </entry> |
|
263 <entry><p>Specifies the compression algorithm to use. The following |
|
264 options are available with the <codeph>-compressionmethod</codeph> keyword:</p> <p><table id="GUID-34E5FD4C-7B82-5342-85C3-C84A706C8C17-GENID-1-2-1-8-1-1-6-1-1-4-1-2-2-7-1-3-29-2-2-1"> |
|
265 <tgroup cols="2"><colspec colname="col0"/><colspec colname="col1"/> |
|
266 <tbody> |
|
267 <row> |
|
268 <entry><p> <codeph>none </codeph> </p> </entry> |
|
269 <entry><p>No compression is used. </p> </entry> |
|
270 </row> |
|
271 <row> |
|
272 <entry><p> <codeph>inflate </codeph> </p> </entry> |
|
273 <entry><p>Compresses executable files using the default (Deflate, |
|
274 Huffman+LZ77) algorithm. </p> </entry> |
|
275 </row> |
|
276 <row> |
|
277 <entry><p> <codeph>bytepair </codeph> </p> </entry> |
|
278 <entry><p>Compresses executable files using the bytepair algorithm. |
|
279 Bytepair compression allows faster decompression than the default |
|
280 Deflate, Huffman+LZ77 algorithm. It also supports demand paging by |
|
281 performing compression and decompression of code in independent 4 |
|
282 KB pages. </p> </entry> |
|
283 </row> |
|
284 </tbody> |
|
285 </tgroup> |
|
286 </table> </p></entry> |
|
287 </row> |
|
288 <row> |
|
289 <entry><p> <codeph>-cache</codeph> </p> </entry> |
|
290 <entry><p>Enables cache mechanism. It ensures that BUILDROM uses cached |
|
291 executable files while creating a ROFS image. This allows BUILDROM |
|
292 to reuse or generate cached files. </p> <p> <b>Notes</b>: </p><ul> |
|
293 <li id="GUID-9B7056D4-EF5B-533B-9E9F-50AD9A7BF498-GENID-1-2-1-8-1-1-6-1-1-4-1-2-2-7-1-3-30-2-3-1"><p>The cache mechanism |
|
294 is disabled by default. </p> </li> |
|
295 <li id="GUID-AF355401-C732-5FB5-A472-D7EEB294E4E0-GENID-1-2-1-8-1-1-6-1-1-4-1-2-2-7-1-3-30-2-3-2"><p>The cached files |
|
296 are stored on the hard disk. </p> </li> |
|
297 <li id="GUID-7EEA01CD-E155-535B-915B-DE22C42FEDD0-GENID-1-2-1-8-1-1-6-1-1-4-1-2-2-7-1-3-30-2-3-3"><p>The cache command |
|
298 line options (<codeph>-cache</codeph>, <codeph>-nocache</codeph>, |
|
299 and <codeph>-cleancache</codeph>) are mutually exclusive. This means |
|
300 that you can use only one cache option at a time. </p> </li> |
|
301 </ul></entry> |
|
302 </row> |
|
303 <row> |
|
304 <entry><p> <codeph>-nocache</codeph> </p></entry> |
|
305 <entry><p>Disallows BUILDROM from using cached files while creating |
|
306 a ROFS image. </p></entry> |
|
307 </row> |
|
308 <row> |
|
309 <entry><p> <codeph>-cleancache</codeph> </p></entry> |
|
310 <entry><p>Deletes all cached files from the hard disk. </p></entry> |
|
311 </row> |
|
312 <row> |
|
313 <entry><p><codeph>-gendep</codeph></p></entry> |
|
314 <entry><p>Generates dependencies file describing a internal dependencies |
|
315 among executables or dlls in a ROM image.</p><p><b>Note</b>: You can |
|
316 only generate dependence information in the paged section of a ROM |
|
317 image.</p></entry> |
|
318 </row> |
|
319 <row> |
|
320 <entry><p><codeph>-checkcase</codeph></p></entry> |
|
321 <entry><p>Checks the character case of the path or name in OBY or |
|
322 IBY files. By default, this option is disabled.</p><p><b>Note</b>: |
|
323 This option is only valid on Windows.</p></entry> |
|
324 </row> |
|
325 <row> |
|
326 |
|
327 <entry><p><codeph>-workdir <output-location></codeph></p></entry> |
|
328 <entry><p>Generates the output files at the specified location.</p></entry> |
|
329 </row> |
|
330 <row> |
|
331 |
|
332 <entry><p><codeph>-prependepocroot</codeph></p></entry> |
|
333 <entry><p>Prepends EPOCROOT to the file location, if the specified |
|
334 location starts from <codeph>\epoc32</codeph> without <codeph>EPOCROOT</codeph>.</p></entry> |
|
335 </row> |
|
336 </tbody> |
|
337 </tgroup> |
|
338 </table> <p><b>Note</b>: <codeph><obeyfile1></codeph> and <codeph><obeyfile2></codeph> and are standard text files containing statements |
|
339 that are used to control the building of ROM images. </p> <p>See the <xref href="GUID-9CF985F1-C100-5999-9410-58B7865A1E18.dita">OBEY files</xref> reference for the full syntax. </p> </section> |
|
340 <section id="GUID-4436DEEC-DB8A-4FDE-A869-63544C856ED8"><title>Passing |
|
341 parameters using a file</title> <p>BUILDROM allows to pass parameters |
|
342 in a file using the <codeph>-argfile</codeph> option. It provides |
|
343 a solution to the limited command line length. It also reduces the |
|
344 risk of error and saves time in typing from a command prompt. </p> <p><userinput>BUILDROM –argfile=arg.txt -s</userinput> </p> <p>In |
|
345 the BUILDROM command above, <filepath>arg.txt</filepath> is the text |
|
346 file with the parameters. An example of this file is as follows: </p> <codeblock id="GUID-C7412FD1-31CC-5860-9A6F-5A386AF5C658" xml:space="preserve">; sample parameter-file |
|
347 -fm=\epoc32\rom\include\featuredatabase.xml ;generate features data file. |
|
348 -noimage -nosymbols -s ;do not generate ROM image and symbol file |
|
349 ;and invoke buildrom in strict mode. |
|
350 -D_PLAT=ARMV5 |
|
351 ; EOF</codeblock> <p>Rules of this argument file are as follows: </p> <ul> |
|
352 <li id="GUID-BBCBEA65-8DD6-5440-8F9F-E780FE2839AA"><p>Single line |
|
353 comments begin with a semicolon (<b>;</b>). </p> </li> |
|
354 <li id="GUID-4322E7DB-E539-5E79-85B8-1CD4C1088BA0"><p>Comments can |
|
355 also be specified after the parameters. </p> </li> |
|
356 <li id="GUID-C509C35B-6643-581F-9A78-ECC4E49DD943"><p>Parameters can |
|
357 be specified either in a single line separated a by space, or in multiple |
|
358 lines. </p> <p> </p> </li> |
|
359 <li id="GUID-69B173D5-2501-5D60-8CD3-CC144422CBB7"><p>Parameters provided |
|
360 in a parameter file override those specified in the command line. </p> </li> |
|
361 <li id="GUID-48482902-77FE-552B-9D4D-FFC062F41E1B"><p>Environment |
|
362 variables must be specified in the command line and not in the parameter |
|
363 file. </p> </li> |
|
364 </ul> </section> |
|
365 </conbody></concept> |