list of mxmlc/compc arguments

August 9th, 2006 中文

Have you ever tried to figure out all the configuration parameters of mxmlc?

Well there is a lot of information inside the mxmlc itself. You can actually list all the simple and advanced command line arguments that are available. It even gives you power to search across multiple sets of lists to get speciifc information about your search terms. Lets take a more in depth look.
You start by running:

CODE:
  1. mxmlc -help

You should see:

CODE:
  1. Adobe Flex Compiler (mxmlc)
  2. Version 2.0 build 143452
  3. Copyright (c) 2004-2006 Adobe Systems, Inc. All rights reserved.
  4.  
  5. -help [keyword] [...]
  6. For information on command line syntax and descriptions of
  7. configuration variables, specify a search string, or one of the
  8. following special keywords:
  9. syntax   - describe the general syntax of the command line
  10. list     - show a list of all basic configuration variables
  11. advanced - also match advanced configuration variables
  12. aliases  - sort using the short alias for the variable
  13. details  - always display the full details for each item
  14. Any other help keyword provided is used to match a full or partial
  15. configuration variable, alias, or text to search for in the
  16. description of the configuration variable.
  17.  
  18. For example, '-help advanced aliases foo' would show all
  19. configuration options (both basic and advanced) containing the text
  20. 'foo', sorted by alias name.
  21.  
  22. In the description of individual configuration variables, required
  23. values are marked with angle brackets, and optional values are marked
  24. with square brackets.  The notation [...] is used to indicate that
  25. the values are a list of arbitrary length.

From here you can run the help on specific keywords or upon the special keywords. You'll see the special keywords defined as syntax, list, advanced, aliases, and details.

Here is my quick search for "theme"

CODE:
  1. C:\Documents and Settings\renaun>mxmlc -help theme
  2. Adobe Flex Compiler (mxmlc)
  3. Version 2.0 build 143452
  4. Copyright (c) 2004-2006 Adobe Systems, Inc. All rights reserved.
  5.  
  6. -compiler.theme [filename] [...]
  7. alias -theme
  8. list of CSS or SWC files to apply as a theme (repeatable)

You can list and search through all the mxml arguments to find what you are looking for, this is much better then livedocs, hehe...

I am going to list all the arguments from the simple and more advanced special keywords to have a running list of arguments. The items in bold are found in the mxmlc -advanced list but not in the livedocs.
-benchmark
-compiler.accessible
-compiler.actionscript-file-encoding
-compiler.allow-source-path-overlap
-compiler.as3
-compiler.context-root
-compiler.debug
-compiler.defaults-css-url
-compiler.doc
-compiler.es
-compiler.external-library-path [path-element] [...]
-compiler.fonts.languages.language-range
-compiler.fonts.local-fonts-snapshot
-compiler.fonts.managers [manager-class] [...]
-compiler.fonts.max-cached-fonts
-compiler.fonts.max-glyphs-per-face
-compiler.headless-server
-compiler.include-libraries [library] [...]
-compiler.incremental
-compiler.keep-all-type-selectors
-compiler.keep-generated-actionscript
-compiler.library-path [path-element] [...]
-compiler.locale
-compiler.namespaces.namespace
-compiler.optimize
-compiler.profile
-compiler.services
-compiler.show-actionscript-warnings
-compiler.show-binding-warnings
-compiler.show-deprecation-warnings
-compiler.source-path [path-element] [...]
-compiler.strict
-compiler.theme [filename] [...]
-compiler.use-resource-bundle-metadata
-compiler.verbose-stacktraces

-compiler.warn-warning_type

-compiler.warn-array-tostring-changes
-compiler.warn-assignment-within-conditional
-compiler.warn-bad-array-cast
-compiler.warn-bad-bool-assignment
-compiler.warn-bad-date-cast
-compiler.warn-bad-es3-type-method
-compiler.warn-bad-es3-type-prop
-compiler.warn-bad-nan-comparison
-compiler.warn-bad-null-assignment
-compiler.warn-bad-null-comparison
-compiler.warn-bad-undefined-comparison
-compiler.warn-boolean-constructor-with-no-args
-compiler.warn-changes-in-resolve
-compiler.warn-class-is-sealed
-compiler.warn-const-not-initialized
-compiler.warn-constructor-returns-value
-compiler.warn-deprecated-event-handler-error
-compiler.warn-deprecated-function-error
-compiler.warn-deprecated-property-error
-compiler.warn-duplicate-argument-names
-compiler.warn-duplicate-variable-def
-compiler.warn-for-var-in-changes
-compiler.warn-import-hides-class
-compiler.warn-instance-of-changes
-compiler.warn-internal-error
-compiler.warn-level-not-supported
-compiler.warn-missing-namespace-decl
-compiler.warn-negative-uint-literal
-compiler.warn-no-constructor
-compiler.warn-no-explicit-super-call-in-constructor
-compiler.warn-no-type-decl
-compiler.warn-number-from-string-changes
-compiler.warn-scoping-change-in-this
-compiler.warn-slow-text-field-addition
-compiler.warn-unlikely-function-value
-compiler.warn-xml-class-has-changed

-debug-password
-default-background-color
-default-frame-rate
-default-script-limits
-default-size
-dump-config
-externs [symbol] [...]
-file-specs [path-element] [...]
-frames.frame [label] [classname] [...]
-help [keyword] [...]
-includes [symbol] [...]
-lazy-init
-licenses.license
-link-report
-load-config
-load-externs

-metadata.contributor
-metadata.creator
-metadata.date
-metadata.description
-metadata.language
-metadata.localized-description
-metadata.localized-title
-metadata.publisher
-metadata.title

-output
-raw-metadata
-resource-bundle-list
-runtime-shared-libraries [url] [...]
-use-network
-version
-warnings

Here is the list of options that are in the livedocs and not in the mxmlc -advanced

-compiler.warn-warning_type and -metadata options refer to groups of options shown above. In the livedocs options all metadata options are shown in the alias form (contributor,creator,date,description,langugage,localized-description,localized-title,publisher and title).

max-recursion-depth
max-execution-time
defaults-css-url
generate-frame-loader

There is a bunch of more good information at the flexcoders post by Roger located at http://groups.yahoo.com/group/flexcoders/message/46751

Entry Filed under: Adobe Flex, Rich Internet Applications

9 Comments Add your own

  • 1. Tom Chiverton  |  2006-08-10 at 2.02 am

    Eww, dude !
    Is there something wrong with the livedocs, rooted around about http://livedocs.macromedia.com/flex/2/docs/00001500.html ?

  • 2. Renaun Erickson  |  2006-08-10 at 7.44 am

    The only thing is there are differences between the two sources. Livedocs shows mostly alias and has good descriptions. The mxmlc -advanced list shows some that are not explained fully (or well) in the livedocs. And then there are some in the livedocs that are not in the mxmlc -advanced list.

  • 3. matthew horn  |  2006-09-25 at 11.24 am

    Some notes about the compiler options that appear in the advanced mxmlc list but do not appear in livedocs:
    compiler.doc - was not implemented at publish date.
    compiler.keep-all-type-selectors - this is supposed to be an internal-only option for Flex Builder.
    compiler.profile - was not implemented at publish date.
    compiler.warn-warning_type - I thought these were pretty self-explanatory and decided to leave them out of the livedocs doc.

    I’ll look into why licenses.license, raw-metadata, and compiler.use-resource-bundle-metadata have been left out of livedocs.

    The metadata options (such as contributor, creator, and data) are in livedocs, but I didnt include their prefix (”metadata.”) since they are unique (as are all compiler options), so they show up in the general list in alphabetical order.

    hth,
    matt horn
    flex docs

  • 4. Renaun Erickson  |  2006-09-25 at 11.26 am

    Matt,

    Thank you for the update.

    Renaun

  • 5. Josephine  |  2007-08-09 at 9.07 am

    Hi, Renaun.
    Do you know where the action script files are kept if -compiler.keep-generated-actionscript is set to true?
    Thanks,
    Josephine

  • 6. Josephine  |  2007-08-09 at 9.12 am

    Duh. Nevermind. I found them under as3/generated/

  • 7. KinRou Blog » mxmlc&hellip  |  2007-08-18 at 7.44 am

    [...] http://renaun.com/blog/2006/08/09/84/ [...]

  • 8. » Ò»¸öÓÐȤµÄFlex¼¼Ê&hellip  |  2008-02-20 at 6.20 pm

    [...] ±ÈÈ磺 flash.text.TextField.pasteRichText() flash.text.TextField.copyRichText() flash.text.TextField.insertXMLText() flash.text.TextField.getXMLText() list of mxmlc/compc arguments £¨mxmcµÄ²ÎÊýÁÐ±í£¬°üÀ¨ÎĵµÖÐûÓÐÁгöµÄ£¬ÓÐÖÐÎÄ·­Ò룩 [...]

  • 9. Gnanasekaran  |  2008-03-18 at 5.28 am

    Is it possible to compile more than one mxml file in a command line?
    Like mxmlc *.mxml

Leave a Comment

Required

Required, hidden

Some HTML allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Trackback this post  |  Subscribe to the comments via RSS Feed


Disclaimer: I work as a Flash/Flex Developer for Adobe Systems Incorporated. The opinions expressed here represent my own and not those of my employer.

My Amazon.com Wish List

Calendar

August 2006
S M T W T F S
« Jul   Sep »
 12345
6789101112
13141516171819
20212223242526
2728293031  

Most Recent Posts


Flex.org - The Directory for Flex