For more information on this SDK release, read the -Release Notes.
- -The SDK includes a variety of tools for developing and debugging application code and designing
-an application UI. You can read about the tools in the documentation included with the SDK.
-You can access the tools in the <sdk>/tools/ directory.
The Android system images listed below are included in this SDK.
- -| Notes | Description | -||
|---|---|---|---|
| 1 | -Includes the {@code com.google.android.maps} external library and a set of standard development -applications. | - -
You can look at a variety of tutorials and samples in the
-documentation included with the SDK and access the sample code itself
-in the <sdk>/samples/ directory of the SDK package.
The SDK package provides a full set of local documentation, including installation and upgrade
-instructions. To view it, open the <sdk>/documentation.html file in a web browser.
-If you are developing in an IDE such as Eclipse, you can also view the reference documentation
-directly in the IDE.
For the current SDK release, see the links under Current SDK Release in the side navigation.
+ -This page describes how to install the Android 1.0 SDK, Release 1, and set up your development environment. -If you haven't downloaded the SDK yet, you can so from the Download page.
- -Before you begin, be sure that your development environment meets the SDK -System Requirements. If you encounter any problems during installation, -see the Installation Notes at the bottom of this page.
- -If you have already developed applications using an earlier version of the -SDK, please skip this page and read the -Upgrading the SDK document instead. -
- - - -After downloading the SDK, unpack the .zip archive to a suitable location on your machine. By default, the SDK files are unpacked into a directory named android_sdk_<platform>_<release>_<build>. The directory contains a link to a local copy of the documentation and the subdirectories tools/, samples/, and others.
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 using SDK tools.
- -Optionally, you can add the path to the SDK tools directory to your path. As mentioned above, the tools/ directory is located in the SDK directory.
tools/ directory to it. If you don't
- see a line setting the path, you can add one:export PATH=${PATH}:<your_sdk_dir>/toolstools/ directory to the path. 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. Note that, if you update your SDK, 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 environment for developing Android applications, continue reading the next -section in order to install the Android Development Tools plugin and setup Eclipse. If you choose not to use Eclipse, you can -develop Android applications using other tools — read the guide to developing -In other IDEs.
- - -First, you should install a custom plugin called Android Development Tools (ADT), which adds integrated support for Android projects and tools. The ADT plugin includes a variety of powerful extensions that make creating, running, and debugging Android applications faster and easier. Developing in ADT/Eclipse is highly recommended for Eclipse users and those new to Android.
- -To download and install the ADT plugin, follow the steps below for your respective Eclipse version.
- -| Eclipse 3.3 (Europa) | Eclipse 3.4 (Ganymede) |
|---|---|
-
|
-
-
-
|
-
Now, you just need to 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. -We recommend you begin with the Hello World tutorial, -which will teach you some basics about Android applications and how to create projects using Eclipse.
- - --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 files to your local machine using a browser and the install the files in Eclipse from there: -
--Note that to update your plugin, you will have to follow these steps again instead of the default update instructions.
- -Note that the "Android Editors" feature of ADT requires several optional -Eclipse components (for example, WST). If you encounter an error when -installing ADT, your Eclipse installion might not include those 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.
- - -ia32-libs package using
-apt-get::
- apt-get install ia32-libs
apt-get install sun-java6-bin
You should have already been redirected by your browser. Please go to +Installing the Android SDK.
\ No newline at end of file diff --git a/docs/html/sdk/1.0_r1/requirements.jd b/docs/html/sdk/1.0_r1/requirements.jd index 4163513174c23..96fdcb26f6fac 100644 --- a/docs/html/sdk/1.0_r1/requirements.jd +++ b/docs/html/sdk/1.0_r1/requirements.jd @@ -1,51 +1,8 @@ -page.title=System Requirements -sdk.version=1.0_r1 - - @jd:body -The sections below describe the system and software requirements for -developing Android applications using the Android SDK tools included in Android 1.0 SDK, Release 1.
+ -The following systems and development environments are supported by this SDK.
- -Note: If JDK is already installed on your development computer, please take a moment to make sure that it meets the version requirements listed above. In -particular, note that some Linux distributions may include JDK 1.4 or Gnu Compiler for Java, both of which are not supported for Android development.
\ No newline at end of file +You should have already been redirected by your browser. Please go to +System Requirements.
\ No newline at end of file diff --git a/docs/html/sdk/1.0_r2/index.jd b/docs/html/sdk/1.0_r2/index.jd index a1989ba93939e..c29c148a48618 100644 --- a/docs/html/sdk/1.0_r2/index.jd +++ b/docs/html/sdk/1.0_r2/index.jd @@ -1,68 +1,5 @@ page.title=Android 1.0 SDK, release 2 - -sdk.not_latest_version=true - -sdk.version=1.0_r2 -sdk.date=November 2008 - -sdk.win_download=android-sdk-windows-1.0_r2.zip -sdk.win_bytes=98360564 -sdk.win_checksum=a5e1af8ac145946b4a9627516ad4a711 - -sdk.mac_download=android-sdk-mac_x86-1.0_r2.zip -sdk.mac_bytes=93771410 -sdk.mac_checksum=87b99d5e9f59b78363a63200c11498e8 - -sdk.linux_download=android-sdk-linux_x86-1.0_r2.zip -sdk.linux_bytes=94186463 -sdk.linux_checksum=a1f3b6d854596f850f5008856d0f380e - +sdk.redirect=true +sdk.redirect.path=index.html @jd:body - -For more information on this SDK release, read the -Release Notes.
- -The SDK includes a variety of tools for developing and debugging application code and designing
-an application UI. You can read about the tools in the documentation included with the SDK.
-You can access the tools in the <sdk>/tools/ directory.
The Android system images listed below are included in this SDK.
- -| Notes | Description | -||
|---|---|---|---|
| 1 | -Includes the {@code com.google.android.maps} external library and a set of standard development -applications. | - -
You can look at a variety of tutorials and samples in the
-documentation included with the SDK and access the sample code itself
-in the <sdk>/samples/ directory of the SDK package.
The SDK package provides a full set of local documentation, including installation and upgrade
-instructions. To view it, open the <sdk>/documentation.html file in a web browser.
-If you are developing in an IDE such as Eclipse, you can also view the reference documentation
-directly in the IDE.
For the current SDK release, see the links under Current SDK Release in the side navigation.
+ -This page describes how to install the Android 1.0 SDK, Release 2, and set up your development environment. -If you haven't downloaded the SDK yet, you can so from the Download page.
- -Before you begin, be sure that your development environment meets the SDK -System Requirements. If you encounter any problems during installation, -see the Installation Notes at the bottom of this page.
- -If you have already developed applications using an earlier version of the -SDK, please skip this page and read the -Upgrading the SDK document instead. -
- - - -After downloading the SDK, unpack the .zip archive to a suitable location on your machine. By default, the SDK files are unpacked into a directory named android_sdk_<platform>_<release>_<build>. The directory contains a link to a local copy of the documentation and the subdirectories tools/, samples/, and others.
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 using SDK tools.
- -Optionally, you can add the path to the SDK tools directory to your path. As mentioned above, the tools/ directory is located in the SDK directory.
tools/ directory to it. If you don't
- see a line setting the path, you can add one:export PATH=${PATH}:<your_sdk_dir>/toolstools/ directory to the path. 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. Note that, if you update your SDK, 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 environment for developing Android applications, continue reading the next -section in order to install the Android Development Tools plugin and setup Eclipse. If you choose not to use Eclipse, you can -develop Android applications using other tools — read the guide to developing -In other IDEs.
- - -First, you should install a custom plugin called Android Development Tools (ADT), which adds integrated support for Android projects and tools. The ADT plugin includes a variety of powerful extensions that make creating, running, and debugging Android applications faster and easier. Developing in ADT/Eclipse is highly recommended for Eclipse users and those new to Android.
- -To download and install the ADT plugin, follow the steps below for your respective Eclipse version.
- -| Eclipse 3.3 (Europa) | Eclipse 3.4 (Ganymede) |
|---|---|
-
|
-
-
-
|
-
Now, you just need to 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. -We recommend you begin with the Hello World tutorial, -which will teach you some basics about Android applications and how to create projects using Eclipse.
- - --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 files to your local machine using a browser and the install the files in Eclipse from there: -
--Note that to update your plugin, you will have to follow these steps again instead of the default update instructions.
- -Note that the "Android Editors" feature of ADT requires several optional -Eclipse components (for example, WST). If you encounter an error when -installing ADT, your Eclipse installion might not include those 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.
- - -ia32-libs package using
-apt-get::
- apt-get install ia32-libs
apt-get install sun-java6-bin
You should have already been redirected by your browser. Please go to +Installing the Android SDK.
\ No newline at end of file diff --git a/docs/html/sdk/1.0_r2/requirements.jd b/docs/html/sdk/1.0_r2/requirements.jd index 4f7c093cad5f3..96fdcb26f6fac 100644 --- a/docs/html/sdk/1.0_r2/requirements.jd +++ b/docs/html/sdk/1.0_r2/requirements.jd @@ -1,50 +1,8 @@ -page.title=System Requirements -sdk.version=1.0_r2 - - @jd:body -The sections below describe the system and software requirements for developing Android applications using the Android SDK tools included in Android 1.0 SDK, Release 2.
+ -The following systems and development environments are supported by this SDK.
- -Note: If JDK is already installed on your development computer, please take a moment to make sure that it meets the version requirements listed above. In -particular, note that some Linux distributions may include JDK 1.4 or Gnu Compiler for Java, both of which are not supported for Android development.
\ No newline at end of file +You should have already been redirected by your browser. Please go to +System Requirements.
\ No newline at end of file diff --git a/docs/html/sdk/1.1_r1/index.jd b/docs/html/sdk/1.1_r1/index.jd index f6582162fb919..63fe51d759a7f 100644 --- a/docs/html/sdk/1.1_r1/index.jd +++ b/docs/html/sdk/1.1_r1/index.jd @@ -1,66 +1,5 @@ page.title=Android 1.1 SDK, Release 1 - -sdk.not_latest_version=true -sdk.version=1.1_r1 -sdk.date=February 2009 - -sdk.win_download=android-sdk-windows-1.1_r1.zip -sdk.win_bytes=86038515 -sdk.win_checksum=8c4b9080b430025370689e03d20842f3 - -sdk.mac_download=android-sdk-mac_x86-1.1_r1.zip -sdk.mac_bytes=79046151 -sdk.mac_checksum=becf0f1763d61eedce15d2a903d6c1dd - -sdk.linux_download=android-sdk-linux_x86-1.1_r1.zip -sdk.linux_bytes=79345522 -sdk.linux_checksum=ebcb16b0cd4aef198b4dd9a1418efbf1 - +sdk.redirect=true +sdk.redirect.path=index.html @jd:body - -For more information on this SDK release, read the -Release Notes.
- -The SDK includes a variety of tools for developing and debugging application code and designing an application UI. You can read about the tools in the
-Dev Guide and access them in the <sdk>/tools/ directory.
-
-
The tools package included in this SDK is the same as that included in the Android 1.0, Release 2 SDK.
- -The Android system images listed below are included in this SDK. For more information about a system image — features, applications included, localizations, API changes, and so on — see its Version Notes.
- -| Notes | Description | -||
|---|---|---|---|
| 2 | -Includes com.google.android.maps external library and a set of standard development applications. | - -
You can look at a variety of tutorials and samples in the Dev Guide and access the sample code itself
-in the <sdk>/samples/ directory of the SDK package.
The SDK package includes a full set of local documentation. To view it, open the <sdk>/documentation.html file in a web browser. If you are developing in an IDE such as Eclipse, you can also view the reference documentation directly in the IDE.
The most current documentation is always available on the Android Developers site:
- - - - diff --git a/docs/html/sdk/1.1_r1/installing.jd b/docs/html/sdk/1.1_r1/installing.jd index 2da24799f95b8..2ea04e4687546 100644 --- a/docs/html/sdk/1.1_r1/installing.jd +++ b/docs/html/sdk/1.1_r1/installing.jd @@ -1,312 +1,8 @@ -page.title=Installing the Android SDK -sdk.version=1.1_r1 - @jd:body + -This page describes how to install the Android SDK and set up your -development environment. If you haven't downloaded the SDK, you can -do so from the -Download page.
- -If you encounter any problems during installation, see the -Installation Notes at the bottom of -this page.
- -If you have already developed applications using an earlier version -of the SDK, please skip this page and read the -Upgrading the -SDK document instead. -
- - -Before you get started with the Android SDK, take a moment to confirm -that your development machine meets the system requirements. -
- -If you will be developing on 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. 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 SDK, unpack the .zip archive to a suitable location on your machine. By default, the SDK files are unpacked into a directory named android_sdk_<platform>_<release>_<build>. The directory contains a link to a local copy of the documentation and the subdirectories tools/, samples/, and others.
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 using SDK tools.
- -Optionally, you can add the path to the SDK tools directory to your path. As mentioned above, the tools/ directory is located in the SDK directory.
tools/ directory to it. If you don't
- see a line setting the path, you can add one:export PATH=${PATH}:<your_sdk_dir>/toolstools/ directory to the path. 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. Note that, if you update your SDK, 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 environment for developing Android applications, continue reading the next -section in order to install the Android Development Tools plugin and set up Eclipse. If you choose not to use Eclipse, you can -develop Android applications using other tools — read the guide to developing -in other IDEs.
- - -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, and debug using the Android SDK tools.
- -If you are new to Android or want to develop using the Eclipse IDE, -the ADT plugin will be an essential part of your development -environment. In general, using Eclipse with ADT is a highly recommended -approach and is the fastest way to get started. This section describes -how to install ADT into your Eclipse environment. - -
If you prefer to work in a development environment other than Eclipse, -you do not need to install Eclipse or the ADT Plugin. Instead, you can -access the SDK tools directly to build and debug your application.
- -Once you have Eclipse 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.3 (Europa) | Eclipse 3.4 (Ganymede) |
|---|---|
-
|
-
-
-
|
-
Now, you just need to 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 After -Installation: Next Steps section for suggestions on how to start.
- - --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 files to your local machine using a browser and the install the files in Eclipse from there: -
--Note that to update your plugin, you will have to follow these steps again instead of the default update instructions.
- -Note that the "Android Editors" feature of ADT requires several optional -Eclipse components (for example, WST). If you encounter an error when -installing ADT, your Eclipse installion might not include those 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.
- - -Once you have installed the SDK and the ADT Plugin, you are ready to -begin developing applications. Here are a few ways you can get started:
- -Learn about Android
-Explore the SDK
-Explore some code
-<sdk>/samples, then compile and run it in
-your development environmentVisit the Android developer groups
-ia32-libs package using
-apt-get::
- apt-get install ia32-libs
apt-get install sun-java6-bin
You should have already been redirected by your browser. Please go to +Installing the Android SDK.
\ No newline at end of file diff --git a/docs/html/sdk/1.1_r1/requirements.jd b/docs/html/sdk/1.1_r1/requirements.jd index 9d8f9eb1e0967..96fdcb26f6fac 100644 --- a/docs/html/sdk/1.1_r1/requirements.jd +++ b/docs/html/sdk/1.1_r1/requirements.jd @@ -1,48 +1,8 @@ -page.title=System Requirements - -sdk.version=1.1_r1 -sdk.date=February 2009 - @jd:body -The sections below describe the system and software requirements for developing Android applications using the Android SDK tools included in Android 1.1 SDK, Release 1.
+ -Note: If JDK is already installed on your development computer, please take a moment to make sure that it meets the version requirements listed above. In -particular, note that some Linux distributions may include JDK 1.4 or Gnu Compiler for Java, both of which are not supported for Android development.
\ No newline at end of file +You should have already been redirected by your browser. Please go to +System Requirements.
\ No newline at end of file diff --git a/docs/html/sdk/1.5_r1/index.jd b/docs/html/sdk/1.5_r1/index.jd index 405f56ce960aa..60dfc142e4f63 100644 --- a/docs/html/sdk/1.5_r1/index.jd +++ b/docs/html/sdk/1.5_r1/index.jd @@ -1,89 +1,5 @@ -sdk.version=1.5 -sdk.rel.id=1 -sdk.date=April 2009 -sdk.not_latest_version=true - -sdk.win_download=android-sdk-windows-1.5_r1.zip -sdk.win_bytes=176263368 -sdk.win_checksum=42be980eb2d3efaced01ea6c32c0045f - -sdk.mac_download=android-sdk-mac_x86-1.5_r1.zip -sdk.mac_bytes=167848675 -sdk.mac_checksum=5b2a8d9f096032db4a75bfa0d689a51b - -sdk.linux_download=android-sdk-linux_x86-1.5_r1.zip -sdk.linux_bytes=162938845 -sdk.linux_checksum=2addfd315da0ad8b5bde6b09d5ff3b06 - page.title=Android 1.5 SDK, Release 1 +sdk.redirect=true +sdk.redirect.path=index.html + @jd:body - -For more information on this SDK release, read the -Release Notes.
- -The SDK includes a full set of tools for developing and debugging application code and designing an application UI. You can read about the tools in the
-Dev Guide and access them in the <sdk>/tools/ directory.
-
-
The tools package in this SDK includes updates from those provided in the previous SDK. The tools also require a different project structure. To use the new tools, you need to migrate your applications to the new development environment. For more information about how to migrate, see Upgrading the SDK. - -
For more information about the new tools features, see the SDK Release Notes. - -
This SDK includes multiple Android platform versions that you use to develop applications. For each version, both a fully compliant Android library and system image are provided. The table below lists the platform versions included in this SDK. For more information about a platform version — features, applications included, localizations, API changes, and so on — see its Version Notes.
- -| Notes | Description | -||
|---|---|---|---|
| 3 | -Includes a standard Android 1.5 library and system image with a set of development applications. Does not include any external libraries (such as the Maps external library). | -||
| 2 | -Includes a compliant Android 1.1 library and system image with a set of development applications. Also includes the Maps external library (due to legacy build system issues). | - -
An SDK add-on provides a development environment for an Android external library or a customized (but fully compliant) Android system image. This SDK includes the SDK add-on listed below. The Android system API Level required by the add-on is noted.
- -| Notes | Description | -||
|---|---|---|---|
| 3 | -- | Includes the com.google.android.maps external library, a compliant -system image, a {@link android.location.Geocoder Geocoder} -backend service implementation, documentation, and sample code. | -
You can look at a variety of tutorials and samples in the Dev Guide and access the sample code itself
-in the <sdk>/platforms/android-1.5/samples/ directory of the SDK package. Note the new location — the SDK now includes multiple platform versions that you can develop against and each has its own sample code directory.
The SDK package includes a full set of local documentation. To view it, open the <sdk>/documentation.html file in a web browser. If you are developing in an IDE such as Eclipse, you can also view the reference documentation directly in the IDE.
The most current documentation is always available on the Android Developers site:
- - - diff --git a/docs/html/sdk/1.5_r1/installing.jd b/docs/html/sdk/1.5_r1/installing.jd index ac6af616d9e80..2ea04e4687546 100644 --- a/docs/html/sdk/1.5_r1/installing.jd +++ b/docs/html/sdk/1.5_r1/installing.jd @@ -1,332 +1,8 @@ -sdk.version=1.5 -sdk.rel.id=1 -sdk.date=April 2009 - -page.title=Installing the Android SDK @jd:body + -This page describes how to install the Android SDK and set up your -development environment. If you haven't downloaded the SDK, you can -do so from the -Download page. Once you've downloaded -the SDK, return here.
- -If you encounter any problems during installation, see the -Installation Notes at the bottom of -this page.
- -If you have already developed applications using an earlier version -of the SDK, please read -Upgrading the -SDK, instead. -
- - -Before you begin, take a moment to confirm that your development machine meets the -System Requirements. -
- -If you will be developing on 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.3 or newer). 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 SDK, unpack the .zip archive to a suitable location on your machine.
-By default, the SDK files are unpacked into a directory named
-android_sdk_<platform>_<release>.
-The directory contains a local copy of the documentation (accessible by opening
-documentation.html in your browser) and the subdirectories
-tools/, add-ons/, platforms/, and others. Inside
-each subdirectory of platforms/ you'll find samples/, which includes
-code samples that are specific to each version of the platform.
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 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.)
- -Once you have Eclipse 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.3 (Europa) | Eclipse 3.4 (Ganymede) |
|---|---|
-
-
|
-
-
-
-
|
-
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.
- - --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 the 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.
- - -Once you have completed installation, you are ready to -begin developing applications. Here are a few ways you can get started:
- -Learn about Android
-Explore the SDK
-Explore some code
-<sdk>/platforms/<platfrom>/samples,
- then compile and run it in your development environmentVisit the Android developer groups
-ia32-libs package using
- apt-get::
- apt-get install ia32-libs-
apt-get install sun-java6-bin
You should have already been redirected by your browser. Please go to +Installing the Android SDK.
\ No newline at end of file diff --git a/docs/html/sdk/1.5_r1/requirements.jd b/docs/html/sdk/1.5_r1/requirements.jd index c10ccac561ea1..96fdcb26f6fac 100644 --- a/docs/html/sdk/1.5_r1/requirements.jd +++ b/docs/html/sdk/1.5_r1/requirements.jd @@ -1,45 +1,8 @@ -page.title=System Requirements @jd:body -The sections below describe the system and software requirements for developing Android applications using the Android SDK tools included in Android SDK, Release .
+ -Note: If JDK is already installed on your development computer, please take a moment to make sure that it meets the version requirements listed above. In -particular, note that some Linux distributions may include JDK 1.4 or Gnu Compiler for Java, both of which are not supported for Android development.
\ No newline at end of file +You should have already been redirected by your browser. Please go to +System Requirements.
\ No newline at end of file diff --git a/docs/html/sdk/1.5_r2/index.jd b/docs/html/sdk/1.5_r2/index.jd index 15342a4339923..4fb99b604701c 100644 --- a/docs/html/sdk/1.5_r2/index.jd +++ b/docs/html/sdk/1.5_r2/index.jd @@ -1,87 +1,5 @@ -sdk.version=1.5 -sdk.rel.id=2 -sdk.date=May 2009 - -sdk.win_download=android-sdk-windows-1.5_r2.zip -sdk.win_bytes=178346828 -sdk.win_checksum=ba54ac6bda45921d442b74b6de6ff6a9 - -sdk.mac_download=android-sdk-mac_x86-1.5_r2.zip -sdk.mac_bytes=169945128 -sdk.mac_checksum=f4e06a5194410243f213d0177713d6c9 - -sdk.linux_download=android-sdk-linux_x86-1.5_r2.zip -sdk.linux_bytes=165035130 -sdk.linux_checksum=1d3c3d099e95a31c43a7b3e6ae307ed3 - page.title=Android 1.5 SDK, Release 2 +sdk.redirect=true +sdk.redirect.path=index.html + @jd:body - -For more information on this SDK release, read the -Release Notes.
- -The SDK includes a full set of tools for developing and debugging application code and designing an application UI. You can read about the tools in the
-Dev Guide and access them in the <sdk>/tools/ directory.
-
-
The tools package in this SDK includes updates from those provided in the previous SDK. The tools also require a different project structure. To use the new tools, you need to migrate your applications to the new development environment. For more information about how to migrate, see Upgrading the SDK. - -
For more information about the new tools features, see the SDK Release Notes. - -
This SDK includes multiple Android platform versions that you use to develop applications. For each version, both a fully compliant Android library and system image are provided. The table below lists the platform versions included in this SDK. For more information about a platform version — features, applications included, localizations, API changes, and so on — see its Version Notes.
- -| Notes | Description | -||
|---|---|---|---|
| 3 | -Includes a standard Android 1.5 library and system image with a set of development applications. Does not include any external libraries (such as the Maps external library). | -||
| 2 | -Includes a compliant Android 1.1 library and system image with a set of development applications. Also includes the Maps external library (due to legacy build system issues). | -
An SDK add-on provides a development environment for an Android external library or a customized (but fully compliant) Android system image. This SDK includes the SDK add-on listed below. The Android system API Level required by the add-on is noted.
- -| Notes | Description | -||
|---|---|---|---|
| 3 | -- | Includes the com.google.android.maps external library, a compliant -system image, a {@link android.location.Geocoder Geocoder} -backend service implementation, documentation, and sample code. | -
You can look at a variety of tutorials and samples in the Dev Guide and access the sample code itself
-in the <sdk>/platforms/android-1.5/samples/ directory of the SDK package. Note the new location — the SDK now includes multiple platform versions that you can develop against and each has its own sample code directory.
The SDK package includes a full set of local documentation. To view it, open the <sdk>/documentation.html file in a web browser. If you are developing in an IDE such as Eclipse, you can also view the reference documentation directly in the IDE.
The most current documentation is always available on the Android Developers site:
- - - diff --git a/docs/html/sdk/1.5_r2/installing.jd b/docs/html/sdk/1.5_r2/installing.jd index 1e4e0f2479c87..2ea04e4687546 100644 --- a/docs/html/sdk/1.5_r2/installing.jd +++ b/docs/html/sdk/1.5_r2/installing.jd @@ -1,332 +1,8 @@ -sdk.version=1.5 -sdk.rel.id=2 -sdk.date=April 2009 - -page.title=Installing the Android SDK @jd:body + -This page describes how to install the Android SDK and set up your -development environment. If you haven't downloaded the SDK, you can -do so from the -Download page. Once you've downloaded -the SDK, return here.
- -If you encounter any problems during installation, see the -Installation Notes at the bottom of -this page.
- -If you have already developed applications using an earlier version -of the SDK, please read -Upgrading the -SDK, instead. -
- - -Before you begin, take a moment to confirm that your development machine meets the -System Requirements. -
- -If you will be developing on 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.3 or newer). 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 SDK, unpack the .zip archive to a suitable location on your machine.
-By default, the SDK files are unpacked into a directory named
-android_sdk_<platform>_<release>.
-The directory contains a local copy of the documentation (accessible by opening
-documentation.html in your browser) and the subdirectories
-tools/, add-ons/, platforms/, and others. Inside
-each subdirectory of platforms/ you'll find samples/, which includes
-code samples that are specific to each version of the platform.
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 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.)
- -Once you have Eclipse 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.3 (Europa) | Eclipse 3.4 (Ganymede) |
|---|---|
-
-
|
-
-
-
-
|
-
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.
- - --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 the 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.
- - -Once you have completed installation, you are ready to -begin developing applications. Here are a few ways you can get started:
- -Learn about Android
-Explore the SDK
-Explore some code
-<sdk>/platforms/<platfrom>/samples,
- then compile and run it in your development environmentVisit the Android developer groups
-ia32-libs package using
- apt-get::
- apt-get install ia32-libs-
apt-get install sun-java6-bin
You should have already been redirected by your browser. Please go to +Installing the Android SDK.
\ No newline at end of file diff --git a/docs/html/sdk/1.5_r2/requirements.jd b/docs/html/sdk/1.5_r2/requirements.jd index c10ccac561ea1..96fdcb26f6fac 100644 --- a/docs/html/sdk/1.5_r2/requirements.jd +++ b/docs/html/sdk/1.5_r2/requirements.jd @@ -1,45 +1,8 @@ -page.title=System Requirements @jd:body -The sections below describe the system and software requirements for developing Android applications using the Android SDK tools included in Android SDK, Release .
+ -Note: If JDK is already installed on your development computer, please take a moment to make sure that it meets the version requirements listed above. In -particular, note that some Linux distributions may include JDK 1.4 or Gnu Compiler for Java, both of which are not supported for Android development.
\ No newline at end of file +You should have already been redirected by your browser. Please go to +System Requirements.
\ No newline at end of file diff --git a/docs/html/sdk/1.5_r3/index.jd b/docs/html/sdk/1.5_r3/index.jd index a79fe43e4146c..eb10f5ee435f3 100644 --- a/docs/html/sdk/1.5_r3/index.jd +++ b/docs/html/sdk/1.5_r3/index.jd @@ -1,88 +1,5 @@ -sdk.version=1.5 -sdk.rel.id=3 - -sdk.date=July 2009 - -sdk.win_download=android-sdk-windows-1.5_r3.zip -sdk.win_bytes=191477853 -sdk.win_checksum=1725fd6963ce69102ba7192568dfc711 - -sdk.mac_download=android-sdk-mac_x86-1.5_r3.zip -sdk.mac_bytes=183024673 -sdk.mac_checksum=b1bafdaefdcec89a14b604b504e7daec - -sdk.linux_download=android-sdk-linux_x86-1.5_r3.zip -sdk.linux_bytes=178117561 -sdk.linux_checksum=350d0211678ced38da926b8c9ffa4fac - page.title=Android 1.5 SDK, Release 3 +sdk.redirect=true +sdk.redirect.path=index.html + @jd:body - -For more information on this SDK release, read the -Release Notes.
- -The SDK includes a full set of tools for developing and debugging application code and designing an application UI. You can read about the tools in the
-Dev Guide and access them in the <sdk>/tools/ directory.
-
-
The tools package in this SDK includes updates from those provided in the previous SDK. The tools also require a different project structure. To use the new tools, you need to migrate your applications to the new development environment. For more information about how to migrate, see Upgrading the SDK. - -
For more information about the new tools features, see the SDK Release Notes. - -
This SDK includes multiple Android platform versions that you use to develop applications. For each version, both a fully compliant Android library and system image are provided. The table below lists the platform versions included in this SDK. For more information about a platform version — features, applications included, localizations, API changes, and so on — see its Version Notes.
- -| Notes | Description | -||
|---|---|---|---|
| 3 | -Includes a standard Android 1.5 library and system image with a set of development applications. Does not include any external libraries (such as the Maps external library). | -||
| 2 | -Includes a compliant Android 1.1 library and system image with a set of development applications. Also includes the Maps external library (due to legacy build system issues). | -
An SDK add-on provides a development environment for an Android external library or a customized (but fully compliant) Android system image. This SDK includes the SDK add-on listed below. The Android system API Level required by the add-on is noted.
- -| Notes | Description | -||
|---|---|---|---|
| 3 | -- | Includes the com.google.android.maps external library, a compliant -system image, a {@link android.location.Geocoder Geocoder} -backend service implementation, documentation, and sample code. | -
You can look at a variety of tutorials and samples in the Dev Guide and access the sample code itself
-in the <sdk>/platforms/android-1.5/samples/ directory of the SDK package. Note the new location — the SDK now includes multiple platform versions that you can develop against and each has its own sample code directory.
The SDK package includes a full set of local documentation. To view it, open the <sdk>/documentation.html file in a web browser. If you are developing in an IDE such as Eclipse, you can also view the reference documentation directly in the IDE.
The most current documentation is always available on the Android Developers site:
- - - diff --git a/docs/html/sdk/1.5_r3/installing.jd b/docs/html/sdk/1.5_r3/installing.jd index ac475d1260c79..2ea04e4687546 100644 --- a/docs/html/sdk/1.5_r3/installing.jd +++ b/docs/html/sdk/1.5_r3/installing.jd @@ -1,332 +1,8 @@ -sdk.version=1.5 -sdk.rel.id=3 -sdk.date=April 2009 - -page.title=Installing the Android SDK @jd:body + -This page describes how to install the Android SDK and set up your -development environment. If you haven't downloaded the SDK, you can -do so from the -Download page. Once you've downloaded -the SDK, return here.
- -If you encounter any problems during installation, see the -Installation Notes at the bottom of -this page.
- -If you have already developed applications using an earlier version -of the SDK, please read -Upgrading the -SDK, instead. -
- - -Before you begin, take a moment to confirm that your development machine meets the -System Requirements. -
- -If you will be developing on 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.3 or newer). 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 SDK, unpack the .zip archive to a suitable location on your machine.
-By default, the SDK files are unpacked into a directory named
-android_sdk_<platform>_<release>.
-The directory contains a local copy of the documentation (accessible by opening
-documentation.html in your browser) and the subdirectories
-tools/, add-ons/, platforms/, and others. Inside
-each subdirectory of platforms/ you'll find samples/, which includes
-code samples that are specific to each version of the platform.
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 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.)
- -Once you have Eclipse 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.3 (Europa) | Eclipse 3.4 (Ganymede) |
|---|---|
-
-
|
-
-
-
-
|
-
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.
- - --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 the 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.
- - -Once you have completed installation, you are ready to -begin developing applications. Here are a few ways you can get started:
- -Learn about Android
-Explore the SDK
-Explore some code
-<sdk>/platforms/<platfrom>/samples,
- then compile and run it in your development environmentVisit the Android developer groups
-ia32-libs package using
- apt-get::
- apt-get install ia32-libs-
apt-get install sun-java6-bin
You should have already been redirected by your browser. Please go to +Installing the Android SDK.
\ No newline at end of file diff --git a/docs/html/sdk/1.5_r3/requirements.jd b/docs/html/sdk/1.5_r3/requirements.jd index 5bcee27ed7534..96fdcb26f6fac 100644 --- a/docs/html/sdk/1.5_r3/requirements.jd +++ b/docs/html/sdk/1.5_r3/requirements.jd @@ -1,48 +1,8 @@ -sdk.version=1.5 -sdk.rel.id=3 -page.title=System Requirements - @jd:body -The sections below describe the system and software requirements for developing Android applications using the Android SDK tools included in Android SDK, Release .
+ -Note: If JDK is already installed on your development computer, please take a moment to make sure that it meets the version requirements listed above. In -particular, note that some Linux distributions may include JDK 1.4 or Gnu Compiler for Java, both of which are not supported for Android development.
\ No newline at end of file +You should have already been redirected by your browser. Please go to +System Requirements.
\ No newline at end of file diff --git a/docs/html/sdk/1.6_r1/index.jd b/docs/html/sdk/1.6_r1/index.jd index 8f33949c05d15..e7f9112ce2fbc 100644 --- a/docs/html/sdk/1.6_r1/index.jd +++ b/docs/html/sdk/1.6_r1/index.jd @@ -1,140 +1,5 @@ page.title=Android 1.6 SDK, Release 1 -sdk.redirect=0 -sdk.version=1.6 - -sdk.date=September 2009 - -sdk.win_download=android-sdk-windows-1.6_r1.zip -sdk.win_bytes=260529085 -sdk.win_checksum=2bcbacbc7af0363058ca1cac6abad848 - -sdk.mac_download=android-sdk-mac_x86-1.6_r1.zip -sdk.mac_bytes=247412515 -sdk.mac_checksum=eb13cc79602d492e89103efcf48ac1f6 - -sdk.linux_download=android-sdk-linux_x86-1.6_r1.tgz -sdk.linux_bytes=238224860 -sdk.linux_checksum=b4bf0e610ff6db2fb6fb09c49cba1e79 - -adt.zip_download=ADT-0.9.3.zip -adt.zip_version=0.9.3 -adt.zip_bytes=3252487 -adt.zip_checksum=c296488ac35772667c0f49e822156979 +sdk.redirect=true +sdk.redirect.path=index.html @jd:body - -For more information on this SDK release, read the -Release Notes.
- -The SDK includes a full set of tools for developing and debugging application
-code and designing an application UI. You can read about the tools in the Dev Guide and access them
-in the <sdk>/tools/ directory.
-
-
The tools package in this SDK includes updates from those provided in the -previous SDK. The tools use the same project structure as in the previous SDK -(Android 1.5). If you have application projects developed in the Android 1.5 -SDK, you can migrate them to the latest SDK without modification. For more -information about how to migrate, see Upgrading the -SDK. - -
This SDK includes multiple Android platform versions that you can use to -develop applications. For each version, both a fully compliant Android library -and system image are provided. The table below lists the platform versions -included in this SDK. For more information about a platform version — -features, applications included, localizations, API changes, and so on — -see its Version Notes.
- -| Notes | Description | -||
|---|---|---|---|
| 4 | -Includes a standard Android 1.6 library and system image with a set of -development applications. Does not include any external libraries (such as the -Maps external library). | -||
| 3 | -Includes a standard Android 1.5 library and system image with a set of -development applications. Does not include any external libraries (such as the -Maps external library). | -
Note that you can use the Android SDK and AVD Manager to download other -platform versions into your development environment.. - -
An SDK add-on provides a development environment for an Android external -library or a customized (but fully compliant) Android system image. This SDK -includes the SDK add-ons listed below. The Android system API Level required by -the add-ons are noted.
- -| Notes | Description | -||
|---|---|---|---|
| 4 | -- | Includes the com.google.android.maps external library, a compliant -Android 1.6 system image, a {@link android.location.Geocoder Geocoder} -backend service implementation, documentation, and sample code. | -|
| 3 | -- | Includes the com.google.android.maps external library, a compliant -Android 1.5 system image, a {@link android.location.Geocoder Geocoder} -backend service implementation, documentation, and sample code. | -
You can look at a variety of tutorials and samples in the Dev Guide and access the sample
-code itself in the <sdk>/platforms/<platform>/samples/
-directory of the SDK package. Note the new location — the SDK now includes
-multiple platform versions that you can develop against and each has its own
-sample code directory.
For example, to view or build the samples available for the Android
-1.6 platform (AVD target "Android 1.6"), you will find the samples in the
-<sdk>/platforms/android-1.6/samples/ directory of the SDK
-package.
The SDK package includes a full set of local documentation. To view it, open
-the <sdk>/documentation.html file in a web browser. If you
-are developing in an IDE such as Eclipse, you can also view the reference
-documentation directly in the IDE.
The most current documentation is always available on the Android Developers -site:
- -http://developer.android.com/ -
- - diff --git a/docs/html/sdk/1.6_r1/installing.jd b/docs/html/sdk/1.6_r1/installing.jd index 954bfa3f00392..2ea04e4687546 100644 --- a/docs/html/sdk/1.6_r1/installing.jd +++ b/docs/html/sdk/1.6_r1/installing.jd @@ -1,441 +1,8 @@ -page.title=Installing the Android 1.6 SDK -sdk.version=1.6 -sdk.preview=0 - @jd:body -This page describes how to install the Android SDK and set up your -development environment.
- -If you encounter any problems during installation, see the -Installation Notes at the bottom of -this page.
- -If you have already developed applications using an earlier version -of the Android SDK, please read Upgrading the SDK, instead. -
- - -Before you begin, take a moment to confirm that your development machine -meets the System Requirements.
- -If you will be developing on 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. | -||
Once you have completed installation, you are ready to -begin developing applications. Here are a few ways you can get started:
- -Learn about Android
-Explore the SDK
-Explore some code
-<sdk>/platforms/<platform>/samples,
- then compile and run it in your development environmentVisit the Android developer groups
-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.
- + +You should have already been redirected by your browser. Please go to +Installing the Android SDK.
\ No newline at end of file diff --git a/docs/html/sdk/1.6_r1/requirements.jd b/docs/html/sdk/1.6_r1/requirements.jd index 8cfc0494b820b..96fdcb26f6fac 100644 --- a/docs/html/sdk/1.6_r1/requirements.jd +++ b/docs/html/sdk/1.6_r1/requirements.jd @@ -1,57 +1,8 @@ -page.title=System Requirements -sdk.version=1.6 -sdk.preview=0 @jd:body -The sections below describe the system and software requirements for developing -Android applications using the Android SDK tools included in Android - SDK, Release .
- -Note: If JDK is already installed on your development computer, please take a moment to make sure that it meets the version requirements listed above. In -particular, note that some Linux distributions may include JDK 1.4 or Gnu Compiler for Java, both of which are not supported for Android development.
- -You should have already been redirected by your browser. Please go to +System Requirements.
\ No newline at end of file diff --git a/docs/html/sdk/RELEASENOTES.jd b/docs/html/sdk/RELEASENOTES.jd index bca89f610b7c8..cbfac2b67e7e9 100644 --- a/docs/html/sdk/RELEASENOTES.jd +++ b/docs/html/sdk/RELEASENOTES.jd @@ -76,11 +76,8 @@ value the application declares in its manifest. For more information, seeFor details about the Android platforms included in the SDK — including -bug fixes, features, and API changes — please read the Version Notes -documents available at left. For a list of Android platforms included in this -release, see the Download -page. Note that you can use the Android SDK and AVD Manager to download -additional platforms.
+bug fixes, features, and API changes — please read the Android 1.6 version notes.If you're installing the Android SDK for the first time, please see -the instructions in Installing the SDK. -
An updated version of the ADT Plugin for Eclipse is available with the @@ -115,8 +108,8 @@ Plugin (0.9.3 or higher).
The new version of ADT is downloadable from the usual remote update site or is separately downloadable as a .zip archive. For instructions on how to -download the plugin, please see Upgrading -Your Eclipse Plugin.
+download the plugin, please see Installing and Updating ADT.The USB driver files are located in the
-<SDK>/usb_driver directory. For driver installation or
+
For driver installation or upgrade instructions, see Installing the WinUSB -Driver.
+href="{@docRoot}sdk/win-usb.html">USB Driver for Windows.For details about the Android platforms included in the SDK — including -bug fixes, features, and API changes — please read the Version Notes -documents available at left. For a list of Android platforms included in this -release, see the Download -page.
+bug fixes, features, and API changes — please read the Android 1.5 version notes.If you're installing the Android SDK for the first time, please see -the instructions in Installing the SDK. -
This version of the SDK introduces support for SDK add-ons, which extend the @@ -457,11 +442,9 @@ these USB drivers that you can install, to let you develop on the device:
The USB driver files are located in the
-<SDK>/usb_driver directory. For details and
-installation instructions, see Setting Up a
-Device for Development.
For driver installation or +upgrade instructions, see USB Driver for Windows.
For details about the Android 1.1 system image included in the SDK — including bug fixes, features, and API changes — please read the Android 1.1 Version Notes.
+href="{@docRoot}sdk/android-1.1.html">Android 1.1 version notes.-wipe-data) when running your
application on the Android 1.1 emulator for the first time.
-If you're installing the Android SDK for the first time, please see -the instructions in Installing the SDK. -
MapView API Key
@@ -673,13 +651,7 @@ added. Development Tools (ADT) Plugin for Eclipse is 0.8.0. If you are using a previous version of ADT, you should update to the latest version for use with this SDK. For information about how to update your ADT plugin, see Upgrading the SDK. - -If you're installing the Android SDK for the first time, please see the -instructions in Installing the -SDK. +href="{@docRoot}sdk/eclipse-adt.html">Installing and Updating ADT.
If you've been developing an application using a previous SDK version and you want the application to run on Android-powered mobile devices, you must port the application to the Android 1.0 SDK. Please see Upgrading the SDK for detailed instructions on how to make the transition to this release. Be sure to wipe application user data (emulator option -wipe-data) when running your application on the Android 1.0 SDK emulator.
If you're installing the Android SDK for the first time, please see the instructions in Installing the SDK. -
MapView API Key
diff --git a/docs/html/sdk/older_releases.jd b/docs/html/sdk/older_releases.jd index 0ecee3c14ef7e..c3ba49566e70f 100644 --- a/docs/html/sdk/older_releases.jd +++ b/docs/html/sdk/older_releases.jd @@ -1,51 +1,369 @@ -page.title=Other SDK Releases +page.title=SDK Archives @jd:body -This page provides a full list of older, obsolete SDK releases, including -non-current versions of active releases and "early look" versions that were -released before Android 1.0. The list is provided for informational purposes -only.
+This page provides a full list of archived and obsolete SDK releases, +including non-current versions of active releases and "early look" versions that +were released before Android 1.0. These are provided for +informational and archival purposes only.
-If you are just getting started developing on Android, make sure that you -are using the most current SDK available, -to ensure that your applications will be compatible with the latest -Android-powered devices.
+If you are just starting to develop applications for Android, please +download the current Android +SDK. With the current Android SDK, you can add any current and previous +version of the Android platform as a component and use it for +development and testing.
+If you already have an Android SDK for platform version 1.6 or newer, then +you do not need to install a new SDK—especially not one from this page. +You should install older platforms as components of your existing SDK. +See Adding SDK Components.
+The table below lists Android SDK releases that have been superceded by an -active release and that are now obsolete. If you are using one of these -releases, please upgrade to the current SDK -release.
+| Platform | +Package | +Size | +MD5 Checksum | +
|---|---|---|---|
| Release - | Platform(s) | -Date - | Description - |
| Android 1.5 SDK, Release 2 | -Android 1.5 Android 1.1 |
- May 2009 | -Replaced by Android 1.5 SDK, Release 3. Release notes | -
| Android 1.5 SDK, Release 1 | -Android 1.5 Android 1.1 |
- April 2009 | -Replaced by Android 1.5 SDK, Release 2. Release notes | -
| Android 1.0 SDK, Release 1 | -Android 1.0 | -September 2008 | -Replaced by Android 1.0 SDK, Release 2. Release notes | -
July 2009 - Release +Notes
+ +| Platform | +Package | +Size | +MD5 Checksum | +
|---|---|---|---|
| Windows | ++ android-sdk- +windows-1 .5_r3.zip + | +191477853 bytes | +1725fd6963ce69102ba7192568dfc711 | +
| Mac OS X (intel) | ++ android-sdk- +mac_x86-1 .5_r3.zip + | +183024673 bytes | +b1bafdaefdcec89a14b604b504e7daec | +
| Linux (i386) | ++ android- +sdk- linux_x86-1.5_r3.zip + | +178117561 bytes | +350d0211678ced38da926b8c9ffa4fac | +
February 2009 - Release +Notes
+ +| Platform | +Package | +Size | +MD5 Checksum | +
|---|---|---|---|
| Windows | ++ android-sdk- +windows-1 +.1_r1.zip + | +86038515 bytes | +8c4b9080b430025370689e03d20842f3 | +
| Mac OS X (intel) | ++ android-sdk- +mac_x86-1 +.1_r1.zip + | +79046151 bytes | +becf0f1763d61eedce15d2a903d6c1dd | +
| Linux (i386) | ++ android- +sdk- +linux_x86-1.1_r1.zip + | +79345522 bytes | +ebcb16b0cd4aef198b4dd9a1418efbf1 | +
November 2008 - Release +Notes
+ +| Platform | +Package | +Size | +MD5 Checksum | +
|---|---|---|---|
| Windows | ++ android-sdk- +windows-1 +.0_r2.zip + | +98360564 bytes | +a5e1af8ac145946b4a9627516ad4a711 | +
| Mac OS X (intel) | ++ android-sdk- +mac_x86-1 +.0_r2.zip + | +93771410 bytes | +87b99d5e9f59b78363a63200c11498e8 | +
| Linux (i386) | ++ android- +sdk- +linux_x86-1.0_r2.zip + | +94186463 bytes | +a1f3b6d854596f850f5008856d0f380e | +
These tables provide Android SDK releases that have been superceded by +an active release (shown above) and that are now obsolete.
+ + +May 2009 - Release +Notes
+ +| Platform | +Package | +Size | +MD5 Checksum | +
|---|---|---|---|
| Windows | ++ android-sdk- +windows-1 .5_r2.zip + | +178346828 bytes | +ba54ac6bda45921d442b74b6de6ff6a9 | +
| Mac OS X (intel) | ++ android-sdk- +mac_x86-1 .5_r2.zip + | +169945128 bytes | +f4e06a5194410243f213d0177713d6c9 | +
| Linux (i386) | ++ android- +sdk- linux_x86-1.5_r2.zip + | +165035130 bytes | +1d3c3d099e95a31c43a7b3e6ae307ed3 | +
April 2009 - Release +Notes
+ +| Platform | +Package | +Size | +MD5 Checksum | +
|---|---|---|---|
| Windows | ++ android-sdk- +windows-1 .5_r1.zip + | +176263368 bytes | +42be980eb2d3efaced01ea6c32c0045f | +
| Mac OS X (intel) | ++ android-sdk- +mac_x86-1 .5_r1.zip + | +167848675 bytes | +5b2a8d9f096032db4a75bfa0d689a51b | +
| Linux (i386) | ++ android- +sdk- linux_x86-1.5_r1.zip + | +162938845 bytes | +2addfd315da0ad8b5bde6b09d5ff3b06 | +
September 23, 2008 - Release +Notes
+ +| Platform | +Package | +Size | +MD5 Checksum | +
|---|---|---|---|
| Windows | ++ android-sdk- +windows-1 .0_r1.zip + | +89.7 MB bytes | +d69f4ee93d4010f726c04302662fd999 | +
| Mac OS X (intel) | ++ android-sdk- +mac_x86-1 .0_r1.zip + | +87.5 MB bytes | +564876ada22872e50c2866806de9fc5c | +
| Linux (i386) | ++ android- +sdk- linux_x86-1.0_r1.zip + | +87.8 MB bytes | +2660b4029039b7d714e59827e9a9a11d | +
The SDKs listed below are "early-look" versions that were released in @@ -63,7 +381,7 @@ the previous version. You can find the migration information in the documentation included in each SDK package.
-August 18, 2008 - Release Notes
| Windows | -android-sdk-windows-0.9_beta.zip | + +android-sdk-windows-0.9_beta.zip93,126,573 bytes | 305031ad8335d1b6040bdd5a65349d6d |
| Mac OS X (intel) | -android-sdk-mac_x86-0.9_beta.zip | + +android-sdk-mac_x86-0.9_beta.zip91,374,464 bytes | 9a6969159091cede46302e11049fe3ca |
| Linux (i386) | -android-sdk-linux_x86-0.9_beta.zip | +android-sdk-linux_x86-0.9_beta.zip91,821,068 bytes | 077e5ef549dd9c5be54bd88e6a8e196c |
| Windows | -android-sdk_m5-rc15_windows.zip | + +android-sdk_m5-rc15_windows.zip79 MB | ecce40bc50201886d95ba2690cdbc5ce |
| Mac OS X (intel) | -android-sdk_m5-rc15_mac-x86.zip | + +android-sdk_m5-rc15_mac-x86.zip76 MB | 45a6385bbc1b2cb295409cfc81fb04b4 |
| Linux (i386) | -android-sdk_m5-rc15_linux-x86.zip | + +android-sdk_m5-rc15_linux-x86.zip76 MB | e913f785afecdeed34c30639fd8c5862 |
| Windows | -android-sdk_m5-rc14_windows.zip | + +android-sdk_m5-rc14_windows.zip79 MB | ecc75c1e69588350634ca25867ce05a0 |
| Mac OS X (intel) | -android-sdk_m5-rc14_mac-x86.zip | + +android-sdk_m5-rc14_mac-x86.zip76 MB | 844c80d0adb1a326f5a9fff262c61efc |
| Linux (i386) | -android-sdk_m5-rc14_linux-x86.zip | + +android-sdk_m5-rc14_linux-x86.zip76 MB | f8b863c8a880afe9bb84124f5976aab1 |
| Windows | -android_sdk_windows_m3-rc37a.zip | + +android_sdk_windows_m3-rc37a.zip58 MB | 5db5aea20a2c2f010baefc4b1091a575 |
| Mac OS X (intel) | -android_sdk_darwin_m3-rc37a.zip | + +android_sdk_darwin_m3-rc37a.zip54 MB | 0b22e73fbd07b4af4009387afce3a37f |
| Linux (i386) | -android_sdk_linux_m3-rc37a.zip | + +android_sdk_linux_m3-rc37a.zip54 MB | 41285beecc4f9926e6ecf5f12610b356 |
| Windows | -android_sdk_windows_m3-rc22a.zip | + +android_sdk_windows_m3-rc22a.zip59 MB | aa3dee05a9872752a3bc4efd0f93e98b |
| Mac OS X (intel) | -android_sdk_darwin_m3-rc22a.zip | + +android_sdk_darwin_m3-rc22a.zip55 MB | 0547f45614ad94c3af22c3c0aa6f709f |
| Linux (i386) | -android_sdk_linux_m3-rc22a.zip | + +android_sdk_linux_m3-rc22a.zip55 MB | 84b3455de5cdfd841a172c13d24c382e |
| Windows | -android_sdk_windows_m3-rc20a.zip | + +android_sdk_windows_m3-rc20a.zip59 MB | a404b875708df7339ba77bdf2e08dc06 |
| Mac OS X (intel) | -android_sdk_darwin_m3-rc20a.zip | + +android_sdk_darwin_m3-rc20a.zip55 MB | 8fc29aeaa45eda84bfac854ebd02a6da |
| Linux (i386) | -android_sdk_linux_m3-rc20a.zip | + +android_sdk_linux_m3-rc20a.zip55 MB | 9196759df9b69cd89a220b156f133364 |