diff --git a/Android.mk b/Android.mk index 2e2fec18ac165..49ee63db0bb0e 100644 --- a/Android.mk +++ b/Android.mk @@ -372,7 +372,7 @@ web_docs_sample_code_flags := \ ## SDK version identifiers used in the published docs # major[.minor] version for current SDK. (full releases only) -framework_docs_SDK_VERSION:=1.6 +framework_docs_SDK_VERSION:=2.0 # release version (ie "Release x") (full releases only) framework_docs_SDK_REL_ID:=1 # name of current SDK directory (full releases only) diff --git a/docs/html/guide/developing/updating-sdk.jd b/docs/html/guide/developing/updating-sdk.jd deleted file mode 100644 index f65eabba050da..0000000000000 --- a/docs/html/guide/developing/updating-sdk.jd +++ /dev/null @@ -1,108 +0,0 @@ -page.title=Updating Your SDK -@jd:body - - -
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.
- -
-
-
-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:
- -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.
- - -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:
-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 f6718e1169e5f..264fe549335c7 100644 --- a/docs/html/guide/guide_toc.cs +++ b/docs/html/guide/guide_toc.cs @@ -239,7 +239,6 @@This page describes how to install the Android SDK and set up your +development environment for the first time.
+ +If you encounter any problems during installation, see the +Installation Notes at the bottom of +this page.
+ +If you have already installed an earlier version +of the Android SDK, please instead read Updating Your SDK. +
+ + +Before you begin, take a moment to confirm that your development machine +meets the System Requirements.
+ +If you will be developing in Eclipse with the Android Development +Tools (ADT) Plugin — the recommended path if you are new to +Android — make sure that you have a suitable version of Eclipse +installed on your computer (3.4 or newer is recommended). If you need +to install Eclipse, you can download it from this location:
+ +http://www.eclipse.org/downloads/
+ +A Java or RCP version of Eclipse is recommended.
+ +After downloading the Android SDK, unpack the Android SDK .zip archive
+to a suitable location on your machine. By default, the SDK files are unpacked
+into a directory named android_sdk_<platform>_<release>.
Make a note of the name and location of the unpacked SDK directory on your system — you +will need to refer to the SDK directory later, when setting up the Android plugin or when +using the SDK tools.
+ +Optionally, you may want to add the location of the SDK's primary tools directory
+to your system PATH. The primary tools/ directory is located at the root of the
+SDK folder. Adding 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 tools directory.
~/.bash_profile or ~/.bashrc file. Look
+ for a line that sets the PATH environment variable and add the
+ full path to the tools/ directory to it. If you don't
+ see a line setting the path, you can add one:export PATH=${PATH}:<your_sdk_dir>/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/ directory to the path. Note that, if you update your SDK in the future, you
+should remember to update your PATH settings to point to the new location, if different.
If you will be using the Eclipse IDE as your development environment, +the next section describes how to install the Android Development Tools (ADT) plugin and set up Eclipse. +If you choose not to use Eclipse, you can +develop Android applications in an IDE of your choice and then compile, debug and deploy using +the tools included in the SDK (skip to Next Steps).
+ + +Android offers a custom plugin for the Eclipse IDE, called Android +Development Tools (ADT), that is designed to give you a powerful, +integrated environment in which to build Android applications. It +extends the capabilites of Eclipse to let you quickly set up new Android +projects, create an application UI, add components based on the Android +Framework API, debug your applications using the Android SDK tools, and even export +signed (or unsigned) APKs in order to distribute your application.
+ +In general, using Eclipse with ADT is a highly recommended approach to +Android development and is the fastest way to get started. (If you prefer to +work in an IDE other than Eclipse, you do not need to install Eclipse or ADT, +instead, you can directly use the SDK tools to build and debug your +application—skip to Next Steps.)
+ +Once you have the Eclipse IDE installed, as described in Preparing for Installation, follow the steps below to +download the ADT plugin and install it in your respective Eclipse environment. +
+ +| Eclipse 3.4 (Ganymede) | Eclipse 3.5 (Galileo) |
|---|---|
+
+
|
+
+
+
|
+
Now modify your Eclipse preferences to point to the Android SDK directory:
+Done! If you haven't encountered any problems, then you're ready to +begin developing Android applications. See the +Next Steps section for suggestions on how to start.
+ + +Once you've downloaded and unpacked the SDK, open the SDK directory +and take a look at what's inside.
+ +The table below describes the SDK directory contents.
+ +| Name | Description | +||
|---|---|---|---|
add-ons/ |
+Contains add-ons to the Android SDK development +environment, which let you develop against external libraries that are available on some +devices. | +||
docs/ |
+A full set of documentation in HTML format, including the Developer's Guide, +API Reference, and other information. | +||
platforms/ |
+Contains a set of Android platform versions that you can develop +applications against, each in a separate directory. | +||
| + | <platform>/ |
+Platform version directory, for example "Android 1.6". All platform version +directories contain a similar set of files and subdirectory structure. | +|
| + | + | data/ |
+Storage area for default fonts and resource definitions. | +
| + | + | images/ |
+Storage area for default disk images, including the Android system image, +the default userdata image, the default ramdisk image, and more. The images +are used in emulator sessions. | +
| + | + | samples/ |
+Contains a wide variety of sample applications that you can load as projects +into your development environment, compile, and run on the emulator. | +
| + | + | skins/ |
+A set of emulator skins available for the platform version. Each skin is +designed for a specific screen resolution. | +
| + | + | templates/ |
+Storage area for file templates used by the SDK development tools. | +
| + | + | tools/ |
+Any development tools that are specific to the platform version. | +
| + | + | android.jar |
+The Android library used when compiling applications against this platform +version. | +
tools/ |
+Contains the set of development and profiling tools available to you, such
+as the emulator, the android tool, adb, ddms, and more. |
+||
RELEASE_NOTES.html |
+A file that loads the local version of the SDK release notes, if +available. | +||
documentation.html |
+A file that loads the entry page for the local Android SDK +documentation. | +||
ia32-libs package using
+ apt-get::
+ apt-get install ia32-libs+
apt-get install sun-java6-bin
If you are having trouble downloading the ADT plugin after following the +steps above, here are some suggestions:
+ +http://dl-ssl.google.com/android/eclipse/
If you are still unable to use Eclipse to download the ADT plugin as a +remote update site, you can download the ADT zip file to your local machine and +manually install it:
+ +To update your plugin once you've installed using the zip file, you will have +to follow these steps again instead of the default update instructions.
+ +Note that there are features of ADT that require some optional +Eclipse components (for example, WST). If you encounter an error when +installing ADT, your Eclipse installion might not include these components. +For information about how to quickly add the necessary components to your +Eclipse installation, see the troubleshooting topic +ADT +Installation Error: "requires plug-in org.eclipse.wst.sse.ui".
+ +If you encounter this error when installing the ADT Plugin for Eclipse: +
+An error occurred during provisioning. +Cannot connect to keystore. +JKS+
+...then your development machine lacks a suitable Java VM. Installing Sun +Java 6 will resolve this issue and you can then reinstall the ADT +Plugin.
+ + diff --git a/docs/html/sdk/download.jd b/docs/html/sdk/download.jd index 1712ae6212870..76f1213691330 100644 --- a/docs/html/sdk/download.jd +++ b/docs/html/sdk/download.jd @@ -57,15 +57,11 @@ The License Agreement constitutes a contract between you and Google with respect