diff --git a/docs/html/images/sdk_manager_packages.png b/docs/html/images/sdk_manager_packages.png index 463be8f387496..027cce76c6feb 100755 Binary files a/docs/html/images/sdk_manager_packages.png and b/docs/html/images/sdk_manager_packages.png differ diff --git a/docs/html/sdk/adding-components.jd b/docs/html/sdk/adding-components.jd index 1f9cb31af13ca..d2e55d8e536a0 100644 --- a/docs/html/sdk/adding-components.jd +++ b/docs/html/sdk/adding-components.jd @@ -98,20 +98,20 @@ complete.
This will reveal all of the components that are currently available for download from the SDK repository.New platforms are automatically saved into the
-<sdk>/platforms/ directory of your SDK;
-new add-ons are saved in the <sdk>/add-ons/
+<sdk>/platforms/ directory of your SDK;
+new add-ons are saved in the <sdk>/add-ons/
directory; samples are saved in the
-<sdk>/samples/android-<level>/;
+<sdk>/samples/android-<level>/;
and new documentation is saved in the existing
-<sdk>/docs/ directory (old docs are replaced).
<sdk>/docs/ directory (old docs are replaced).
By default, Available Packages only shows the default -repository site, which offers platforms, SDK tools, documentation, the -Google APIs Add-on, and other components. You can add other sites that host +
By default, Available Packages displays components available from the +Android Repository and Third party Add-ons. You can add other sites that host their own Android SDK add-ons, then download the SDK add-ons from those sites.
For example, a mobile carrier or device manufacturer might offer additional API libraries that are supported by their own Android-powered devices. In order -to develop using their libraries, you must install their Android SDK add-on.
+to develop using their libraries, you must install their Android SDK add-on, if it's not already +available under Third party Add-ons.If a carrier or device manufacturer has hosted an SDK add-on repository file on their web site, follow these steps to add their site to the SDK and AVD @@ -183,11 +183,12 @@ Manager:
Any SDK components available from the site will now be listed under -Available Packages.
+Any SDK components available from the site will now be listed under a new item named +User Add-ons.
+android-sdk-<machine-platform>.
-Make a note of the name and -location of the unpacked SDK directory on your system—you will need to +
If you downloaded the Windows installer ({@code .exe} file), run it now and it will check +whether the proper Java SE Development Kit (JDK) is installed (installing it, if necessary), then +install the SDK Tools into a default location (which you can modify).
+ +Make a note of the name and location of the SDK directory on your system—you will need to refer to the SDK directory later, when setting up the ADT plugin and when using the SDK tools from command line.
-Optionally, you might want to add the location of the SDK's
-tools/ directory and {@code platform-tools/} directory to your system
-PATH. Both tool directories are located at the root of the SDK folder.
-
-
-
- How to update your PATH
- Adding
-tools/ and {@code platform-tools/} to your path lets you run Android Debug Bridge (adb)
-and the other command line tools without needing to
-supply the full path to the tool directories.
~/.bash_profile or ~/.bashrc file. Look
- for a line that sets the PATH environment variable and add the
- full path to the tools/ and {@code platform-tools/} directories to it. If you don't
- see a line setting the path, you can add one:
-
- export PATH=${PATH}:<your_sdk_dir>/tools:<your_sdk_dir>/platform-tools
- .bash_profile and
- proceed as for Linux. You can create the .bash_profile if
- you haven't already set one up on your machine. tools/ and {@code platform-tools/} directories to the path. If you used the Windows installer, when you complete the installation wizard, it will launch the +Android SDK and AVD Manager with a default set of platforms and other components selected +for you to install. Simply click Install to accept the recommended set of +components and install them. You can then skip to Step 5, but we +recommend you first read the section about the Available Components to +better understand the components available from the Android SDK and AVD Manager.
+You can launch the Android SDK and AVD Manager in one of the following ways:
SDK Manager.ext file at the root of the Android
SDK directory.tools/ directory in the
-Android SDK, then execute: android update sdk
This will automatically select -the required and recommended components for you to install.
android
To download components, use the graphical UI of the Android SDK and AVD Manager, shown in Figure 1, to browse the SDK repository and select new or updated components. The Android SDK and AVD Manager will install the selected components in your SDK environment. For information about which components you should download, see the following -section about Recommended Components
+section about Recommended Components.
Figure 1. The Android SDK and AVD Manager's Available Packages panel, which shows the SDK components that are available for you to download into your environment.
-The SDK repository offers these types of components:
+ +By default, there are two repositories of components for your SDK: Android +Repository and Third party Add-ons.
+ +The Android Repository offers these types of components:
com.google.android.maps library. You can also add additional
-repositories, so that you can download other SDK add-ons, where available. The Third party Add-ons provide components that allow you to create a development +environment using a specific Android external library (such as the Google Maps library) or a +customized (but fully compliant) Android system image. You can add additional Add-on repositories, +by clicking Add Add-on Site.
+Optionally, you might want to add the location of the SDK's tools/ and
+platform-tools to your PATH environment variable, to provide easy
+access to the tools.
+ How to update your PATH
+ Adding both tools/ and platform-tools/ to your PATH lets you run
+command line tools without needing to
+supply the full path to the tool directories. Depending on your operating system, you can
+include these directories in your PATH in the following way:
tools/ and platform-tools/ directories to the path. ~/.bash_profile or ~/.bashrc file. Look
+ for a line that sets the PATH environment variable and add the
+ full path to the tools/ and platform-tools directories to it. If you
+ don't see a line setting the path, you can add one:
+ export PATH=${PATH}:<sdk>/tools:<sdk>/platform-tools
+ .bash_profile and
+ proceed as for Linux. You can create the .bash_profile if
+ you don't already have one. Once you have completed installation, you are ready to begin developing applications. Here are a few ways you can get started: