Specifications
147ADOBE FLEX 3
Building and Deploying Adobe Flex 3 Applications
library-path path-element [...]
Links SWC files to the resulting application SWF file. The compiler only links in
those classes for the SWC file that are required. You can specify a directory or
individual SWC files.
The default value of the library-path option includes all SWC files in the
libs and libs/player directories, plus the current locale directory. These are
required.
To point to individual classes or packages rather than entire SWC files, use the
source-path option.
If you set the value of the library-path as an option of the command-line
compiler, you must also explicitly add the framework.swc and locale SWC files.
Your new entry is not appended to the
library-path but replaces it, unless
you use the += operator.
On the command line, you use the += operator to append the new argument
to the list of existing SWC files.
In a configuration file, you can set the append attribute of the library-path
tag to
true to indicate that the values should be appended to the library path
rather than replace existing default entries.
license product_name license_key
Defines the license key to use when compiling. Valid values for
product_name include flexbuilder3.
link-report filename
Prints linking information to the specified output file. This file is an XML file
that contains
<def>, <pre>, and <ext> symbols showing linker dependen-
cies in the final SWF file.
The file format output by this command can be used to write a file for input to
the
load-externs option.
For more information on the report, see “Examining linker dependencies” on
page 65.
This is an advanced option.
load-config filename
Specifies the location of the configuration file that defines compiler options.
If you specify a configuration file, you can override individual options by
setting them on the command line.
All relative paths in the configuration file are relative to the location of the
configuration file itself.
Use the += operator to chain this configuration file to other configuration files.
For more information on using configuration files to provide options to the
command-line compilers, see
“About configuration files” on page 134.
Option Description