You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@flex.apache.org by "Raj U. Shaikh" <Ra...@mastek.com> on 2014/04/10 12:45:30 UTC
compc additional compiler arguments
Hi All,
In mxmlc we have an option to define additional compiler arguments in following way
-define=NAMESPACE::variable,value
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 time.
Please help.
Regards,
Raj Shaikh
MASTEK LTD.
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.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
AW: compc additional compiler arguments
Posted by Christofer Dutz <ch...@c-ware.de>.
Well Flexmojos doesn't actually do much itself ... it's more a Maven Style Remote Control to the compiler. So If the compiler doesn't support that, there will be no use doing that in FlexMojos. But I'll have a look at that.
Chris
________________________________________
Von: Raj U. Shaikh <Ra...@mastek.com>
Gesendet: Sonntag, 27. April 2014 14:29
An: users@flex.apache.org
Betreff: RE: compc additional compiler arguments
Hi Chris,
Please find attached library project depicting additional compiler arguments using "-define=CONFIG::Version"
I consider there is no way to define custom arguments in compc and there my problem stands. (While mxmlc supports -define parameter)
I am wondering why there is no support in compc?
Regards,
Raj Shaikh
-----Original Message-----
From: Christofer Dutz [mailto:christofer.dutz@c-ware.de]
Sent: Friday, April 11, 2014 8:01 PM
To: users@flex.apache.org
Subject: AW: compc additional compiler arguments
Hi,
well I'm stil at the ApacheCon so I don't quite have the time right now, but If you could whip up a small maven project demonstrating this problem, zip it up and send it to my private email. I'lll try to check it out. Unfortunately there currently seems to be a problem preventing us from registering new users on the Fllexmojos Jira :-(
Chris
-----Ursprüngliche Nachricht-----
Von: Raj U. Shaikh [mailto:Raj.Shaikh@mastek.com]
Gesendet: Freitag, 11. April 2014 08:18
An: users@flex.apache.org
Betreff: RE: compc additional compiler arguments
I am using flexmojos and I can use these task into pom as follows,
<compiler>
<define>
<name>CONFIG::version</name>
<value>MyVersion</value>
</define>
</compiler>
Also, I tried following as well,
<define name="CONFIG::version" value"MyVersion"/>
But I get following error,
D:\eclipse_workspace\icd\8.6.0.0_Library>mvn compile
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building ICD Library 5.38.0.18-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ ICDLibrary ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 69 resources
[INFO]
[INFO] --- flexmojos-maven-plugin:4.1-beta:compile-swc (default-compile-swc) @ ICDLibrary ---
[INFO] Flexmojos 4.1-beta
[INFO] Apache License - Version 2.0 (NO WARRANTY) - See COPYRIGHT file
[WARNING] No themes are explicitly defined in the <theme> section or in any scope="theme" dependencies. Flexmojos is now attempting to figure out which themes to include. (to avoid this warning you should explicitly state your theme dependencies)
[WARNING] Adding spark.css theme because spark.swc was included as a dependency
[INFO] Writing configuration dump to D:\eclipse_workspace\icd\8.6.0.0_Library\target\ICDLibrary-5.38.0.18-SNAPSHOT-configs.xml
[ERROR] D:\eclipse_workspace\icd\8.6.0.0_Library\src\main\flex\com\majescomastek\stgicd\ui\module\BaseModule.as:[92,11] Access of undefined property version. CONFIG::version
[ERROR] D:\eclipse_workspace\icd\8.6.0.0_Library\src\main\flex\com\majescomastek\stgicd\ui\module\BaseModule.as:[92,11] Access of undefined property version. CONFIG::version
[ERROR] D:\eclipse_workspace\icd\8.6.0.0_Library\src\main\flex\com\majescomastek\stgicd\ui\module\BaseModule.as:[92,11] Access of undefined property version. CONFIG::version
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4.171s
[INFO] Finished at: Fri Apr 11 11:43:14 IST 2014
[INFO] Final Memory: 10M/76M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.sonatype.flexmojos:flexmojos-maven-plugin:4.1-beta:compile-swc (default-compile-swc) on project ICDLibrary: Got 3 errors building project, check logs -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
I believe down the line it uses compc and in api documents there is no mention of define namespace.
Am I missing something?
-----Original Message-----
From: Christofer Dutz [mailto:christofer.dutz@c-ware.de]
Sent: Thursday, April 10, 2014 9:27 PM
To: users@flex.apache.org
Subject: AW: compc additional compiler arguments
If you are talking about flexmojos. This should be possible by adding that to the configuration element of the plugin. There should be an example in the flexmojos test suite.
Chris
Gesendet mit meinem HTC
----- Reply message -----
Von: "Lee Burrows" <su...@leeburrows.com>
An: "users@flex.apache.org" <us...@flex.apache.org>
Betreff: compc additional compiler arguments
Datum: Do., Apr. 10, 2014 08:53
I dont use maven so i cant answer that
On 10/04/2014 15:40, Raj U. Shaikh wrote:
> Can I able to add this in pom xml(maven)? I searched on it but no clues..
>
> -----Original Message-----
> From: Lee Burrows [mailto:subscriptions@leeburrows.com]
> Sent: Thursday, April 10, 2014 7:14 PM
> To: users@flex.apache.org
> Subject: Re: compc additional compiler arguments
>
> Ignore my previous email with docs link ;(
>
> You can add custom arguments to config files like so:
>
> <compiler>
> <define>
> <name>NAMESPACE::variable</name>
> <value>your-value</value>
> </define>
> </compiler>
>
> On 10/04/2014 14:20, Raj U. Shaikh wrote:
>> Virat,
>>
>> I am looking for custom arguments and not the predefined ones.
>>
>> Regards,
>> Raj Shaikh
>>
>> -----Original Message-----
>> From: Patil, Virat [mailto:virat.patil@capgemini.com]
>> Sent: Thursday, April 10, 2014 5:21 PM
>> To: users@flex.apache.org
>> Cc: Yogesh C. Jadhav
>> Subject: RE: compc additional compiler arguments
>>
>> 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 Problem
>>
>> You want to compile a Flex component into a SWC file that can be used as a runtime shared library (RSL).
>>
>> Solution
>>
>> 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.
>>
>> Discussion
>>
>> 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:
>>
>> -benchmark
>> Indicates that the compiler should benchmark the amount of time needed to compile the SWC.
>> -compiler.debug
>> 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.
>> -compiler.optimize
>> 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.
>> -compiler.use-resource-bundle-metadata
>> 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 compilation.
>> -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.
>> -use-network
>> 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 option:
>>
>> <include-sources>src/.</include-sources>
>>
>>
>>
>> Regards
>> 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
>>
>> -define=NAMESPACE::variable,value
>>
>> 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 time.
>>
>> Please help.
>>
>> Regards,
>> Raj Shaikh
>> MASTEK LTD.
>> 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.
>> MASTEK LTD.
>> 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.
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> ~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> --
> Lee Burrows
> ActionScripter
>
> MASTEK LTD.
> 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.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
Lee Burrows
ActionScripter
MASTEK LTD.
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.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
MASTEK LTD.
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.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
RE: compc additional compiler arguments
Posted by "Raj U. Shaikh" <Ra...@mastek.com>.
Hi Chris,
Please find attached library project depicting additional compiler arguments using "-define=CONFIG::Version"
I consider there is no way to define custom arguments in compc and there my problem stands. (While mxmlc supports -define parameter)
I am wondering why there is no support in compc?
Regards,
Raj Shaikh
-----Original Message-----
From: Christofer Dutz [mailto:christofer.dutz@c-ware.de]
Sent: Friday, April 11, 2014 8:01 PM
To: users@flex.apache.org
Subject: AW: compc additional compiler arguments
Hi,
well I'm stil at the ApacheCon so I don't quite have the time right now, but If you could whip up a small maven project demonstrating this problem, zip it up and send it to my private email. I'lll try to check it out. Unfortunately there currently seems to be a problem preventing us from registering new users on the Fllexmojos Jira :-(
Chris
-----Ursprüngliche Nachricht-----
Von: Raj U. Shaikh [mailto:Raj.Shaikh@mastek.com]
Gesendet: Freitag, 11. April 2014 08:18
An: users@flex.apache.org
Betreff: RE: compc additional compiler arguments
I am using flexmojos and I can use these task into pom as follows,
<compiler>
<define>
<name>CONFIG::version</name>
<value>MyVersion</value>
</define>
</compiler>
Also, I tried following as well,
<define name="CONFIG::version" value"MyVersion"/>
But I get following error,
D:\eclipse_workspace\icd\8.6.0.0_Library>mvn compile
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building ICD Library 5.38.0.18-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ ICDLibrary ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 69 resources
[INFO]
[INFO] --- flexmojos-maven-plugin:4.1-beta:compile-swc (default-compile-swc) @ ICDLibrary ---
[INFO] Flexmojos 4.1-beta
[INFO] Apache License - Version 2.0 (NO WARRANTY) - See COPYRIGHT file
[WARNING] No themes are explicitly defined in the <theme> section or in any scope="theme" dependencies. Flexmojos is now attempting to figure out which themes to include. (to avoid this warning you should explicitly state your theme dependencies)
[WARNING] Adding spark.css theme because spark.swc was included as a dependency
[INFO] Writing configuration dump to D:\eclipse_workspace\icd\8.6.0.0_Library\target\ICDLibrary-5.38.0.18-SNAPSHOT-configs.xml
[ERROR] D:\eclipse_workspace\icd\8.6.0.0_Library\src\main\flex\com\majescomastek\stgicd\ui\module\BaseModule.as:[92,11] Access of undefined property version. CONFIG::version
[ERROR] D:\eclipse_workspace\icd\8.6.0.0_Library\src\main\flex\com\majescomastek\stgicd\ui\module\BaseModule.as:[92,11] Access of undefined property version. CONFIG::version
[ERROR] D:\eclipse_workspace\icd\8.6.0.0_Library\src\main\flex\com\majescomastek\stgicd\ui\module\BaseModule.as:[92,11] Access of undefined property version. CONFIG::version
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4.171s
[INFO] Finished at: Fri Apr 11 11:43:14 IST 2014
[INFO] Final Memory: 10M/76M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.sonatype.flexmojos:flexmojos-maven-plugin:4.1-beta:compile-swc (default-compile-swc) on project ICDLibrary: Got 3 errors building project, check logs -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
I believe down the line it uses compc and in api documents there is no mention of define namespace.
Am I missing something?
-----Original Message-----
From: Christofer Dutz [mailto:christofer.dutz@c-ware.de]
Sent: Thursday, April 10, 2014 9:27 PM
To: users@flex.apache.org
Subject: AW: compc additional compiler arguments
If you are talking about flexmojos. This should be possible by adding that to the configuration element of the plugin. There should be an example in the flexmojos test suite.
Chris
Gesendet mit meinem HTC
----- Reply message -----
Von: "Lee Burrows" <su...@leeburrows.com>
An: "users@flex.apache.org" <us...@flex.apache.org>
Betreff: compc additional compiler arguments
Datum: Do., Apr. 10, 2014 08:53
I dont use maven so i cant answer that
On 10/04/2014 15:40, Raj U. Shaikh wrote:
> Can I able to add this in pom xml(maven)? I searched on it but no clues..
>
> -----Original Message-----
> From: Lee Burrows [mailto:subscriptions@leeburrows.com]
> Sent: Thursday, April 10, 2014 7:14 PM
> To: users@flex.apache.org
> Subject: Re: compc additional compiler arguments
>
> Ignore my previous email with docs link ;(
>
> You can add custom arguments to config files like so:
>
> <compiler>
> <define>
> <name>NAMESPACE::variable</name>
> <value>your-value</value>
> </define>
> </compiler>
>
> On 10/04/2014 14:20, Raj U. Shaikh wrote:
>> Virat,
>>
>> I am looking for custom arguments and not the predefined ones.
>>
>> Regards,
>> Raj Shaikh
>>
>> -----Original Message-----
>> From: Patil, Virat [mailto:virat.patil@capgemini.com]
>> Sent: Thursday, April 10, 2014 5:21 PM
>> To: users@flex.apache.org
>> Cc: Yogesh C. Jadhav
>> Subject: RE: compc additional compiler arguments
>>
>> 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 Problem
>>
>> You want to compile a Flex component into a SWC file that can be used as a runtime shared library (RSL).
>>
>> Solution
>>
>> 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.
>>
>> Discussion
>>
>> 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:
>>
>> -benchmark
>> Indicates that the compiler should benchmark the amount of time needed to compile the SWC.
>> -compiler.debug
>> 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.
>> -compiler.optimize
>> 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.
>> -compiler.use-resource-bundle-metadata
>> 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 compilation.
>> -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.
>> -use-network
>> 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 option:
>>
>> <include-sources>src/.</include-sources>
>>
>>
>>
>> Regards
>> 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
>>
>> -define=NAMESPACE::variable,value
>>
>> 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 time.
>>
>> Please help.
>>
>> Regards,
>> Raj Shaikh
>> MASTEK LTD.
>> 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.
>> MASTEK LTD.
>> 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.
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> ~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> --
> Lee Burrows
> ActionScripter
>
> MASTEK LTD.
> 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.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
Lee Burrows
ActionScripter
MASTEK LTD.
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.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
MASTEK LTD.
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.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
AW: compc additional compiler arguments
Posted by Christofer Dutz <ch...@c-ware.de>.
Hi,
well I'm stil at the ApacheCon so I don't quite have the time right now, but If you could whip up a small maven project demonstrating this problem, zip it up and send it to my private email. I'lll try to check it out. Unfortunately there currently seems to be a problem preventing us from registering new users on the Fllexmojos Jira :-(
Chris
-----Ursprüngliche Nachricht-----
Von: Raj U. Shaikh [mailto:Raj.Shaikh@mastek.com]
Gesendet: Freitag, 11. April 2014 08:18
An: users@flex.apache.org
Betreff: RE: compc additional compiler arguments
I am using flexmojos and I can use these task into pom as follows,
<compiler>
<define>
<name>CONFIG::version</name>
<value>MyVersion</value>
</define>
</compiler>
Also, I tried following as well,
<define name="CONFIG::version" value"MyVersion"/>
But I get following error,
D:\eclipse_workspace\icd\8.6.0.0_Library>mvn compile
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building ICD Library 5.38.0.18-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ ICDLibrary ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 69 resources
[INFO]
[INFO] --- flexmojos-maven-plugin:4.1-beta:compile-swc (default-compile-swc) @ ICDLibrary ---
[INFO] Flexmojos 4.1-beta
[INFO] Apache License - Version 2.0 (NO WARRANTY) - See COPYRIGHT file
[WARNING] No themes are explicitly defined in the <theme> section or in any scope="theme" dependencies. Flexmojos is now attempting to figure out which themes to include. (to avoid this warning you should explicitly state your theme dependencies)
[WARNING] Adding spark.css theme because spark.swc was included as a dependency
[INFO] Writing configuration dump to D:\eclipse_workspace\icd\8.6.0.0_Library\target\ICDLibrary-5.38.0.18-SNAPSHOT-configs.xml
[ERROR] D:\eclipse_workspace\icd\8.6.0.0_Library\src\main\flex\com\majescomastek\stgicd\ui\module\BaseModule.as:[92,11] Access of undefined property version. CONFIG::version
[ERROR] D:\eclipse_workspace\icd\8.6.0.0_Library\src\main\flex\com\majescomastek\stgicd\ui\module\BaseModule.as:[92,11] Access of undefined property version. CONFIG::version
[ERROR] D:\eclipse_workspace\icd\8.6.0.0_Library\src\main\flex\com\majescomastek\stgicd\ui\module\BaseModule.as:[92,11] Access of undefined property version. CONFIG::version
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4.171s
[INFO] Finished at: Fri Apr 11 11:43:14 IST 2014
[INFO] Final Memory: 10M/76M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.sonatype.flexmojos:flexmojos-maven-plugin:4.1-beta:compile-swc (default-compile-swc) on project ICDLibrary: Got 3 errors building project, check logs -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
I believe down the line it uses compc and in api documents there is no mention of define namespace.
Am I missing something?
-----Original Message-----
From: Christofer Dutz [mailto:christofer.dutz@c-ware.de]
Sent: Thursday, April 10, 2014 9:27 PM
To: users@flex.apache.org
Subject: AW: compc additional compiler arguments
If you are talking about flexmojos. This should be possible by adding that to the configuration element of the plugin. There should be an example in the flexmojos test suite.
Chris
Gesendet mit meinem HTC
----- Reply message -----
Von: "Lee Burrows" <su...@leeburrows.com>
An: "users@flex.apache.org" <us...@flex.apache.org>
Betreff: compc additional compiler arguments
Datum: Do., Apr. 10, 2014 08:53
I dont use maven so i cant answer that
On 10/04/2014 15:40, Raj U. Shaikh wrote:
> Can I able to add this in pom xml(maven)? I searched on it but no clues..
>
> -----Original Message-----
> From: Lee Burrows [mailto:subscriptions@leeburrows.com]
> Sent: Thursday, April 10, 2014 7:14 PM
> To: users@flex.apache.org
> Subject: Re: compc additional compiler arguments
>
> Ignore my previous email with docs link ;(
>
> You can add custom arguments to config files like so:
>
> <compiler>
> <define>
> <name>NAMESPACE::variable</name>
> <value>your-value</value>
> </define>
> </compiler>
>
> On 10/04/2014 14:20, Raj U. Shaikh wrote:
>> Virat,
>>
>> I am looking for custom arguments and not the predefined ones.
>>
>> Regards,
>> Raj Shaikh
>>
>> -----Original Message-----
>> From: Patil, Virat [mailto:virat.patil@capgemini.com]
>> Sent: Thursday, April 10, 2014 5:21 PM
>> To: users@flex.apache.org
>> Cc: Yogesh C. Jadhav
>> Subject: RE: compc additional compiler arguments
>>
>> 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 Problem
>>
>> You want to compile a Flex component into a SWC file that can be used as a runtime shared library (RSL).
>>
>> Solution
>>
>> 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.
>>
>> Discussion
>>
>> 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:
>>
>> -benchmark
>> Indicates that the compiler should benchmark the amount of time needed to compile the SWC.
>> -compiler.debug
>> 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.
>> -compiler.optimize
>> 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.
>> -compiler.use-resource-bundle-metadata
>> 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 compilation.
>> -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.
>> -use-network
>> 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 option:
>>
>> <include-sources>src/.</include-sources>
>>
>>
>>
>> Regards
>> 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
>>
>> -define=NAMESPACE::variable,value
>>
>> 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 time.
>>
>> Please help.
>>
>> Regards,
>> Raj Shaikh
>> MASTEK LTD.
>> 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.
>> MASTEK LTD.
>> 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.
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> ~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> --
> Lee Burrows
> ActionScripter
>
> MASTEK LTD.
> 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.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
Lee Burrows
ActionScripter
MASTEK LTD.
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.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
RE: compc additional compiler arguments
Posted by "Raj U. Shaikh" <Ra...@mastek.com>.
I am using flexmojos and I can use these task into pom as follows,
<compiler>
<define>
<name>CONFIG::version</name>
<value>MyVersion</value>
</define>
</compiler>
Also, I tried following as well,
<define name="CONFIG::version" value"MyVersion"/>
But I get following error,
D:\eclipse_workspace\icd\8.6.0.0_Library>mvn compile
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building ICD Library 5.38.0.18-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ ICDLibrary ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 69 resources
[INFO]
[INFO] --- flexmojos-maven-plugin:4.1-beta:compile-swc (default-compile-swc) @ ICDLibrary ---
[INFO] Flexmojos 4.1-beta
[INFO] Apache License - Version 2.0 (NO WARRANTY) - See COPYRIGHT file
[WARNING] No themes are explicitly defined in the <theme> section or in any scope="theme" dependencies. Flexmojos is now attempting to figure out which themes to include. (to avoid this warning you should explicitly state your theme dependencies)
[WARNING] Adding spark.css theme because spark.swc was included as a dependency
[INFO] Writing configuration dump to D:\eclipse_workspace\icd\8.6.0.0_Library\target\ICDLibrary-5.38.0.18-SNAPSHOT-configs.xml
[ERROR] D:\eclipse_workspace\icd\8.6.0.0_Library\src\main\flex\com\majescomastek\stgicd\ui\module\BaseModule.as:[92,11] Access of undefined property version. CONFIG::version
[ERROR] D:\eclipse_workspace\icd\8.6.0.0_Library\src\main\flex\com\majescomastek\stgicd\ui\module\BaseModule.as:[92,11] Access of undefined property version. CONFIG::version
[ERROR] D:\eclipse_workspace\icd\8.6.0.0_Library\src\main\flex\com\majescomastek\stgicd\ui\module\BaseModule.as:[92,11] Access of undefined property version. CONFIG::version
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4.171s
[INFO] Finished at: Fri Apr 11 11:43:14 IST 2014
[INFO] Final Memory: 10M/76M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.sonatype.flexmojos:flexmojos-maven-plugin:4.1-beta:compile-swc (default-compile-swc) on project ICDLibrary: Got 3 errors building project, check logs -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
I believe down the line it uses compc and in api documents there is no mention of define namespace.
Am I missing something?
-----Original Message-----
From: Christofer Dutz [mailto:christofer.dutz@c-ware.de]
Sent: Thursday, April 10, 2014 9:27 PM
To: users@flex.apache.org
Subject: AW: compc additional compiler arguments
If you are talking about flexmojos. This should be possible by adding that to the configuration element of the plugin. There should be an example in the flexmojos test suite.
Chris
Gesendet mit meinem HTC
----- Reply message -----
Von: "Lee Burrows" <su...@leeburrows.com>
An: "users@flex.apache.org" <us...@flex.apache.org>
Betreff: compc additional compiler arguments
Datum: Do., Apr. 10, 2014 08:53
I dont use maven so i cant answer that
On 10/04/2014 15:40, Raj U. Shaikh wrote:
> Can I able to add this in pom xml(maven)? I searched on it but no clues..
>
> -----Original Message-----
> From: Lee Burrows [mailto:subscriptions@leeburrows.com]
> Sent: Thursday, April 10, 2014 7:14 PM
> To: users@flex.apache.org
> Subject: Re: compc additional compiler arguments
>
> Ignore my previous email with docs link ;(
>
> You can add custom arguments to config files like so:
>
> <compiler>
> <define>
> <name>NAMESPACE::variable</name>
> <value>your-value</value>
> </define>
> </compiler>
>
> On 10/04/2014 14:20, Raj U. Shaikh wrote:
>> Virat,
>>
>> I am looking for custom arguments and not the predefined ones.
>>
>> Regards,
>> Raj Shaikh
>>
>> -----Original Message-----
>> From: Patil, Virat [mailto:virat.patil@capgemini.com]
>> Sent: Thursday, April 10, 2014 5:21 PM
>> To: users@flex.apache.org
>> Cc: Yogesh C. Jadhav
>> Subject: RE: compc additional compiler arguments
>>
>> 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 Problem
>>
>> You want to compile a Flex component into a SWC file that can be used as a runtime shared library (RSL).
>>
>> Solution
>>
>> 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.
>>
>> Discussion
>>
>> 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:
>>
>> -benchmark
>> Indicates that the compiler should benchmark the amount of time needed to compile the SWC.
>> -compiler.debug
>> 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.
>> -compiler.optimize
>> 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.
>> -compiler.use-resource-bundle-metadata
>> 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 compilation.
>> -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.
>> -use-network
>> 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 option:
>>
>> <include-sources>src/.</include-sources>
>>
>>
>>
>> Regards
>> 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
>>
>> -define=NAMESPACE::variable,value
>>
>> 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 time.
>>
>> Please help.
>>
>> Regards,
>> Raj Shaikh
>> MASTEK LTD.
>> 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.
>> MASTEK LTD.
>> 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.
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> ~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> --
> Lee Burrows
> ActionScripter
>
> MASTEK LTD.
> 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.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
Lee Burrows
ActionScripter
MASTEK LTD.
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.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
AW: compc additional compiler arguments
Posted by Christofer Dutz <ch...@c-ware.de>.
If you are talking about flexmojos. This should be possible by adding that to the configuration element of the plugin. There should be an example in the flexmojos test suite.
Chris
Gesendet mit meinem HTC
----- Reply message -----
Von: "Lee Burrows" <su...@leeburrows.com>
An: "users@flex.apache.org" <us...@flex.apache.org>
Betreff: compc additional compiler arguments
Datum: Do., Apr. 10, 2014 08:53
I dont use maven so i cant answer that
On 10/04/2014 15:40, Raj U. Shaikh wrote:
> Can I able to add this in pom xml(maven)? I searched on it but no clues..
>
> -----Original Message-----
> From: Lee Burrows [mailto:subscriptions@leeburrows.com]
> Sent: Thursday, April 10, 2014 7:14 PM
> To: users@flex.apache.org
> Subject: Re: compc additional compiler arguments
>
> Ignore my previous email with docs link ;(
>
> You can add custom arguments to config files like so:
>
> <compiler>
> <define>
> <name>NAMESPACE::variable</name>
> <value>your-value</value>
> </define>
> </compiler>
>
> On 10/04/2014 14:20, Raj U. Shaikh wrote:
>> Virat,
>>
>> I am looking for custom arguments and not the predefined ones.
>>
>> Regards,
>> Raj Shaikh
>>
>> -----Original Message-----
>> From: Patil, Virat [mailto:virat.patil@capgemini.com]
>> Sent: Thursday, April 10, 2014 5:21 PM
>> To: users@flex.apache.org
>> Cc: Yogesh C. Jadhav
>> Subject: RE: compc additional compiler arguments
>>
>> 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 Problem
>>
>> You want to compile a Flex component into a SWC file that can be used as a runtime shared library (RSL).
>>
>> Solution
>>
>> 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.
>>
>> Discussion
>>
>> 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:
>>
>> -benchmark
>> Indicates that the compiler should benchmark the amount of time needed to compile the SWC.
>> -compiler.debug
>> 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.
>> -compiler.optimize
>> 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.
>> -compiler.use-resource-bundle-metadata
>> 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 compilation.
>> -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.
>> -use-network
>> 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 option:
>>
>> <include-sources>src/.</include-sources>
>>
>>
>>
>> Regards
>> 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
>>
>> -define=NAMESPACE::variable,value
>>
>> 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 time.
>>
>> Please help.
>>
>> Regards,
>> Raj Shaikh
>> MASTEK LTD.
>> 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.
>> MASTEK LTD.
>> 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.
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> --
> Lee Burrows
> ActionScripter
>
> MASTEK LTD.
> 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.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
Lee Burrows
ActionScripter
Re: compc additional compiler arguments
Posted by Lee Burrows <su...@leeburrows.com>.
I dont use maven so i cant answer that
On 10/04/2014 15:40, Raj U. Shaikh wrote:
> Can I able to add this in pom xml(maven)? I searched on it but no clues..
>
> -----Original Message-----
> From: Lee Burrows [mailto:subscriptions@leeburrows.com]
> Sent: Thursday, April 10, 2014 7:14 PM
> To: users@flex.apache.org
> Subject: Re: compc additional compiler arguments
>
> Ignore my previous email with docs link ;(
>
> You can add custom arguments to config files like so:
>
> <compiler>
> <define>
> <name>NAMESPACE::variable</name>
> <value>your-value</value>
> </define>
> </compiler>
>
> On 10/04/2014 14:20, Raj U. Shaikh wrote:
>> Virat,
>>
>> I am looking for custom arguments and not the predefined ones.
>>
>> Regards,
>> Raj Shaikh
>>
>> -----Original Message-----
>> From: Patil, Virat [mailto:virat.patil@capgemini.com]
>> Sent: Thursday, April 10, 2014 5:21 PM
>> To: users@flex.apache.org
>> Cc: Yogesh C. Jadhav
>> Subject: RE: compc additional compiler arguments
>>
>> 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 Problem
>>
>> You want to compile a Flex component into a SWC file that can be used as a runtime shared library (RSL).
>>
>> Solution
>>
>> 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.
>>
>> Discussion
>>
>> 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:
>>
>> -benchmark
>> Indicates that the compiler should benchmark the amount of time needed to compile the SWC.
>> -compiler.debug
>> 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.
>> -compiler.optimize
>> 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.
>> -compiler.use-resource-bundle-metadata
>> 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 compilation.
>> -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.
>> -use-network
>> 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 option:
>>
>> <include-sources>src/.</include-sources>
>>
>>
>>
>> Regards
>> 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
>>
>> -define=NAMESPACE::variable,value
>>
>> 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 time.
>>
>> Please help.
>>
>> Regards,
>> Raj Shaikh
>> MASTEK LTD.
>> 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.
>> MASTEK LTD.
>> 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.
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> --
> Lee Burrows
> ActionScripter
>
> MASTEK LTD.
> 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.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
Lee Burrows
ActionScripter
RE: compc additional compiler arguments
Posted by "Raj U. Shaikh" <Ra...@mastek.com>.
Can I able to add this in pom xml(maven)? I searched on it but no clues..
-----Original Message-----
From: Lee Burrows [mailto:subscriptions@leeburrows.com]
Sent: Thursday, April 10, 2014 7:14 PM
To: users@flex.apache.org
Subject: Re: compc additional compiler arguments
Ignore my previous email with docs link ;(
You can add custom arguments to config files like so:
<compiler>
<define>
<name>NAMESPACE::variable</name>
<value>your-value</value>
</define>
</compiler>
On 10/04/2014 14:20, Raj U. Shaikh wrote:
> Virat,
>
> I am looking for custom arguments and not the predefined ones.
>
> Regards,
> Raj Shaikh
>
> -----Original Message-----
> From: Patil, Virat [mailto:virat.patil@capgemini.com]
> Sent: Thursday, April 10, 2014 5:21 PM
> To: users@flex.apache.org
> Cc: Yogesh C. Jadhav
> Subject: RE: compc additional compiler arguments
>
> 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 Problem
>
> You want to compile a Flex component into a SWC file that can be used as a runtime shared library (RSL).
>
> Solution
>
> 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.
>
> Discussion
>
> 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:
>
> -benchmark
> Indicates that the compiler should benchmark the amount of time needed to compile the SWC.
> -compiler.debug
> 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.
> -compiler.optimize
> 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.
> -compiler.use-resource-bundle-metadata
> 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 compilation.
> -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.
> -use-network
> 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 option:
>
> <include-sources>src/.</include-sources>
>
>
>
> Regards
> 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
>
> -define=NAMESPACE::variable,value
>
> 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 time.
>
> Please help.
>
> Regards,
> Raj Shaikh
> MASTEK LTD.
> 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.
> MASTEK LTD.
> 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.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
Lee Burrows
ActionScripter
MASTEK LTD.
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.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Re: compc additional compiler arguments
Posted by Lee Burrows <su...@leeburrows.com>.
Ignore my previous email with docs link ;(
You can add custom arguments to config files like so:
<compiler>
<define>
<name>NAMESPACE::variable</name>
<value>your-value</value>
</define>
</compiler>
On 10/04/2014 14:20, Raj U. Shaikh wrote:
> Virat,
>
> I am looking for custom arguments and not the predefined ones.
>
> Regards,
> Raj Shaikh
>
> -----Original Message-----
> From: Patil, Virat [mailto:virat.patil@capgemini.com]
> Sent: Thursday, April 10, 2014 5:21 PM
> To: users@flex.apache.org
> Cc: Yogesh C. Jadhav
> Subject: RE: compc additional compiler arguments
>
> 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 Problem
>
> You want to compile a Flex component into a SWC file that can be used as a runtime shared library (RSL).
>
> Solution
>
> 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.
>
> Discussion
>
> 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:
>
> -benchmark
> Indicates that the compiler should benchmark the amount of time needed to compile the SWC.
> -compiler.debug
> 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.
> -compiler.optimize
> 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.
> -compiler.use-resource-bundle-metadata
> 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 compilation.
> -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.
> -use-network
> 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 option:
>
> <include-sources>src/.</include-sources>
>
>
>
> Regards
> 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
>
> -define=NAMESPACE::variable,value
>
> 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 time.
>
> Please help.
>
> Regards,
> Raj Shaikh
> MASTEK LTD.
> 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.
> MASTEK LTD.
> 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.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
Lee Burrows
ActionScripter
Re: compc additional compiler arguments
Posted by Lee Burrows <su...@leeburrows.com>.
This is available in compc. see
http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf69084-7a92.html
On 10/04/2014 14:20, Raj U. Shaikh wrote:
> Hi All,
>
> In mxmlc we have an option to define additional compiler arguments in following way
>
> -define=NAMESPACE::variable,value
>
> 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 time.
>
> Please help.
>
> Regards,
--
Lee Burrows
ActionScripter
RE: compc additional compiler arguments
Posted by "Raj U. Shaikh" <Ra...@mastek.com>.
Virat,
I am looking for custom arguments and not the predefined ones.
Regards,
Raj Shaikh
-----Original Message-----
From: Patil, Virat [mailto:virat.patil@capgemini.com]
Sent: Thursday, April 10, 2014 5:21 PM
To: users@flex.apache.org
Cc: Yogesh C. Jadhav
Subject: RE: compc additional compiler arguments
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 Problem
You want to compile a Flex component into a SWC file that can be used as a runtime shared library (RSL).
Solution
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.
Discussion
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:
-benchmark
Indicates that the compiler should benchmark the amount of time needed to compile the SWC.
-compiler.debug
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.
-compiler.optimize
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.
-compiler.use-resource-bundle-metadata
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 compilation.
-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.
-use-network
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 option:
<include-sources>src/.</include-sources>
Regards
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
-define=NAMESPACE::variable,value
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 time.
Please help.
Regards,
Raj Shaikh
MASTEK LTD.
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.
MASTEK LTD.
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.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
RE: compc additional compiler arguments
Posted by "Patil, Virat" <vi...@capgemini.com>.
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
Problem
You want to compile a Flex component into a SWC file that can be used as a runtime shared library (RSL).
Solution
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.
Discussion
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:
-benchmark
Indicates that the compiler should benchmark the amount of time needed to compile the SWC.
-compiler.debug
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.
-compiler.optimize
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.
-compiler.use-resource-bundle-metadata
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 compilation.
-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.
-use-network
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 option:
<include-sources>src/.</include-sources>
Regards
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
-define=NAMESPACE::variable,value
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 time.
Please help.
Regards,
Raj Shaikh
MASTEK LTD.
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.