How to build and test
Once you have everything configured, building and testing the SDK is easy and fast — it takes only a few minutes. (Fortunately, it's only the first-time setup that requires some effort!)
Selecting what to build
To do a build, first decide whether you want to build the trunk, a branch, or a tag. (Tags are particular releases, such as the 3.0.0.477 release.) Execute
in Cygwin (on Windows) or Terminal (on Macintosh). The environment variables JAVA_HOME, ANT_HOME, and PATH are now set properly for working with that particular branch.
Building
When you build, two things happen:
- First the Java source code for the author-time command-line tools, which is located in the modules directory, is compiled using the J2SDK to create JAR files in the lib directory. This includes the code for the command-line tools mxmlc and compc.
- Then the ActionScript source code for the runtime framework, which is located in the frameworks/projects directory, is compiled using compc to create SWC files in the frameworks/libs and frameworks/locale directories.
To build everything, execute
The -q option tells the build scripts to produce less output so that you don't get overwhelmed.
You should see output similar to this:
You can ignore the messages about deprecated APIs. As you can see, various JARs and SWCs got built.
The information above allows you to build the Free Adobe Flex SDK and not the individual pieces such as the Open Source Flex SDK or the Adobe Add-ons for Open Source Flex SDK.
As we're optimizing the build scripts for each SDK package, build scripts and instructions will follow maybe even before you see this note!
Testing
To test what you've just built, execute
This will compile two test applications and run them in the standalone Flash Player under our automated testing framework (which we call Mustella).
You'll see a Flash Player window open twice and each application will quickly run as if a very fast user were interacting with it. In the Cygwin or Terminal window, you should see output like
Of course, you can combine building and testing in one Ant command:
Developing
You should now be able to use the SDK that you just built to compile an application:
Cleaning
To get rid of all the output files created by building and testing, execute
Switching branches
To work on a different branch, you don't have to open a new shell. Simply cd to the branch and run its setup.sh script:
If you want to restore JAVA_HOME, ANT_HOME, and PATH to their original settings, start a new shell.
| You must be logged in to comment. |
|