flex-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patil, Virat" <virat.pa...@capgemini.com>
Subject RE: compc additional compiler arguments
Date Thu, 10 Apr 2014 11:50:55 GMT
Hi Raj

Check out if this solves your problem. By passing Configuration XML file in load-config argument.

Section 21.2: Use the Component Compiler

You want to compile a Flex component into a SWC file that can be used as a runtime shared
library (RSL).


Use the Component compiler (compc) and either pass command-line arguments to the compiler
or pass a configuration XML file as the load-config argument.


To invoke the Component compiler, compc, use this syntax:

compc -source-path . -include-classes oreilly.cookbook.foo -output example.swc
Some of the most important options for the compc are as follows:

Indicates that the compiler should benchmark the amount of time needed to compile the SWC.
Indicates whether the generated SWC should have debugging information and functionality included
with it.
-compiler.external-library-path [path-element] [...]
Indicates SWC files or directories to compile against but to omit from linking.
-compiler.include-libraries [library] [...]
Indicates libraries (SWCs) to completely include in the SWF.
-compiler.library-path [path-element] [...]
Indicates SWC files or directories that contain SWC files that should be used in compiling.
-compiler.locale [locale-element] [...]
Specifies the locale for internationalization.
Enables postlink SWF optimization.
-compiler.services <filename>
Specifies the path to the Flex Data Services configuration file.
-compiler.theme [filename] [...]
Lists all CSS or SWC files to apply as themes within the application.
Determines whether resources bundles are included in the application.
-include-classes [class] [...]
Indicates all the classes that should be included in the RSL; can be repeated multiple times
or have a wildcard path listed.
-include-file <name><path>
Indicates all the files that should be included in the RSL; can be repeated multiple times
or have a wildcard path listed.
-include-resource-bundles [bundle] [...]
Sets whether a localization resource bundle should be included.
-load-config <filename>
Loads a file containing configuration options.
-output <filename>
Determines the name and location of the file that is generated by compc.
-runtime-shared-libraries [url] [...]
Indicates any external RSLs that should be bundled into the RSL generated by compc in this
-runtime-shared-library-path [path-element] [rsl-url] [policy-file-url] [rsl-url] [policy-file-url]
Sets the location and other information about an RSL that the application will use.
Toggles whether the SWC is flagged for access to network resources.
Compiling many classes into a runtime shared library can result in a very long command. To
simplify this, you can use either configuration files or manifest files.

As with the MXML compiler (mxmlc), you can use configuration files with compc by specifying
a load-config option. Also like mxmlc, compc automatically loads a default configuration file
called flex-config.xml. Unless you want to duplicate the entire contents of flex-config.xml
(much of which is required), specify a configuration file in addition to the default by using
the += operator:

compc -load-config+=configuration.xml
Any flags passed to the compiler can be described in XML and passed to compc in the ´┐Żload-config


Virat I Patil

-----Original Message-----
From: Raj U. Shaikh [mailto:Raj.Shaikh@mastek.com] 
Sent: Thursday, April 10, 2014 4:16 PM
To: users@flex.apache.org
Cc: Yogesh C. Jadhav
Subject: compc additional compiler arguments

Hi All,

In mxmlc we have an option to define additional compiler arguments in following way


But same is not available in compc. Is there have any alternate way for same?

I am creating a library project(swc) and want to set one argument/property to it at compile

Please help.

Raj Shaikh
In the US, we're called MAJESCOMASTEK

Opinions expressed in this e-mail are those of the individual and not that of Mastek Limited,
unless specifically indicated to that effect. Mastek Limited does not accept any responsibility
or liability for it. This e-mail and attachments (if any) transmitted with it are confidential
and/or privileged and solely for the use of the intended person or entity to which it is addressed.
Any review, re-transmission, dissemination or other use of or taking of any action in reliance
upon this information by persons or entities other than the intended recipient is prohibited.
This e-mail and its attachments have been scanned for the presence of computer viruses. It
is the responsibility of the recipient to run the virus check on e-mails and attachments before
opening them. If you have received this e-mail in error, kindly delete this e-mail from desktop
and server.
This message contains information that may be privileged or confidential and is the property
of the Capgemini Group. It is intended only for the person to whom it is addressed. If you
are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate,
distribute, or use this message or any part thereof. If you receive this message in error,
please notify the sender immediately and delete all copies of this message.
View raw message