Setup Android SDK Starter Package on Fedora 16
Can a man’s love for the command line blossom like a rose or age like good wine? I do believe the answer to my rhetorical question is a resounding YES! Recently I’ve found myself choosing gnome-terminal to execute things rather than clicking in a series of menus on my desktop. Don’t get me wrong; a GUI is nice thing to have, but the efficency of the CLI is unmatched. Through a series of unfortunate events I’ve setup my Linux environment for Android development (aka how trying to fix a bricked phone). I’m working with a fresh install from Fedora 16 Live. What that means is A LOT of packages/libraries are not installed. Just the bare minimum to get me going.
Here’s a general overview of the process I took:
- Download and extracted the Android Software Development Kit.
- Installed the Eclipse IDE (roughly 68 packages).
- Installed ADT plugins for Eclipse.
- Ran ./android command from SDK “tools” directory.
- It started the “Android SDK Manager”. I then installed:
- Android SDK Platform-tools
- The covented “Android 4.0″ platform
- 3.2, 2.3.3, and 2.2 platforms (just to show that I can be verstile)
WGET the Android SDK
I’m really enjoy the simplicity of the WGET command. While viewing the SDK page in Firefox I simply copied the link for the SDK file and pasted it into the terminal:
$ wget http://dl.google.com/android/android-sdk_r15-linux.tgz
I then used YUM to grab the Eclipse IDE and all its relevant components. Again; since this OS installation was pretty light I ended up installing 68 packages, such as: Eclipse, Java, etc.
# yum install eclipse
Once that was done I then installed the ADT plugin.
- I opened the Eclipse IDE.
- Clicked on Help > Install Software.
- Added the following repository: https://dl-ssl.google.com/android/eclipse/
- Clicked “Select All” and went to town! It was odd, but I noticed I had to try a couple times. It was claiming to have dependency issues. So; I started clicking one-by-one. Eventually I was able to get all 4 packages installed.
This following set is unnecessary since you can access the Android SDK Manager from within Eclipse (thanks to the ADT plugin). Originally; skipped the ADT plugin step.
Now that Java is installed I can run the “android” command. It’s located in the “tools” directory of your freshly extracted tarball file “android-sdk_r15-linux.tgz”.
The Android SDK Manager popped up with some packages to install. I chose what I thought were appropriate and wrote this blog post while I waited for the files to be downloaded and installed.
So; that’s pretty much it. At this point you’re ready to jump into the wonderment, which is Android development. Enjoy!