Eclipse For Android Mac Os

  1. Eclipse For Android Download
  2. Eclipse Android Mac Os
  3. Install Eclipse On Mac
  1. In Eclipse, you can configure proxy information from the main Eclipse menu in Window (on Mac OS X, Eclipse) Preferences General Network Connections. 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: Download the.
  2. For future readers, do not store under /Developer/android-sdk-mac or anywhere under /Developer if you're on iOS 10.6, because when you upgrade to 10.7, Apple throws your /Developer directory in the.Trash – James Jul 27 '12 at 16:10.

Eclipse has no impact on Mac OS beyond it directory, so there is no problem uninstalling. I think that What you are facing is the result of Eclipse switching the plugin distribution system recently. There are now two redundant and not very compatible means of installing plugins. It's a complete mess.

In this document

  1. Installing the ADT Plugin

Android Development Tools (ADT) is a plugin for the Eclipse IDEthat is designed to give you a powerful, integrated environment in whichto build Android applications.

ADT extends the capabilities of Eclipse to let you quickly set up new Androidprojects, create an application UI, add components based on the AndroidFramework API, debug your applications using the Android SDK tools, and evenexport signed (or unsigned) APKs in order to distribute your application.

Developing in Eclipse with ADT is highly recommended and is the fastest wayto get started. With the guided project setup it provides, as well as toolsintegration, custom XML editors, and debug ouput pane, ADT gives you anincredible boost in developing Android applications.

This document provides step-by-step instructions on how to download the ADTplugin and install it into your Eclipse development environment. Note thatbefore you can install or use ADT, you must have compatible versions of both theEclipse IDE and the Android SDK installed. For details, make sure to read Installing the ADT Plugin, below.

If you are already using ADT, this document also provides instructions onhow to update ADT to the latest version or how to uninstall it, if necessary.

Eclipse For Android Mac Os

Revisions

The sections below provide notes about successive releases ofthe ADT Plugin, as denoted by revision number.

ADT 9.0.0(January 2011)
Dependencies:
ADT 9.0.0 is designed for use with SDK Tools r9. If you haven'talready installed SDK Tools r9 into your SDK, use the Android SDK and AVD Manager to doso.
General notes:
  • 'Go To Declaration' hyperlink support: You can jump directly from code references (such as 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.
  • Improvements were made to name refactoring.
  • AVDs now automatically save their state, so they can restart almost instantly. You can enable this feature when creating an AVD or by editing an AVD with the AVD Manager.
  • Improvements to the Visual Layout Editor:
    • Support for rendering targets: You can now choose an arbitrary Android platform to render the current page, regardless of the project's minimum platform. This makes it easy to verify the layout and appearance of your activity on different versions of the platform.
    • Improved support for empty and nested layouts: Dragging items over nested and invisible layouts automatically enlarges and highlights these layouts, so that they can receive drops.
    • XML formatting improvements: The editor generates cleaner XML and you can now enable XML auto-formatting in the Preferences menu.
    • Improved Outline labels: The Outline tab now displays additional information about each View. Textual Views display a snippet of the actual text. Views with a source (such as ImageView) displays the resource name. Included Views display the name of the View.
    • When you right click a View in the Layout Editor, the context menu now contains Edit ID... and Edit Text... items. The Properties... context menus now list all of the properties and provide a way to edit them (Details).
    • The layout editor now properly handles <include> and <merge> tags (Details).
    • 'Extract as Include' refactoring: The Layout Editor has a new refactoring that allows you to select one or more views in a layout, and extract it into a separate layout (Details).
    • Improved diagnostics for class loading and rendering errors: Class loading and rendering error messages are more useful and provide better information about the root cause of the error.
    • Improved error handling to prevent drag and reordering operations from adding children into an AdapterView.
    • Outline reordering: Reordering your views in the Outline tab is much easier (Details).
    • Fix for keybinding bug where keyboard shortcuts did not work (Issues 13231 and 13134).
    • Fix for problems with Custom layout attribute menu (Issue 13134).
    • Automatic configuration for various view types: Certain views have properties configured by default. For example, the width of an EditText object is set to match_parent when added to a vertical LinearLayout or a default image is added to an ImageButton.
    • Previews during dragging: Dragging from the palette or dragging within the layout editor now shows live previews of the dragged item.
    • Navigation improvements: In the Layout Editor, double-clicking Views jumps to the corresponding XML element. In the Outline view, double-clicking opens the Properties view.
    • The editor has Honeycomb style animation preview support.
    • Improved rendering support for various Views (such as TabHosts and SlidingDrawers) in Honeycomb (Issues 3162 and 13092).
    • Included layouts can be rendered and edited in the context of the layouts that include them. From a layout using an <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.
  • This release fixes many other bugs, but the most important ones are listed below:
    • Fixed issue that prevented launching debug builds on productions devices when debuggable=true was not set in the Android manifest.
    • The LogCat view in DDMS properly handles UTF-8 characters.
    • The SDK Manager is more reliable on Windows (Details).
    • A JUnit initialization bug that prevented you from working with JUnit tests was fixed (Issue 12411).

Eclipse For Android Download

ADT 8.0.1(December 2010)
Dependencies:

ADT 8.0.1 is designed for use with SDK Tools r8. If you haven'talready installed SDK Tools r8 into your SDK, use the Android SDK and AVD Manager to doso.

General notes:
  • This is a quick follow-up to ADT 8.0.0 to fix some bugs.
  • Fixes an issue in which projects failed to compile, citing a dex error.
  • Better ProGuard error reporting when exporting applications for release.

Also see the recent release notes for 8.0.0, below.

ADT 8.0.0Mac(December 2010)
Dependencies:

ADT 8.0.0 is designed for use with SDK Tools r8. If you haven'talready installed SDK Tools r8 into your SDK, use the Android SDK and AVD Manager to doso.

General notes:
  • New version number scheme that follows the SDK Tools revision number. The major versionnumber for your ADT plugin should now always match the revision number of your SDK Tools. Forexample, ADT 8.x is for SDK Tools r8.
  • Support for true debug build. You no longer need to change the value of the debuggable attribute in the Android Manifest.

    Incremental builds automatically insert 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).

  • Automatic ProGuard support in release builds. For it to work, you need to have a proguard.config property in the default.properties file that points to a ProGuard config file.
  • Completely rewritten Visual Layout Editor. (This is still a work in progress.) Now includes:
    • Full drag and drop from palette to layout for all Layout classes.
    • Move widgets inside a Layout view, from one Layout view to another and from one layout file to another.
    • Contextual menu with enum/flag type properties.
    • New zoom controls.
  • New HierarchyViewer plug-in integrated in Eclipse.
  • Android launch configurations don't recompile the whole workspace on launch anymore.
  • android.jar source and javadoc location can now be configured.
ADT 0.9.9(September 2010)
Dependencies:

ADT 0.9.9 replaces ADT 0.9.8 and is designed for use with SDK Tools r7and later. ADT 0.9.9 includes the ADT 0.9.8 features as well as an importantbugfix, so we recommend that you upgrade as soon as possible. If you haven'talready installed SDK Tools r7 into your SDK, use the Android SDK Manager to doso.

General notes:
  • Fixes a problem in project import, in which source files were deleted in some cases.
  • Includes all other ADT 0.9.8 features (see below).
ADT 0.9.8(September 2010)
Dependencies:

ADT 0.9.8 is now deprecated. Please use ADT 0.9.9 instead.

General notes:
  • Adds a new Action, 'Rename Application Package', to the Android Toolscontextual menu. The Action does a full application package refactoring.
  • Adds support for library projects that don't have a source foldercalled 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.
  • Adds support for library projects that depend on other libraryprojects.
  • Adds support for additional resource qualifiers:car/desk, night/notnight andnavexposed/navhidden.
  • Adds more device screen types in the layout editor. All screenresolution/density combinations listed in the SupportingMultiple Screens are now available.
  • Fixes problems with handling of library project names thatcontain characters that are incompatible with the Eclipse path variable.Now properly sets up the link between the main project and the libraryproject.
ADT 0.9.7(May 2010)
Library projects:

The ADT Plugin now supports the use of library projects duringdevelopment, a capability that lets you store shared Android applicationcode and resources in a separate development project. You can then reference thelibrary project from other Android projects and, at build time, the toolscompile the shared code and resources as part of the dependent applications.More information about this feature is available in the Developingin Eclipse with ADT document.

If you are not developing in Eclipse, SDK Tools r6 provides the equivalent libraryproject support through the Ant build system.

ADT 0.9.6(March 2010)
Dependencies:

ADT 0.9.6 is designed for use with SDK Tools r5 and later. Beforeupdating to ADT 0.9.6, we highly recommend that you use the Android SDK andAVD Manager to install SDK Tools r5 into your SDK.

General Notes:
  • Editing default.properties outside of Eclipse will nowautomatically update the project.
  • Loads the SDK content only when a project requires it. This will makeEclipse use less resources when the SDK contains many versions of Android.
  • Resolves potential deadlock between modal dialogs, when launching ADT thefirst time with the SDK Usage panel.
  • Fixes issues with the New Project Wizard when selecting samples.
AVD/SDK Manager:
  • Adds support for platform samples components.
  • Improves support for dependency between components.
  • AVDs now sorted by API level.
  • The AVD creation dialog now enforces a minimum SD card size of 9MB.
  • Prevents deletion of running AVDs.
DDMS:
  • DDMS plug-in now contains the Allocation Tracker view.
  • New action in the Logcat view: 'Go to problem' lets you go directly from anexception trace output to the code.
Editors:
  • Explode mode in the Visual Layout Editor adds a margin to all layout objectsso that it's easier to see embedded or empty layouts.
  • Outline mode in the Visual Layout Editor draws layout outline to make iteasier to see layout objects.
  • Several fixes in the configuration selector of the Visual LayoutEditor.
Application launching:
  • Applications launched from ADT now behave as if they were clicked from theHome screen.
  • Fixes issue where add-on with no optional library would not show up as validtargets for application launches.
  • Resolves possible crash when launching applications.
ADT 0.9.5(December 2009)
Dependencies:

ADT 0.9.5 requires features provided in SDK Tools r4 or higher. If you installADT 0.9.5, which is highly recommended, you should use the Android SDK and AVDManager to download the latest SDK Tools into your SDK. For more information,see Adding SDK Components.

General Notes:
  • AVD Launch dialog now shows scale value.
  • Fixes potential NPE in SDK Manager on AVD launch, for older AVD with no skin name specified.
  • Fixes XML validation issue in on older Java versions.
  • .apk packaging now properly ignores vi swap files as well as hidden files.
ADT 0.9.4(October 2009)
Dependencies:

ADT 0.9.4 requires features provided in SDK Tools r3 or higher. If you installADT 0.9.4, which is highly recommended, you should use the Android SDK and AVDManager to download the latest SDK Tools into your SDK. For more information,see Adding SDK Components.

Project Creation Wizard:
  • New option to create a project from a sample by choosing it from a list.
Layout Editor:
  • Improved Configuration selector that lets you see how your layout willrender on different devices. Default device descriptions include ADP1and Google Ion, while SDK add-ons can also provide new descriptions.A new UI allows you to create custom descriptions.
  • Adds a new clipping toggle, to let you see your full layout even if it'sbigger than the screen.
DDMS Integration:
  • Includes the improvements from the standlone DDMS, revision 3.
  • Adds an option to open HPROF files into eclipse instead of writing them ondisk. If a profiler such as MAT (Memory AnalyzerTool) is installed, it'll open the file.
Android SDK and AVD Manager integration:
  • Includes the improvements from the standalone Android SDK and AVD Manager,revision 3.

Installing the ADT Plugin

The sections below provide instructions on how to download and installADT into your Eclipse environment. If you encounter problems, see the Troubleshooting section.

Preparing Your Development Computer

ADT is a plugin for the Eclipse IDE. Before you can install or use ADT,you must have a compatible version of Eclipse installed on your developmentcomputer.

  • If Eclipse is already installed on your computer, make sure that it isa version that is compatible with ADT and the Android SDK. Check the System Requirements document fora list of Eclipse versions that are compatible with the Android SDK.
  • If you need to install or update Eclipse, you can download it from thislocation:

    For Eclipse 3.5 or newer, the 'Eclipse Classic' version is recommended. Otherwise, a Java or RCPversion of Eclipse is recommended.

Additionally, before you can configure or use ADT, you must install theAndroid SDK starter package, as described in Downloading the SDK Starter Package.Specifically, you need to install a compatible version of the Android SDK Toolsand at least one development platform. To simplify ADT setup, we recommendinstalling the Android SDK prior to installing ADT.

When your Eclipse and Android SDK environments are ready, continue with theADT installation as described in the steps below.

Downloading the ADT Plugin

Use Update Manager feature of your Eclipse installation to install the latestrevision of ADT on your development computer.

Assuming that you have a compatible version of the Eclipse IDE installed, asdescribed in Preparing for Installation, above, followthese steps to download the ADT plugin and install it in your Eclipseenvironment.

Eclipse 3.5 (Galileo) and 3.6 (Helios)Eclipse 3.4 (Ganymede)
  1. Start Eclipse, then select Help > Install NewSoftware....
  2. Click Add, in the top-right corner.
  3. In the Add Repository dialog that appears, enter 'ADT Plugin' for the Name and thefollowing URL for the Location:

    Note: If you have trouble acquiring the plugin, try using 'http' in the Location URL, instead of 'https' (https is preferred for security reasons).

    Click OK.

  4. In the Available Software dialog, selectthe checkbox next to Developer Tools and click Next.
  5. In the next window, you'll see a list of the tools to be downloaded. ClickNext.
  6. Read and accept the license agreements, then click Finish.
  7. When the installation completes, restart Eclipse.
  1. Start Eclipse, then select Help > Software Updates....In the dialog that appears, click the Available Software tab.
  2. Click Add Site.
  3. In the Add Site dialog that appears, enter this URL in the 'Location' field:

    Note: If you have trouble acquiring the plugin, you can try using 'http' in the URL, instead of 'https' (https is preferred for security reasons).

    Click OK.

  4. Back in the Available Software view, you should see the plugin listed by the URL, with 'Developer Tools' nested within it. Select the checkbox next to Developer Tools, which will automatically select the nested tools. Then click Install
  5. On the subsequent Install window, all of the included tools should be checked. Click Next.
  6. Read and accept the license agreements, then click Finish.
  7. When the installation completes, restart Eclipse.

Eclipse Android Mac Os

Configuring the ADT Plugin

Once you've successfully downloaded ADT as described above, the next stepis to modify your ADT preferences in Eclipse to point to the Android SDK directory:

  1. Select Window > Preferences... to open the Preferences panel (Mac OS X: Eclipse > Preferences).
  2. Select Android from the left panel.
  3. For the SDK Location in the main panel, click Browse... and locate your downloaded SDK directory.
  4. Click Apply, then OK.

Done! If you haven't encountered any problems, then the installation iscomplete. If you're installing the Android SDK for the first time, return to Installing the SDK to complete your setup.

Troubleshooting ADT Installation

If you are having trouble downloading the ADT plugin after following thesteps above, here are some suggestions:

  • If Eclipse can not find the remote update site containing the ADT plugin,try changing the remote site URL to use http, rather than https. That is, setthe Location for the remote site to:
  • If you are behind a firewall (such as a corporate firewall), make sure thatyou have properly configured your proxy settings in Eclipse. In Eclipse,you can configure proxy information from the main Eclipse menu inWindow (on Mac OS X, Eclipse) >Preferences > General > NetworkConnections.

If you are still unable to use Eclipse to download the ADT plugin as aremote update site, you can download the ADT zip file to your local machine andmanually install it:

  1. Download the current ADT Plugin zip file from the table below (do not unpack it).
    NamePackageSizeMD5 Checksum
    ADT 9.0.0ADT_9.0.0.zip4433536 bytesbc2757f2a5a11d131390ce547bae154b
  2. Follow steps 1 and 2 in the default install instructions (above).
  3. In the Add Site dialog, click Archive.
  4. Browse and select the downloaded zip file.
  5. Enter a name for the local update site (e.g., 'Android Plugin') in the 'Name' field.
  6. Click OK.
  7. Follow the remaining procedures as listed for default installation above, starting from step 4.

To update your plugin once you've installed using the zip file, you will haveto follow these steps again instead of the default update instructions.

Other install errors

Note that there are features of ADT that require some optionalEclipse components (for example, WST). If you encounter an error wheninstalling ADT, your Eclipse installion might not include these components.For information about how to quickly add the necessary components to yourEclipse installation, see the troubleshooting topicADTInstallation Error: 'requires plug-in org.eclipse.wst.sse.ui'.

Android

For Linux users

If you encounter this error when installing the ADT Plugin for Eclipse:

...then your development machine lacks a suitable Java VM. Installing SunJava 6 will resolve this issue and you can then reinstall the ADTPlugin.

Updating the ADT Plugin

From time to time, a new revision of the ADT Plugin becomes available, withnew features and bug fixes. Generally, when a new revision of ADT is available,you should update to it as soon as convenient.

In some cases, a new revision of ADT will have a dependency on a specificrevision of the Android SDK Tools. If such dependencies exist, you will need toupdate the SDK Tools component of the SDK after installing the new revision ofADT. To update the SDK Tools component, use the Android SDK and AVD Manager, asdescribed in Adding SDK Components.

To learn about new features of each ADT revision and also any dependencies onthe SDK Tools, see the listings in the Revisionssection. To determine the version currently installed, open theEclipse Installed Software window using Help> Software Updates and refer to the version listed for'Android Development Tools'.

Follow the steps below to check whether an update is available and, if so,to install it.

Eclipse 3.5 (Galileo) and 3.6 (Helios)Eclipse 3.4 (Ganymede)
  1. Select Help > Check for Updates.

    If there are no updates available, a dialog will say so and you're done.

  2. If there are updates available, select Android DDMS, Android Development Tools, and Android Hierarchy Viewer, then click Next.
  3. In the Update Details dialog, click Next.
  4. Read and accept the license agreement and then click Finish. This will download and install the latest version of Android DDMS and Android Development Tools.
  5. Restart Eclipse.
  1. Select Help > Software Updates.
  2. Select the Available Software tab.
  3. If there are updates available, select Android DDMS, Android Development Tools, and Android Hierarchy Viewer, then click Update.
  4. In the resulting Available Updates dialog, ensure that each of the listed tools are selected, then click Next.
  5. Read and accept the license agreement and then click Finish. This will download and install the latest version of Android DDMS and Android Development Tools.
  6. Restart Eclipse.

If you encounter problems during the update, remove the existing ADT plugin from Eclipse, thenperform a fresh installation, using the instructions for Installing the ADTPlugin.

In this document

  1. 4. Adding Platforms and Other Components

See also

This page describes how to install the Android SDKand set up your development environment for the first time.

If you encounter any problems during installation, see theTroubleshooting section at the bottom ofthis page.

Updating?

If you already have an Android SDK, use the Android SDK and AVD Manager tool to installupdated tools and new Android platforms into your existing environment. For information about how todo that, see Adding SDK Components

Step 1. Preparing Your Development Computer

Before getting started with the Android SDK, take a moment to confirm thatyour development computer meets the SystemRequirements. In particular, you might need to install the JDK, if you don't have it already.

If you will be developing in Eclipse with the Android DevelopmentTools (ADT) Plugin—the recommended path if you are new toAndroid—make sure that you have a suitable version of Eclipseinstalled on your computer (3.4 or newer is recommended). If you needto install Eclipse, you can download it from this location:

For Eclipse 3.5 or newer, the 'Eclipse Classic' version is recommended. Otherwise, a Java orRCP version of Eclipse is recommended.

Step 2. Downloading the SDK Starter Package

The SDK starter package is not a fulldevelopment environment—it includes only the core SDK Tools, which you canuse to download the rest of the SDK components (such as the latest Android platform).

If you haven't already, get the latest version of the SDK starter package from the SDK download page.

If you downloaded a .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>.

If you downloaded the Windows installer (.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).

Make a note of the name and location of the SDK directory on your system—you will need torefer to the SDK directory later, when setting up the ADT plugin and when usingthe SDK tools from command line.

Step 3. Installing the ADT Plugin for Eclipse

Android offers a custom plugin for the Eclipse IDE, called AndroidDevelopment Tools (ADT), that is designed to give you a powerful, integratedenvironment in which to build Android applications. It extends the capabilitesof Eclipse to let you quickly set up new Android projects, create an applicationUI, debug your applicationsusing the Android SDK tools, and even export signed (or unsigned) APKs in orderto distribute your application. In general, developing in Eclipse with ADT is ahighly recommended approach and is the fastest way to get started with Android.

If you'd like to use ADT for developing Android applications, install it now.Read Installing the ADT Plugin forstep-by-step installation instructions, then return here to continue thelast step in setting up your Android SDK.

If you prefer to work in a different IDE, you do not need toinstall Eclipse or ADT, instead, you can directly use the SDK tools to build anddebug your application. The developer guide has more information about Developing in Other IDEs.

Step 4. Adding Platforms and Other Components

The last step in setting up your SDK is using the Android SDK and AVD Manager (atool included in the SDK starter package) to downloadessential SDK components into your development environment.

The SDK uses a modular structure that separates the major parts of the SDK—Android platformversions, add-ons, tools, samples, and documentation—into a set of separately installablecomponents. The SDK starter package, which you've already downloaded, includes only a singlecomponent: the latest version of the SDK Tools. To develop an Androidapplication, you also need to download at least one Android platform and the SDK Platform-tools(tools that the latest platform depend upon). However, downloadingadditional components is highly recommended.

If you used the Windows installer, when you complete the installation wizard, it will launch theAndroid SDK and AVD Manager with a default set of platforms and other components selectedfor you to install. Simply click Install to accept the recommended set ofcomponents and install them. You can then skip to Step 5, but werecommend you first read the section about the Available Components tobetter understand the components available from the Android SDK and AVD Manager.

You can launch the Android SDK and AVD Manager in one of the following ways:

  • From within Eclipse, select Window > Android SDK and AVD Manager.
  • On Windows, double-click the SDK Manager.ext file at the root of the AndroidSDK directory.
  • On Mac or Linux, open a terminal and navigate to the tools/ directory in theAndroid SDK, then execute:

To download components, use the graphical UI of the Android SDK and AVDManager, shown in Figure 1, to browse the SDK repository and select new or updatedcomponents. The Android SDK and AVD Manager will install the selected components inyour SDK environment. For information about which components you should download, see the followingsection about Recommended Components.

Install Eclipse On Mac

Eclipse android mac os

Figure 1. The Android SDK and AVD Manager'sAvailable Packages panel, which shows the SDK components that areavailable for you to download into your environment.

Available Components

By default, there are two repositories of components for your SDK: AndroidRepository and Third party Add-ons.

The Android Repository offers these types of components:

  • SDK Tools (pre-installed in the Android SDK starterpackage) — Contains tools for debuggingand testing your application and other utility tools. You can access thesein the <sdk>/tools/ directory of your SDK and read more about them in the Tools section of the developer guide.
  • SDK Platform-tools — Contains tools that are required to develop anddebug your application, but which are developed alongside the Android platform in order to supportthe latest features. These tools are typically updated only when a new platform becomesavailable. You can access thesein the <sdk>/platform-tools/ directory. Read more about them inthe Tools section of the developer guide.
  • Android platforms — An SDK platform isavailable for every production Android platform deployable to Android-powereddevices. Each platform component includes a fully compliant Android library andsystem image, sample code, emulator skins, and any version specific tools. Fordetailed information about each platform, see the overview documents availableunder the section 'Downloadable SDK Components,' at left.
  • USB Driver for Windows (Windows only) — Contains driver filesthat you can install on your Windows computer, so that you can run and debugyour applications on an actual device. You do not need the USB driver unlessyou plan to debug your application on an actual Android-powered device. If youdevelop on Mac OS X or Linux, you do not need a special driver to debugyour application on an Android-powered device. (See Developing on a Device for more informationabout developing on a real device.)
  • Samples — Contains the sample code and apps availablefor each Android development platform. If you are just getting started withAndroid development, make sure to download the samples to your SDK.
  • Documentation — Contains a local copy of the latestmultiversion documentation for the Android framework API.

The Third party Add-ons provide components that allow you to create a developmentenvironment using a specific Android external library (such as the Google Maps library) or acustomized (but fully compliant) Android system image. You can add additional Add-on repositories,by clicking Add Add-on Site.

Recommended Components

The SDK repository contains a range of components that you can download.Use the table below to determine which components you need, based on whether youwant to set up a basic, recommended, or full development environment:

EnvironmentSDK ComponentComments
BasicSDK ToolsIf 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-toolsThis 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 platformYou need to download at least one platform into your environment, so thatyou will be able to compile your application and set up an Android VirtualDevice (AVD) to run it on (in the emulator). To start with, just download thelatest version of the platform. Later, if you plan to publish your application,you will want to download other platforms as well, so that you can test yourapplication on the full range of Android platform versions that your application supports.
+
Recommended
(plus Basic)
DocumentationThe Documentation component is useful because it lets you work offline andalso look up API reference information from inside Eclipse.
SamplesThe 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 DriverThe 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 APIsThe 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 PlatformsIf 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.

Once you've installed at least the basic configuration of SDK components, you're ready to startdeveloping Android apps. The next section describes the contents of the Android SDK to familiarizeyou with the components you've just installed.

For more information about using the Android SDK and AVD Manager, see the Adding SDK Components document.

Step 5. Exploring the SDK (Optional)

Once you've installed the SDK and downloaded the platforms, documentation,and add-ons that you need, we suggest that you open the SDK directory and take a look at what'sinside.

The table below describes the full SDK directory contents, with componentsinstalled.

NameDescription
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.jarThe 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.txtA 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.exeWindows SDK only. A shortcut that launches the Android SDK and AVDManager tool, which you use to add components to your SDK.

Optionally, you might want to add the location of the SDK's tools/ andplatform-tools to your PATH environment variable, to provide easyaccess to the tools.

How to update your PATH

Adding both 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:

  • On Windows, right-click on My Computer, and select Properties. Under the Advanced tab, hit the Environment Variables button, and in the dialog that comes up, double-click on Path (under System Variables). Add the full path to the tools/ and platform-tools/ directories to the path.
  • On Linux, edit your ~/.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:
  • On a Mac OS X, look in your home directory for .bash_profile and proceed as for Linux. You can create the .bash_profile if you don't already have one.

Next Steps

Once you have completed installation, you are ready tobegin developing applications. Here are a few ways you can get started:

Set up the Hello World application

  • If you have just installed the SDK for the first time, go to the Hello World tutorial. The tutorial takes you step-by-step through the process of setting up your first Android project, including setting up an Android Virtual Device (AVD) on which to run the application.

Following the Hello World tutorial is an essentialfirst step in getting started with Android development.

Learn about Android

  • Take a look at the Dev Guide and the types of information it provides
  • Read an introduction to Android as a platform in What is Android?
  • Learn about the Android framework and how applications run on it in Application Fundamentals
  • Take a look at the Android framework API specification in the Reference tab

Explore the development tools

  • Get an overview of the development tools that are available to you
  • Read how to develop in Eclipse/ADT or in other IDEs
  • Read Developing on a Device to set up anAndroid-powered device to run and test your application.

Follow the Notepad tutorial

  • The Notepad Tutorial shows you how to build a full Android application and provides helpful commentary on the Android system and API. The Notepad tutorial helps you bring together the important design and architectural concepts in a moderately complex application.

Following the Notepad tutorial is an excellentsecond step in getting started with Android development.

Explore some code

  • The Android SDK includes sample code and applications for each platformversion. You can browse the samples in the Resources tab or download theminto your SDK using the Android SDK and AVD Manager. Once you've downloaded thesamples, you'll find them in<sdk>/samples/<platform>/.

Visit the Android developer groups

  • Take a look at the Community pages to see a list of Android developers groups. In particular, you might want to look at the Android Developers group to get a sense for what the Android developer community is like.

Troubleshooting

Ubuntu Linux Notes

  • If you need help installing and configuring Java on your development machine, you might find these resources helpful:
  • Here are the steps to install Java and Eclipse, prior to installing the Android SDK and ADT Plugin.
    1. If you are running a 64-bit distribution on your development machine, you need to install the ia32-libs package using apt-get::
    2. Next, install Java:
    3. The Ubuntu package manager does not currently offer an Eclipse 3.3 version for download, so we recommend that you download Eclipse from eclipse.org (http://www.eclipse.org/ downloads/). A Java or RCP version of Eclipse is recommended.
    4. Follow the steps given in previous sections to install the SDK and the ADT plugin.

Other Linux Notes

  • If JDK is already installed on your development computer, please take a moment to make sure that it meets the version requirements listed in the System Requirements. 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.