R.id.main
) to the corresponding XML declaration, or from XML attributes (such as @string
) to the corresponding resource definition, or from manifest XML registrations to activities and services.<include>
and <merge>
tags (Details).AdapterView
.EditText
object is set to match_parent
when added to a vertical LinearLayout
or a default image is added to an ImageButton
.<include>
tag, double-clicking on the <include>
element edits the referenced layout in the context of the current layout. Additionally, when editing a layout that is included by other layouts, you can quickly change between context layouts, by right clicking in the editor and choosing Show included in.... This feature is only available in Honeycomb.debuggable=true
was not set in the Android manifest.debuggable
attribute in the Android Manifest. debuggable='true'
, but if you perform 'export signed/unsigned application package', ADT does not insert it. If you manually set debuggable='true'
in the manifest file, then release builds will actually create a debug build (it does not remove it if you placed it there).proguard.config
property in the default.properties
file that points to a ProGuard config file.android.jar
source and javadoc location can now be configured.src/
. There is now support for any number of source folders,with no name restriction. They can even be in subfolder such assrc/java
. If you are already working with library projects createdin ADT 0.9.7, see Migratinglibrary projects to ADT 0.9.8 for important information about movingto the new ADT environment.car
/desk
, night
/notnight
andnavexposed
/navhidden
.default.properties
outside of Eclipse will nowautomatically update the project.Eclipse 3.5 (Galileo) and 3.6 (Helios) | Eclipse 3.4 (Ganymede) |
---|---|
|
|
Name | Package | Size | MD5 Checksum |
---|---|---|---|
ADT 9.0.0 | ADT_9.0.0.zip | 4433536 bytes | bc2757f2a5a11d131390ce547bae154b |
Eclipse 3.5 (Galileo) and 3.6 (Helios) | Eclipse 3.4 (Ganymede) |
---|---|
|
|
.zip
or .tgz
package (instead of the SDK installer), unpackit to a safe location on your machine. By default, the SDK files are unpackedinto a directory named android-sdk-<machine-platform>
..exe
file), run it now and it will checkwhether the proper Java SE Development Kit (JDK) is installed (installing it, if necessary), theninstall the SDK Tools into a default location (which you can modify).SDK Manager.ext
file at the root of the AndroidSDK directory.tools/
directory in theAndroid SDK, then execute: <sdk>/tools/
directory of your SDK and read more about them in the Tools section of the developer guide. <sdk>/platform-tools/
directory. Read more about them inthe Tools section of the developer guide.Environment | SDK Component | Comments |
---|---|---|
Basic | SDK Tools | If you've just installedthe SDK starter package, then you already have the latest version of this component. TheSDK Tools component is required to develop an Android application. Make sure you keep this up todate. |
SDK Platform-tools | This includes more tools that are requiredfor application development. These tools are platform-dependent and typically update only whena new SDK platform is made available, in order to support new features in the platform. Thesetools are always backward compatible with older platforms, but you must be sure that you havethe latest version of these tools when you install a new SDK platform. | |
SDK platform | You need to download | |
+ | ||
Recommended (plus Basic) | Documentation | The Documentation component is useful because it lets you work offline andalso look up API reference information from inside Eclipse. |
Samples | The Samples components give you source code that you can use to learn aboutAndroid, load as a project and run, or reuse in your own app. Note that multiplesamples components are available — one for each Android platform version. Whenyou are choosing a samples component to download, select the one whose API Levelmatches the API Level of the Android platform that you plan to use. | |
Usb Driver | The Usb Driver component is needed only if you are developing on Windows andhave an Android-powered device on which you want to install your application fordebugging and testing. For Mac OS X and Linux platforms, nospecial driver is needed. | |
+ | ||
Full (plus Recommended) | Google APIs | The Google APIs add-on gives your application access to the Maps externallibrary, which makes it easy to display and manipulate Maps data in yourapplication. |
Additional SDK Platforms | If you plan to publish your application, you will want to downloadadditional platforms corresponding to the Android platform versions on which youwant the application to run. The recommended approach is to compile yourapplication against the lowest version you want to support, but test it againsthigher versions that you intend the application to run on. You can test yourapplications on different platforms by running in an Android Virtual Device(AVD) on the Android emulator. |
Name | Description | ||
---|---|---|---|
add-ons/ | Contains add-ons to the Android SDK developmentenvironment, which let you develop against external libraries that are available on somedevices. | ||
docs/ | A full set of documentation in HTML format, including the Developer's Guide,API Reference, and other information. To read the documentation, load thefile offline.html in a web browser. | ||
platform-tools/ | Contains development tools that may be updated with each platform release (from the AndroidSDK Platform-tools component). Tools in here include adb , dexdump , and othersothers that you don't typically use directly. These tools are separate from the generic developmenttools in the tools/ directory, because these tools may be updated in order to support newfeatures in the latest Android platform, whereas the other tools have no dependencies on theplatform version. | ||
platforms/ | Contains a set of Android platform versions that you can developapplications against, each in a separate directory. | ||
<platform>/ | Platform version directory, for example 'android-1.6'. All platform versiondirectories 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 imagesare used in emulator sessions. | ||
skins/ | A set of emulator skins available for the platform version. Each skin isdesigned for a specific screen resolution. | ||
templates/ | Storage area for file templates used by the SDK development tools. | ||
tools/ | This directory is used only by SDK Tools r7 and below for development tools that are specific tothis platform version—it's not used by SDK Tools r8 and above. | ||
android.jar | The Android library used when compiling applications against this platformversion. | ||
samples/ | Sample code and apps that are specific to platform version. | ||
tools/ | Contains the set of development and profiling tools that are platform-independent, suchas the emulator, the AVD and SDK Manager, ddms, hierarchyviewer and more. The tools inthis directory may be updated at any time (from the Android SDK Tools component),independent of platform releases, whereas the tools in platform-tools/ may be updated basedon the latest platform release. | ||
SDK Readme.txt | A file that explains how to perform the initial setup of your SDK,including how to launch the Android SDK and AVD Manager tool on allplatforms | ||
SDK Manager.exe | Windows SDK only. A shortcut that launches the Android SDK and AVDManager tool, which you use to add components to your SDK. |
tools/
andplatform-tools
to your PATH
environment variable, to provide easyaccess to the tools.tools/
and platform-tools/
to your PATH lets you runcommand line tools without needing tosupply the full path to the tool directories. Depending on your operating system, you caninclude these directories in your PATH in the following way:tools/
and platform-tools/
directories to the path. ~/.bash_profile
or ~/.bashrc
file. Look for a line that sets the PATH environment variable and add the full path to the tools/
and platform-tools
directories to it. If you don't see a line setting the path, you can add one: .bash_profile
and proceed as for Linux. You can create the .bash_profile
if you don't already have one. <sdk>/samples/<platform>/
. ia32-libs
package using apt-get:
: