Titanium Community Questions & Answer Archive

We felt that 6+ years of knowledge should not die so this is the Titanium Community Questions & Answer Archive

Mobilesdk install under /Library or ~/Library on OS X?

I inherited a coworker's Mac running an old beta (0.8) of the mobilesdk. So several weeks ago I downloaded and installed a fresh copy of Titanium Developer 1.2.1 (plus SDK 1.4).

I had many problems building and running, and finally figured out that there was still an old copy of the 0.8 beta mobilesdk in /Library/Application Support/Titanium/mobilesdk/osx, even though my new sdk's were installed in ~/Library/Application Support/Titanium/mobilesdk/osx (i.e., the beta was installed in the Library at root [/] but my new ones were installed in the Library in my user directory [~/]). After clearing out the mobilesdk directory on the root Library, everything was fine.

When Titanium SDK was upgraded to 1.4.1 and, it auto installed correctly to my user directory's Library.

Today, when 1.4.2 auto installed, it installed back in the root Library.

Can someone tell me which is correct? Should the mobilesdk be installing at /Library or ~/Library? Does it matter if some sdk's are in one and some in the other? In both cases, my account has read/write permissions but the admin account has read-only access. That doesn't sound right for something in /Library.


— asked November 12th 2010 by Lou M
  • 1.4.2
  • install
  • mac
  • mobile
  • osx

2 Answers

  • Accepted Answer

    In case this still of any use to you Lou, these are the official install instructions for the Continuous (nightly) SDK Builds.

    — answered November 19th 2010 by Paul Dowsett
  • Hi Lou,

    As far as I know the correct path for all of the different mobilesdk versions should be /Library. That's where they've always been on my Mac's anyway.

    — answered November 12th 2010 by Dan Giulvezan
    1 Comment
    • If you select Get Info on the folder in the Finder, are you the only one that has read/write permissions? That's what I see, and it's a problem when 2 different developers log onto the same machine on different days and try to update the SDK.

      — commented November 15th 2010 by Lou M
The ownership of individual contributions to this community generated content is retained by the authors of their contributions.
All trademarks remain the property of the respective owner.