Friday, March 11, 2011

Titanium Developer And Android SDK On Windows

Hi


OS : Windows XP SP3


I spent a few hours trying to get Titanium Developer working to recognise my installation of the Android SDK.  On selection of Android SDK's default platform directory, C:\Program Files\Android\android-sdk, for example, Titanium would report that it could not find "adb" and required to be pointed to the folder that contained the folders "add-ons", "platforms" and "tools" folders.




On looking a little further inside folders, I found that the Android SDK had changed things around.  In the folder, C:\Program Files\Android\android-sdk\tools, there is a file "adb_has_moved.txt".  This file reads



The adb tool has moved to platform-tools/


If you don't see this directory in your SDK,
launch the SDK and AVD Manager (execute the android tool)
and install "Android SDK Platform-tools"


Please also update your PATH environment variable to
include the platform-tools/ directory, so you can
execute adb from any location.

Titanium expects to find adb.exe in C:\Program Files\Android\android-sdk\tools folder.

This is what my Titanium config screen looks like



Without adb.exe in C:\Program Files\Android\android-sdk\tools, Titanium refuses to work and reports this error




This is what my Android SDK folder structure looks like





SOLUTION



One of the solutions I had found was to add  c:\Program Files\Android\android-sdk\platform-tools to the computer's PATH.  That did not work for me.


I had to take adb.exe from c:\Program Files\Android\android-sdk\platform-tools and copy it to c:\Program Files\Android\android-sdk\tools folder.


Post this, Titanium happily found adb.exe and I could get a zero line Android app running in the emulator in under 10 minutes.


It seems like Titanium tries to execute a fixed path c:\Program Files\Android\android-sdk\tools\adb.exe - instead of using Windows PATH settings.  


That does not sound right or possible, though.


Hope this saves someone some time.




No comments:

Post a Comment