diff --git a/docs/html/guide/developing/tools/othertools.jd b/docs/html/guide/developing/tools/othertools.jd index 603609eb1ae03..b4c4cf32dd08a 100644 --- a/docs/html/guide/developing/tools/othertools.jd +++ b/docs/html/guide/developing/tools/othertools.jd @@ -1,9 +1,11 @@ page.title=Other Tools @jd:body -

The sections below describe other tools that you can use when building Android applications.

+

The sections below describe other tools that you can use when building +Android applications.

-

All of the tools are included in the Android SDK and are accessible from the <sdk>/tools/ directory.

+

All of the tools are included in the Android SDK and are accessible from the +<sdk>/tools/ directory.

Contents

@@ -16,24 +18,32 @@ page.title=Other Tools

android

-

The android tool is a script that lets you create and manage Android Virtual Devices (AVDs) and, if you are developing using Ant, generate template Android projects to help you get started quickly.

+

{@code android} is an important development tool that lets you:

-

For information about how to use the android tool to manage AVDs, see Android Virtual Devices.

+ -

For information about how to use the android tool to create or update a project, see Developing in Other IDEs.

- -

Note that if you are developing in Eclipse with the ADT plugin, you will use the android tool to manage the AVDs you create, but you will not use the android tool for creating a project. The ADT plugin provides a New Project Wizard that helps you set up an Android project in Eclipse.

- -

If you are developing in Ant, you will use the android tool to manage your AVDs, and you can also use it to create or update a project.

- -

Note: The android tool replaces the activitycreator tool provided in previous SDK releases.

+

If you develop in Eclipse with the ADT plugin, you can perform +these tasks directly from the IDE. To create +Android projects and AVDs from Eclipse, see Developing +In Eclipse. To update your SDK from Eclipse, see +Updating Your SDK. +

mksdcard

-

The mksdcard tool lets you quickly create a FAT32 disk image that you can load in the emulator, to simulate the presence of an SD card in the device. Here is the usage for mksdcard:

+

The mksdcard tool lets you quickly create a FAT32 disk image that you can +load in the emulator, to simulate the presence of an SD card in the device. +Here is the usage for mksdcard:

mksdcard [-l label] <size>[K|M] <file>
@@ -53,7 +63,8 @@ page.title=Other Tools size An integer that specifies the size (in bytes) of disk image to create. -You can also specify size in kilobytes or megabytes, by appending a "K" or "M" to <size>. For example, 1048576K, 1024M. +You can also specify size in kilobytes or megabytes, by appending a "K" or "M" to +<size>. For example, 1048576K, 1024M. @@ -63,7 +74,9 @@ You can also specify size in kilobytes or megabytes, by appending a "K" or "M" t -

Once you have created the disk image file, you can load it in the emulator at startup using the emulator's -sdcard option. For more information, see Android Emulator.

+

Once you have created the disk image file, you can load it in the emulator at +startup using the emulator's -sdcard option. For more information, see +Android Emulator.

emulator -sdcard <file>
@@ -71,7 +84,11 @@ You can also specify size in kilobytes or megabytes, by appending a "K" or "M" t

dx

-

The dx tool lets you generate Android bytecode from .class files. The tool converts target files and/or directories to Dalvik executable format (.dex) files, so that they can run in the Android environment. It can also dump the class files in a human-readable format and run a target unit test. You can get the usage and options for this tool by using dx --help.

+

The dx tool lets you generate Android bytecode from .class files. The tool +converts target files and/or directories to Dalvik executable format (.dex) files, +so that they can run in the Android environment. It can also dump the class files +in a human-readable format and run a target unit test. You can get the usage and +options for this tool by using dx --help.

diff --git a/docs/html/guide/developing/updating-sdk.jd b/docs/html/guide/developing/updating-sdk.jd new file mode 100644 index 0000000000000..f65eabba050da --- /dev/null +++ b/docs/html/guide/developing/updating-sdk.jd @@ -0,0 +1,108 @@ +page.title=Updating Your SDK +@jd:body + + +
+
+

Quickview

+ + +

In this document

+
    +
  1. Installing SDK Packages
  2. +
  3. Adding SDK Package Sites
  4. +
+
+
+ +

The Android SDK and AVD Manager lets you +update your Android SDK without a visit to the +Android Developers web site. Instead of downloading an entirely new SDK +that includes Android platforms, tools, and documentation, you can instead +install only the individual packages that you want.

+ +

For example, when a new version of the Android platform is made available +for developing applications, use the SDK and AVD Manager to install the +platform into your existing SDK directory. You can then use the new platform +in your AVDs and +build your apps against it.

+ +

The benefit to using this feature is that your SDK directory will +remain the same. You don't need to reset the SDK location in +your Eclipse preferences or modify your {@code PATH} environment variable, +because all new packages are installed into your existing SDK directory.

+ + +

The SDK and AVD Manager can be opened in two ways:

+ + +

The screenshot below shows the Android SDK and AVD Manager +with the Available Packages open.

+ + + + +

Installing SDK Packages

+ +

When a new Android SDK platform, add-on, set of development tools or +documentation becomes available, you can quickly download and +install them into your existing Android SDK:

+ +
    +
  1. Select Available Packages in the left panel. + This will reveal all packages currently available for download.
  2. +
  3. Select the packages you'd like to install and click Install + Selected.
  4. +
  5. Verify and accept the packages you want and click Install + Accepted. The packages will now be installed into your existing + Android SDK directories.
  6. +
+ +

New platforms are automatically saved into the +<sdk_dir>/platforms/ directory of your SDK; +new add-ons are saved in the <sdk_dir>/add-ons/ +directory; and new documentation is saved in the existing +<sdk_dir>/docs/ directory (old docs are replaced).

+ +

Tip: +Use the "Display updates only" checkbox to show only the packages +you do not have.

+ + +

Adding SDK Package Sites

+ +

By default, Available Packages only shows +the Google repository for Android SDK packages and Google API +add-ons. You can add additional sites that host +Android SDK add-ons, then download add-on packages from them.

+ +

For example, a mobile carrier or hardware manufacturer may offer additional +API libraries that are supported by their own Android-powered devices. +In order for you to develop using their libraries, you may need to install an +Android SDK add-on. +If the carrier or manufacturer has hosted an add-on repository file on their +web site, add their site to the SDK and AVD Manager:

+
    +
  1. Select Available Packages in the left panel.
  2. +
  3. Click Add Site and enter the URL of the +{@code repository.xml} file. Click OK.
  4. +
+

Any SDK packages available from the web site will now be listed and +available for you to install in your existing Android SDK.

+ + diff --git a/docs/html/guide/guide_toc.cs b/docs/html/guide/guide_toc.cs index 264fe549335c7..f6718e1169e5f 100644 --- a/docs/html/guide/guide_toc.cs +++ b/docs/html/guide/guide_toc.cs @@ -239,6 +239,7 @@
  • Debugging Tasks
  • +
  • Updating Your SDK
  • Tools diff --git a/docs/html/images/sdk_manager_packages.png b/docs/html/images/sdk_manager_packages.png new file mode 100755 index 0000000000000..463be8f387496 Binary files /dev/null and b/docs/html/images/sdk_manager_packages.png differ