I’ve recently been looking at developing a cross-platform application on my Linux system for eventual use on Windows and Macintosh. AIR became an obvious choice, because it’s solid on Windows and Macintosh, and supports Linux pretty well as well. I’m still in the midst of development, but I thought I’d post some of my original thoughts on JS/HTML AIR development on Linux.
The first step to developing an AIR application is of course to download the AIR SDK from Adobe. This is available as a download for Linux. Extracting files from a tarball is probably pretty familiar to Linux users, but in case you aren’t familiar with it, I’ll give a short instruction set here.
- Download the file to your home directory (/home/<username>)
- Unzip the directory to your temp directory (mkdir /tmp/air/;cd /tmp/air; tar xvjf /home/<username>/AdobeAIRSDK.tbz2)
- Copy the AIR SDK to the “/opt” directory. (sudo mkdir /opt/air-sdk; sudo cp -r /tmp/air /opt/air-sdk/1.5.2)
- Create a symbolic link to the “current” AIR SDK (sudo ln -s /opt/air-sdk/1.5.2 /opt/air/current)
- Create a script to add the environment variables.
- Setup your environment for your main username. Basically, add to the end of your .profile file “source /opt/air-sdk/current/setup.sh”
#!/bin/sh export PATH=/opt/air-sdk/1.5.2/bin:$PATH
At this point, you should verify (by opening a command window and typing “source ~/.profile”) that your profile is working. If it’s not, fix it and try again. Once you’ve got it working, log all the way out of your linux account, and log back in again. This should make sure that any terminals you launch will have access to the AIR tools (ADL and ADT).
ADL is the primary debugging tool that you’ll use when developing an AIR application. adl is a Java program, and takes as an argument the Application descriptor XML for an AIR application.
ADT is the primary packaging and package signing tool that you will use when “compiling” and “distributing” your AIR application. The adt tool uses the same application xml descriptor as adl, and requires an SSL certificate. You may generate your own “Self Signed” certificate, but it will be less trusted than a real SSL certificate. Finally, when packaging an application using adt you MUST be connected to the internet. ADT verifies the current date with several known timeservers to validate that the certificate is current and not expired. If you are not connected to the internet, ADT WILL fail.