Please note the information on this page is currently incomplete . Missing are topics such as using ANT and MAVEN.
Manual Compilation
If you are not yet using a build script such as ANT or MAVEN, and want to build specific platforms for your FlexJS Application, these command line templates can help get you started. You should be able to cut and paste the command lines to a terminal session, but you will need to define some environment variables first unless you edit the command lines before they are put into a terminal session.
FLEXJS_HOME | The directory location of the Apache FlexJS installation. It should have a frameworks sub-directory. |
PLAYERGLOBAL_HOME | The full path to the directory containing playerglobal.swc files. This directory should contain version sub-directories such as 11.1 |
PLAYERGLOBAL_VERSION | The version of the playerglobal.swc to use, such as 11.1 |
FALCON_HOME | The directory location of the Apache Flex Falcon compiler. This directory should contain a compiler.jx sub-directory. |
GOOG_HOME | The directory location of the Google Closure library. |
Creating SWF Output Only
Be sure to set the values for the FLEXJS_HOME
, PLAYERGLOBAL_VERSION
, and PLAYERGLOBAL_HOME
environment variables as indicated above.
Code Block | ||||
---|---|---|---|---|
| ||||
mxmlc +flexlib=${FLEXJS_HOME}/frameworks -debug -define=CONFIG::theme,false \
-compiler.mxml.children-as-data -compiler.binding-value-change-event=org.apache.flex.events.ValueChangeEvent \
-compiler.binding-value-change-event-kind=org.apache.flex.events.ValueChangeEvent \
-compiler.binding-value-change-event-type=valueChange +playerglobal.version=${PLAYERGLOBAL_VERSION} \
+env.PLAYERGLOBAL_HOME=${PLAYERGLOBAL_HOME} FILENAME.MXML |
Substitute FILENAME.MXML
with the application's main source MXML file. The above command line will generate a FILENAME.swf
file in the current directory.
The Windows command line is similar.
Creating js-debug Output Only
Be sure to set the values for the FLEXJS_HOME
, FALCON_HOME
, PLAYERGLOBAL_VERSION
, PLAYERGLOBAL_HOME
, and GOOG_HOME
environment variables as indicated above.
Code Block | ||||
---|---|---|---|---|
| ||||
/Library/Java/JavaVirtualMachines/jdk1.7.0_75.jdk/Contents/Home/jre/bin/java -Xms64m -Xmx384m -ea \
-Dapple.awt.UIElement=true -Dflexlib=${FLEXJS_HOME}/frameworks -jar ${FALCON_HOME}/compiler.jx/lib/mxmlc.jar \
+flexlib=${FLEXJS_HOME}/frameworks -debug=true -define=CONFIG::theme,false -compiler.mxml.children-as-data \
-compiler.binding-value-change-event=org.apache.flex.events.ValueChangeEvent \
-compiler.binding-value-change-event-kind=org.apache.flex.events.ValueChangeEvent \
-compiler.binding-value-change-event-type=valueChange +playerglobal.version=${PLAYERGLOBAL_VERSION} \
+env.PLAYERGLOBAL_HOME=${PLAYERGLOBAL_HOME} -define=CONFIG::extlib,false -js-output-optimization=skipAsCoercions \
-define=CONFIG::opt2,false -js-output-type=FLEXJS -closure-lib=${GOOG_HOME} \
-sdk-js-lib=${FLEXJS_HOME}/frameworks/js/FlexJS/libs -output=. FILENAME.MXML |
Substitute FILENAME.MXML
with the application's main source MXML file. The above command will generate a bin/js-debug
directory structure in the current directory and place the resulting artifacts in the js-debug
directory, including an index.html
file which can be opened by a browser.
The Windows command line is similar.
...
and is serving as a place holder for more details about the build process for FlexJS applications.