34,333
edits
Changes
→Windows 7
'adb' is not recognized as an internal or external command,
operable program or batch file.
</pre>
=== Windows 8 ===
1. On the start screen, move the mouse to the bottom right hand corner of the screen and select Search from the resulting menu. In the search box, enter Control Panel. When the Control Panel icon appears in the results area, click on it to launch the tool on the desktop.
2. Within the Control Panel, use the Category menu to change the display to Large Icons. From the list of icons select, the one labeled System.
3. Follow the steps outlined for Windows 7 starting from step 2.
== Adding the ADT Plugin to an Existing Eclipse Integration ==
The steps outlined so far in this chapter have assumed that the Eclipse IDE is not already installed on your system. In the event that you are already using Eclipse for Java based development, the appropriate Android development tools and SDKs can be added to this existing Eclipse installation. Eclipse editions with which the ADT Plugin is compatible are as follows:
* Eclipse IDE for Java Developers
* Eclipse Classic (versions 3.5.1 and higher)
* Eclipse IDE for Java EE Developers
* Eclipse for Mobile Developers
The ADT Plugin for Eclipse adds a range of Android specific features to what is otherwise a general-purpose Java edition of the Eclipse environment. To install this plugin, launch Eclipse and select the Help –> Install New Software… menu option. In the resulting window, click on the Add… button to display the Add Repository dialog. Enter “ADT Plugin” into the Name field and the following URL into the Location field:
[https://dl-ssl.google.com/android/eclipse/ https://dl-ssl.google.com/android/eclipse/]
Click on the OK button and wait while Eclipse connects to the Android repository. Once the information has been downloaded, new items will be listed entitled Developer Tools and NDK Plugins as illustrated in Figure 3-4:
[[Image:kindle_fire_adt_eclipse_plugin.png|Installing the Android Eclipse Plugin]]
Figure 3-4
Select the checkbox next to the Developer Tools entry and click on the Next > button. After requirements and dependencies have been calculated by the installer, a more detailed list of the packages to be installed will appear. Once again click on the Next > button to proceed. On the subsequent licensing page, select the option to accept the terms of the agreements (assuming that you do, indeed, agree) and click on Finish to complete the installation. During the download and installation process, you may be prompted to confirm that you wish to install unsigned content. In the event that this happens, simply click on the option to proceed with the installation.
When the ADT Plugin installation is complete, a dialog will appear providing the option to restart Eclipse in order to complete the installation. Click on Yes and wait for the tool to exit and re-launch.
Upon restarting, the Welcome to Android Development dialog will appear as illustrated in Figure 3-5:
[[Image:kindle_fire_android_adt_welcome.png|The Android ADT welcome screen]]
Figure 3-5
At this stage there is no existing SDK installed so the Use Existing SDKs choice is not a viable option. Unfortunately, the ADT Plugin does not provide the option at this point to install the SDKs of our choice so we will need to install the latest available SDK versions and then manually install the ones we actually need for Kindle Fire development. With this in mind, select the option to install the latest available version of the Android APIs. Make a note of the Target Location path and change it if you prefer the SDKs to be installed in a different location, then click Next. Choose whether to send usage information to Google, accept all the licensing terms and click on Install. The Android SDK Manager will now download and install the latest Android SDKs. Once this process is complete, follow the steps outlined in the earlier section entitled Installing the Correct Android and Kindle SDK Packages to install the appropriate Android and Amazon packages for Kindle development.
At this point, the Eclipse environment is ready to begin the development of Android applications for the Kindle Fire family of devices.
=== Mac OS X ===
A number of techniques may be employed to modify the $PATH environment variable on Mac OS X. Arguably the cleanest method is to add a new file in the /etc/paths.d directory containing the paths to be added to $PATH. Assuming an installation location of /Users/demo/adt-bundle-mac-x86_64, the path may be configured by creating a new file named android-sdk in the /etc/paths.d directory containing the following lines:
<pre>
/Users/demo/adt-bundle-mac-x86_64/sdk/tools
/Users/demo/adt-bundle-mac-x86_64/sdk/platform-tools
</pre>
Note that since this is a system directory it will be necessary to use the sudo command when creating the file. For example:
<pre>
sudo vi /etc/paths.d/android-sdk
</pre>
=== Windows 8 ===
