About the component compiler options

Writes a digest to the catalog.xml of a library. Use this when the library will be used as a cross-domain RSL or when you want to enforce the versioning of RSLs. The default value is true.

For more information about RSLs, see Runtime Shared Libraries.

Outputs the SWC file in an open directory format rather than a SWC file. You use this option with the output option to specify a destination directory, as the following example shows:

compc -directory=true -output=destination_directory

You typically use this option when you create RSLs because you must extract the library.swf file from the SWC file before deployment. For more information, see Runtime Shared Libraries.

The default value is false.

Specifies classes to include in the SWC file. You provide the class name (for example, MyClass) rather than the file name (for example, MyClass.as) to the file for this option. As a result, all classes specified with this option must be in the compiler’s source path. You specify this by using the source-path compiler option.

You can use packaged and unpackaged classes. To use components in namespaces, use the include-namespaces option.

If the components are in packages, ensure that you use dot-notation rather than slashes to separate package levels.

This is the default option for the component compiler.

Adds the file to the SWC file. This option does not embed files inside the library.swf file. This is useful for adding graphics files, where you want to add non-compiled files that can be referenced in a style sheet or embedded as assets in MXML files.

If you add a stylesheet that references compiled resources such as programmatic skins, use the include-stylesheet option.

If you use the [Embed] syntax to add a resource to your application, you are not required to use this option to also link it into the SWC file.

For more information, see Adding nonsource classes.

If true, only manifest entries with lookupOnly=true are included in the SWC catalog. The default value is false.

This is an advanced option.

Specifies namespace-style components in the SWC file. You specify a list of URIs to include in the SWC file. The uri argument must already be defined with the namespace option.

To use components in packages, use the include-classes option.

Specifies classes or directories to add to the SWC file. When specifying classes, you specify the path to the class file (for example, MyClass.as) rather than the class name itself (for example, MyClass). This lets you add classes to the SWC file that are not in the source path. In general, though, use the include-classes option, which lets you add classes that are in the source path.

If you specify a directory, this option includes all files with an MXML or AS extension, and ignores all other files.

If you use this option to include MXML components that are in a non-default package, you must include the source folder in the source path.

Specifies stylesheets to add to the SWC file. This option compiles classes that are referenced by the stylesheet before including the stylesheet in the SWC file.

You do not need to use this option for all stylesheets; only stylesheets that reference assets that need to be compiled such as programmatic skins or other class files. If your stylesheet does not reference compiled assets, you can use the include-file option.

This option does not compile the stylesheet into a SWF file before including it in the SWC file. You compile a CSS file into a SWF file when you want to load it at run time.