DISQUS

Laaker.com: Installing the Adobe AIR SDK on a Mac

  • haveboard · 2 years ago
  • Tom · 2 years ago
    Hey there,

    Thanks for the extra info. I still can't get this to work thought! No errors are thrown during the steps and when I do and echo $PATH I get,

    MacPro:~ tom$ echo $PATH
    /bin:/sbin:/usr/bin:/usr/sbin:/applications/airsdk/bin

    I've got the SDK in /tom/applications/airsdk. When I type adt I get

    MacPro:~ tom$ adt
    -bash: adt: command not found

    Any advice?

    Cheers,
    Tom
  • jr · 2 years ago
    Hey Tom:

    Looks like you don't have the right path specified in your $PATH

    Try changing "/applications/airsdk/bin" to "/tom/applications/airsdk/bin" and see if that works for you.
  • kab · 2 years ago
    Hey Tom:

    The Unix under the shiny aqua interface of Mac OS X is very Case sensitive. I think your PATH schould by

    /Application/.. instead of /application/...

    I hope it will work now for you.
  • Ed Prue · 2 years ago
    I can't even get the installer to run. I'm using the one from "air_b1_mac_061107.dmg" (currently on the Adobe web site as of 9/15/07.) It just blows up as soon as I double-click it, with "The application quit unexpectedly" dialog. So far, I haven't been able to find any mentions via Google.
  • micah · 2 years ago
    Sorry, Ed. Don't have a clue why that's happening. It runs just fine on my machine.
  • Ed Prue · 2 years ago
    I solved my own problem. Just happened to be at Stacey's in downtown S.F. on my lunch hour (heh heh - no, I wasn't just there yesterday and the day before that...) flipping through the new O'Reilly pocket guide on AIR, and I stumbled on the fact that you have to be running OS X 10.4.8 or higher to install AIR. Too bad Adobe doesn't plainly say so on the download site. Anyway, now I'm breathing in the AIR experience -- beauty! Hopefully anyone else out there googling "Mac OS X AIR installer doesn't work" - will find this now, instead of nothing.
  • Robyn Tippins · 2 years ago
    I can't get it to install either. Wanted to run snitter. No way am I going through this many steps for that though. ;)
  • Chad · 2 years ago
    I probably didn't get as far as everyone else, I'm guessing it's something minor.

    I downloaded the ebook of the pocket guide to see if there was any additional help there too.

    I'm running leopard. I didn't have a .profile or a .bashrc file. So I typed touch .profile
    perfect. I open it up in the TextMate and it is entirely BLANK.

    So the step where I have to look for a line that is similar to "export PATH=$PATH:/usr/local/bin" doesn't apply because I'm looking at an entirely blank file.

    Any ideas?

    Thanks -- Chad
  • Bob · 1 year ago
    Hey All, I had a lot of trouble installing this too.. finally got it to work by adding the full path to my AIRSDK/bin directory. So, I put this:

    export PATH=$PATH:/Users/bob/Applications/AIRSDK/bin

    It worked for me... thought it might be helpful.

    Also, Mike Chambers posted a link(4/17/08) on his blog to an updated edition of Pocket Guide. Check out his blog(www.mikechambers.com).

    Direct Link to pdf:
    http://onair.adobe.com/files/AIRforJSDevPocketG...
  • MrBonze · 1 year ago
    Thank you! Been Googling for hours trying to find out how to do this! Just a note to avoid confusion that you have to replace the path 'airsdk', with the path where you have the air SDK installed.
  • Stephen Coley · 1 year ago
    I tried setting the path initial, this didn't work, even though I know I set the path correctly. So I thought I would trouble shoot, and just navigate to the /bin from the Terminal. Once I was in the /bin, I "ls -al" to make sure adl and adt were in the directory. Once confirmed, I typed adt... It says the command is not found, so I tried adl, it also said the command was not found. Do you have any idea what my issue could be? I do have the all of the directories included in the download in the same directory as /bin.
  • That Kid from Omaha · 1 year ago
    Hmmm.... sorry, I wish I did, but don't have a clue. You may want to reach out to Mike (from Adobe) over at http://www.mikechambers.com/blog/

    If you find out, please feel free to post back here, in case others are stuck, too.