Free Trial

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.

Share this Page URL

Chapter 9: Using Flex Ant Tasks > Using the mxmlc task - Pg. 182

ADOBE FLEX 3 187 Building and Deploying Adobe Flex 3 Applications The following options are implemented as implicit FileSets: compiler.external-library-path compiler.include-libraries compiler.library-path compiler.theme compiler.include-sources (compc only) The Flex Ant task's implicit FileSets are also different from the Ant project's implicit FileSets in that they support being empty, as in the following example: <external-library-path/> This is equivalent to using external-library-path= on the command line. Using the mxmlc task You use the mxmlc Flex Ant task to compile applications, modules, resource modules, and Cascading Style Sheets (CSS) SWF files. This task supports most mxmlc command-line compiler options, including aliases. For more information on using the mxmlc command-line compiler, see "Using mxmlc, the application compiler" on page 139. Required attributes The mxmlc task requires the file attribute. The file attribute specifies the MXML file to compile. This attribute does not have a command-line equivalent because it is the default option on the command line. Unsupported options The following mxmlc command-line compiler options are not supported by the mxmlc task: · · help version Example The following example mxmlc task explicitly defines the source-path and library-path options, in addition to other properties such as incremental and keep-generated-actionscript . This example also specifies an output location for the resulting SWF file. This example defines two targets: main and clean. The main target compiles the Main.mxml file into a SWF file. The clean target deletes the output of the main target.