Flex SDK’s Blue Print
Every Flex SDK has pretty much the same structure:
- ant – support for ant (flex tasks).
- asdoc – support for generating documentation from ActionScript source files.
- bin – platform dependent launcher
- frameworks – runtime libraries and skins
- lib – Java JAR files used by the launchers in bin and by the Flash Builder IDE.
- runtimes – native AIR framework for OSX.
What’s in the lib folder?
As mentioned earlier SDK’s lib folder contains Java JAR files that are used by the platform dependent launch utilities in the bin folder and by the Flash Builder IDE. There are three JARs that I would like to focus on for now:
- asc.jar – ActionScript compiler
- mxmlc.jar – MXML and ActionScript compiler for creating applications (SWFs).
- compc.jar – MXML and ActionScript compiler for creating libraries (SWCs).
Those are the main three JARs we would need to replace with our cross-compiler versions:
What’s under frameworks?
There is a lot of stuff under Flex SDK’s frameworks folder. In order to keep things simple I will only look at two sub-folders, which I think are the most important ones.
- frameworks/libs is the folder where you can find almost all of the SDK’s SWCs.
In the “regular” Flex SDK you’ll find within the frameworks/libs folder a SWC called player/x.x/playerglobal.swc, which contains the implementation of ActionScript core classes (Object, Array etc) as well as the complete Flash Runtime API (flash.display.* etc).