Technically a swc is a zip with a swf inside. I am sure that some extract the swf from the swc. Then all the
properties useful for a swf become useful for a swc.

yours
Martin.

On 10/04/2012 00:10, JP Bader wrote:
If they are ignored, is there a reason they are there in the documentation?

JP

On Mon, Apr 9, 2012 at 10:05 AM, Darrell Loverin<dlove...@adobe.com>  wrote:
The mxmlc options that don't contribute SWCs to the compiler are ignored by 
swcdepends. The idea is you can substitute swcdepends for mxmlc on the command 
line without having to worry about removing options like metadata. So many 
options are ignored by swcdepends.


-Darrell

-----Original Message-----
From: Left Right [mailto:olegsivo...@gmail.com]
Sent: Monday, April 09, 2012 10:33 AM
To: flex-dev@incubator.apache.org
Subject: Re: What does swcdepends do?

Hi and thanks for the links, this is somewhat helpful, but it leaves a lot of 
questions unanswered. These articles only cover some small subset of all 
options available to this utility, below is the full set:

-benchmark
-compiler.accessible
-compiler.actionscript-file-encoding<string>  -compiler.compress 
-compiler.context-root<context-path>  -compiler.debug 
-compiler.enable-runtime-design-layers
-compiler.extensions.extension [extension] [parameters] [...] 
-compiler.external-library-path [path-element] [...] 
-compiler.fonts.advanced-anti-aliasing
-compiler.fonts.flash-type
-compiler.fonts.max-glyphs-per-face<string>  -compiler.include-libraries [library] [...] 
-compiler.incremental -compiler.library-path [path-element] [...] -compiler.locale [locale-element] [...] 
-compiler.minimum-supported-version<string>  -compiler.mobile 
-compiler.mxml.compatibility-version<version>  -compiler.mxml.minimum-supported-version<string>  
-compiler.namespaces.namespace [uri] [manifest] [...] -compiler.omit-trace-statements -compiler.optimize 
-compiler.preloader<string>  -compiler.report-invalid-styles-as-warnings
-compiler.services<filename>
-compiler.show-actionscript-warnings
-compiler.show-binding-warnings
-compiler.show-invalid-css-property-warnings
-compiler.show-shadowed-device-font-warnings
-compiler.show-unused-type-selector-warnings
-compiler.source-path [path-element] [...] -compiler.strict -compiler.theme 
[filename] [...] -compiler.use-resource-bundle-metadata
-compiler.verbose-stacktraces
-dependency.minimize-dependency-set
-dependency.show-external-classes
-dependency.show-swcs [swc-name] [...]
-dependency.show-types
-dependency.types [type] [...]
-framework<string>
-help [keyword] [...]
-include-resource-bundles [bundle] [...] -licenses.license<product>  <serial-number>  -load-config<filename>  -metadata.contributor<name>  
-metadata.creator<name>  -metadata.date<text>  -metadata.description<text>  -metadata.language<code>  -metadata.localized-description<text> 
 <lang>  -metadata.localized-title<title>  <lang>  -metadata.publisher<name>  -metadata.title<text>  -output<filename>  
-runtime-shared-libraries [url] [...] -runtime-shared-library-path [path-element] [rsl-url] [policy-file-url] [rsl-url] [policy-file-url] 
-static-link-runtime-shared-libraries
-swf-version<int>
-target-player<version>
-tools-locale<string>
-use-direct-blit
-use-gpu
-use-network
-version
-warnings

There are a lot of options that aren't even applicable to SWCs, like, for 
example, all the metadata group. The descriptions for these properties are 
copy-and-paste from mxmlc/compc documentation. So, I don't know what to think.

Best.

Oleg



Reply via email to