Setup Android Emulator on Mac OS X. The purpose of this section is to guide you to create in your development environment an Android emulator. Android emulators are managed through a UI called AVD Manager. AVD Manager has a nice interface when started from Android Studio. Start Android Studio app, then create a blank project.
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.
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
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.
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.
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.
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:
SDK Manager.ext
file at the root of the AndroidSDK directory.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.
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.
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/
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.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.
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:
Download for MacOS - server 1 - Free. Download and Install iMovie. Download for PC - server 1 - MAC: Download for MacOS - server 1. You could either first visit the Mac store or Windows AppStore and search for the app OR you can easily use any of the download links we provided above under the 'Download and Install' header section to. Imovie mac free download for windows. From the first scene to the last. Whether you’re using a Mac or an iOS device. Imovie mac free download - Bigasoft iMovie Converter, Apple iMovie, iMovie Updater, and many more programs.
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. |
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.
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.
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. |
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.
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:
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. 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
Following the Hello World tutorial is an essentialfirst step in getting started with Android development.
Learn about Android
Explore the development tools
Follow the Notepad tutorial
Following the Notepad tutorial is an excellentsecond step in getting started with Android development.
Explore some code
<sdk>/samples/<platform>/
. Visit the Android developer groups
ia32-libs
package using apt-get:
: