Props to Motorola for attempting to package all their tools and utilities for Android into one nice package. Thanks, guys. It’s good work. My only complaint is that the emulator doesn’t work really well from within Eclipse. And, I wish Eclipse just flat out performed more like Netbeans, but that’s another story.
Anyway, with the new SDK out, I’m already seeing people have issues with basic setup. So, I dedicate this page to just simply getting things setup and going.
Installing SDK 2.0
MotoDEV doesn’t come packaged with SDK 2.0 Again, that’s a smart move. Doing so would only confuse people. I always say that if you can keep your dev toolkit components loosley coupled, it’s a good thing. If one thing breaks it doesn’t mess up the whole shootin’ match.
So, let’s go over the installation of version 2.0 of the Android SDK. Here are the relevant download links:
- Main SDK web page: http://developer.android.com/sdk/android-2.0.html
- Link to the SDK download itself: http://developer.android.com/sdk/download.html?v=android-sdk_r3-windows.zip
Go grab that zip file and unpack on your drive. My work computer is, for better or worse (usually worse), Vista laptop. So, I unpack it into this directory, just to keep things organized:
It doesn’t matter where y0u unpack it. So, you might as well keep it in the same place as all your other Google software. Here’s what the directory looks like:
. .. add-ons docs platforms temp tools usb_driver SDK Readme.txt SDK Setup.exe
READ SDK Readme.txt. O.K. – I know you won’t, but let’s go on anyway.
Run SDK Setup.exe. When the software tries to connect to the server to discover what packages are available, you’re probably going to get an error and have a problem just like this person had. The error about not being able to connect using HTTPS is weird and frustrating and only applies to a few people (I speculate), but at least the Googlers had the descency to make the workaround obvious enough. Clear the error dialog box and click on the Settings menu item. Click the check box that forces the setup tool to use HTTP instead of HTTPS:
Once you’re done with that, of course, you’re also going to need to upgrade the Android Development Tools (ADT) Plugin for Eclipse. Here’s a handy link for your reference:
If you’ve already installed that, make sure you start Eclipse and go into the software updates screen from the main menu (Help -> Software Updates).
I’m not going to cover the installation of the MOTOdev Studio from Motorola. developer.motorola.com has the installation kit. Go get it and have fun installing. It’s a straightforward and clean process. What I will point out, however, is that you’re going to have to get the normal Eclipse IDE and MOTOdev Studio to play nice. The standard Eclipse installation with the Android SDK and the ADK plugin are not the same as the MOTOdev Studio installation. A short list of things to watch out that I’ve already discovered:
- when you are done using the emulator in MOTOdev studio, kill the emulator process. If you don’t the normal Eclipse installation will see the emulator running and use it to debug your code, but you won’t see it run. That’s because MOTOdev Studio is needed to see that emulator screen. After you kill MOTOdev’s emulator process, the old Eclipse IDE will fire it up for you in a way that you can see it.
Yep – just one item so far.