-
Couldn't load subscription status.
- Fork 116
Building From Source
Josh Tynjala edited this page Jul 16, 2019
·
5 revisions
The Royale SDK can be built using either ant or maven. Below are instructions for both.
- Java 7 or later should be installed.
- Apache Ant should be installed.
- Clone the Royale Framework repo.
- Make sure you are using the
developbranch. - Open the folder of the cloned repo in a terminal.
- Run
ant all.
This will clone all the necessary repos and build them all in the correct order. It will also add the necessary files to use the royale-asjs folder as a working SDK. You should be able to point your IDE (i.e. VS Code, Moonshine, Flash Builder, etc.) to the royale-asjs folder and it should be recognized and "just work".
- If you are working on Framework features, once the original
ant allis run, you should be able to build individual swcs by running ant on the specific project. - To make changes to the new js swcs available in active projects, you need to clean the project and remove the old .js files in the
bin/js-debugfolder. Those files are not overwritten by default. - The above instructions does not include any environment variables. For a basic build, none are needed. However, for a full build which runs all tests, additional environment variables can be specified.
-
PLAYERGLOBAL_HOMEshould point to a folder which has sub-folders with the playerglobal files. The structure should be[version_number]/playerglobal.swcwhereversion_numberis the specific version(s) being used. -
AIR_HOMEshould point to an AIR SDK folder -
FLASHPLAYER_DEBUGGERshould point to the Flash Player debugged executable. On Mac, it should point to the executable inside the app package. -
GOOG_HOMECan point to a folder containingclosure-library. Using the environment variable can save some time and prevent downloading the closure files after cleaning. -
ROYALE_COMPILER_REPOcan be used to point the build to aroyale-compilerclone in some place other than the default location. -
ROYALE_TYPEDEFS_HOMEcan be used to point the build to aroyale-typedefsclone in some place other than the default location.
-
Apache®, Apache Royale, Royale™, and the Royale logo are either registered trademarks or trademarks of the Apache Software Foundation in the United States and/or other countries.