{"id":113,"date":"2007-08-19T23:29:39","date_gmt":"2007-08-20T07:29:39","guid":{"rendered":"http:\/\/mlaaker.com\/cms\/?p=113"},"modified":"2007-11-21T00:06:48","modified_gmt":"2007-11-21T08:06:48","slug":"installing-the-adobe-air-sdk-on-a-mac","status":"publish","type":"post","link":"https:\/\/www.laaker.com\/micah\/blog\/2007\/installing-the-adobe-air-sdk-on-a-mac","title":{"rendered":"Installing the Adobe AIR SDK on a Mac"},"content":{"rendered":"

I recently attempted to install the Adobe AIR<\/a> SDK<\/a> on my MacBook Pro so that I could compile AIR applications. While Adobe’s done some great work at developing and exposing their tools early to the public, I could not find a set of instructions that resulted in a working installation. <\/p>\n

Luckily, Yahoo! Developer Network co-worker JR Conlin<\/a> stepped up and helped me fill in a couple blanks. As such, I present my revision to the O’Reilly Adobe Integrated Runtime (AIR) for JavaScript Developers Pocket Guide<\/a> (by Mike Chambers<\/a>, Daniel Dura<\/a>, & Kevin Hoyt<\/a>)… particularly pages 27 and 28, Setting Up the AIR SDK and Command-LineTools:<\/p>\n

\nThere are a number of ways to add the path to the AIR SDK to your system path, depending on which shell you are using, and how you specify user environment variables. <\/p>\n

The instructions below show how to modify your path environment variable if you are using the bash shell. <\/p>\n

    \n
  1. Open the Terminal program (\/Applications\/Utilities\/Terminal) <\/li>\n
  2. Make sure you’re in your home directory by typing\n
    cd<\/pre>\n
     and pressing enter. <\/li>\n
  3. We need to check to see if one of two files are present. Run the following command\n
    ls -la<\/pre>\n<\/li>\n
  4. Look for a file named either.profile or.bashrc. <\/li>\n
  5. If you have neither the .profile or .bashrc file, then create the .profile file with the following command:
    \n touch .profile <\/li>\n
  6. Open the .profile or .bashrc file with a text editor. <\/li>\n
  7. Look for a line that looks similar to this:\n
    export PATH=$PATH:\/usr\/local\/bin<\/pre>\n<\/li>\n
  8. Add the path to the \/bindirectory to the end of this line. For example, if <\/sdk_path>\/bin is at \/airsdk\/bin, the export path should look something like this:\n
    export PATH=$PATH:\/usr\/local\/bin;\/airsdk\/bin<\/pre>\n
    making sure to separate the entries with a colon.<\/sdk_path><\/li>\n
  9. If the file is empty, add the following line:\n
    export PATH=$PATH:\/airsdk\/bin<\/pre>\n<\/li>\n
  10. Save and close the file. <\/li>\n<\/ol>\n<\/blockquote>\n
    Insert:<\/em> Quit Terminal (and other applications), and restart your Mac. (If you don’t restart your Mac, your Terminal application won’t recognize the changes.)<\/p>\n
    \n
      \n
    1. Run the following command to load the new settings source,\n
      .profile<\/pre>\n
       (or <\/p>\n
      .bashrc<\/pre>\n
      , if that is the file you edited). <\/li>\n<\/ol>\n<\/blockquote>\n
      Revise item #11:<\/em> Run the following command to load the new settings source, <\/p>\n
      . .profile<\/pre>\n
       (or <\/p>\n
      . .bashrc<\/pre>\n
      , if that is the file you edited).<\/p>\n
      \n
        \n
      1. You can confirm that the new settings have taken effect by typing\n
        echo $PATH<\/pre>\n
         and pressing Enter. Make sure that the<\/p>\n
        \/bin<\/sdk_path><\/pre>\n
         path is included in the output. <\/li>\n
      2. In order to test the installation, open a Terminal window and type\n
        adt<\/pre>\n
        .
         
        \nYou should see output similar this: <\/p>\n
        Too few arguments.
        \r\nUsage: adt -package air_file app_xml [ file_or_dir | -C dir file_or_dir ... ] ... <\/pre>\n
        meaning that the tools are configured correctly. <\/li>\n<\/ol>\n
        If you get an error that the file cannot be found, then check the following things: <\/p>\n