We currently run a full spectrum of development and testing environments for
our software (Multi-Linux, Mac and Windows), and our automated build/test
server runs linux. In an effort to ensure all engineers and build servers
are using the same SDK versions, we have an SDK repository and externals
linked to our main project.
So this is my quandary: Combining the disparate packages of Flex and AIR
SDK's for each environment is extremely cumbersome:
1. Flex
1. Download Flex SDK
2. Download Flex DVC SDK
3. Download Flex Automation Libs (overlaying with files distributed
with Flex Builder because it's incomplete)
4. Extract in that order to new SDK dir (eg: 3.4.0/)
2. AIR
1. Download AIR SDK (windows)
2. Download AIR SDK (mac)
3. Download AIR SDK (linux)
4. Check for any differences outside of the bin dir (src/swc files)
5. Combine in to common directory
3. Overlay combined AIR directory on top of directory created in 1.4
Anyone who's tried this knows there are some issues with it, like linked
resources in the Mac and Linux AIR player directories, that make it so you
have to complete a few of these steps on a Mac and/or Linux box... And there
are common-named files on each that conflict (for example: adl conflicts
between Mac and Linux, and there are jar file differences between the Linux
AIR SDK and the Windows AIR SDK).
There has to be an easier way to do this. Does anyone know of one? Or should
I file this as a request on bugs.adobe.com?
