Specifications

CHAPTER 8
148
load-externs filename [...]
Specifies the location of an XML file that contains <def>, <pre>, and <ext>
symbols to omit from linking when compiling a SWF file. The XML file uses the
same syntax as the one produced by the
link-report option. For more
information on the report, see
“Examining linker dependencies” on page 65.
This option provides compile-time link checking for external components that
are dynamically linked.
For more information about dynamic linking, see “About linking” on page 196.
This is an advanced option.
locale string
Specifies one or more locales to be compiled into the SWF file. If you do not
specify a locale, then the compiler uses the default locale from the flex-
config.xml file. The default value is en_US. You can append additional locales
to the default locale by using the += operator.
If you remove the default locale from the flex-config.xml file, and do not
specify one on the command line, then the compiler will use the machine’s
locale.
For more information, see “Localizing Flex Applications” on page 1101in
Adobe Flex 3 Developer Guide.
localized-description text lang
Sets metadata in the resulting SWF file. For more information, see “Adding
metadata to SWF files” on page 155.
localized-title text lang
Sets metadata in the resulting SWF file. For more information, see “Adding
metadata to SWF files” on page 155.
mxml.compatibility-version=version
Specifies the version of the Flex compiler that the output should be compat-
ible with. This option affects some behavior such as the layout rules, padding
and gaps, skins, and other style settings. In addition, it affects the rules for
parsing properties files.
The currently-supported values are 3 and 2.0.1. The default value is 3.
The following example instructs the application to compile with the 2.0.1 rules
for these behaviors:
-compatibility-version=2.0.1
For more information on using the option, see “Backward compatibility” on
page 286.
namespaces.namespace uri manifest
Specifies a namespace for the MXML file. You must include a URI and the loca-
tion of the manifest file that defines the contents of this namespace. This path
is relative to the MXML file.
For more information about manifest files, see “About manifest files” on
page 175.
Option Description