In this document
- Install Android Sdk For Mac Os 10.13
- Android Sdk
- Install Android Sdk Windows 7
- Android Sdk Mac Os
- Android Sdk For Mac
Aug 25, 2020 Chrome OS. Follow these steps to install Android Studio on Chrome OS: If you haven't already done so, install Linux for Chrome OS. Open the Files app and locate the DEB package you downloaded in the Downloads folder under My files. Right-click the DEB package and select Install with Linux (Beta).
- 4. Adding Platforms and Other Components
See also
- Berkeley Electronic Press Selected Works.
- On Windows, Android is required for Mobile SDK development. On Mac OS X, if you don’t intend to support the Android platform, you can skip this section. You can always come back to it later if you change your mind.
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:
“Many thanks to AMS for going the extra mile and providing a friendly, consistent and all around fantastic service. Komatsu pc 220 6 excavator parts manual. Geoff. Jason Duffin. “They have provided me with quality parts and service for three years without any part failures.and always at the lowest market price.
- 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.
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:
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.
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.
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
How to update your PATHtools/
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:- 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/
andplatform-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 thetools/
andplatform-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.
Install Android Sdk For Mac Os 10.13
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 Email extractor 9 for macos.
- 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.
- If you are running a 64-bit distribution on your development machine, you need to install the
ia32-libs
package usingapt-get:
: - Next, install Java:
- 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.
- Follow the steps given in previous sections to install the SDK and the ADT plugin.
- If you are running a 64-bit distribution on your development machine, you need to install the
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.
Android Sdk
I’ve got at least two concepts for Android apps running around in my head, notebooks & text files at the moment. Being a web developer for some years now, and having developed a Windows app or two, I figured I would be able to start prototyping these concepts for Android without too much hassle.
So far, the hardest and most frustrating part of this process has been installing the SDK. Part of the hassle I’ve had is that most online resources only explain the steps required for users of Eclipse (which automates a bit of it for you). The most frustrating bit was forum answers which simply told you to install Eclipse to fix whatever code-related problem the asker was having.
I want to avoid Eclipse, for two main reasons:
Download and install the Camera Raw plug-in. Note: If you still haven't been able to successfully update the Camera Raw plug-in for currently supported versions of Adobe applications, use the Camera Raw 12.4 installer below. For older Adobe applications, substitute with the Camera Raw 10.5 installer below. The way it works is you use FileOpen in photoshop cs6, select a camera raw file from your camera and then the file opens in the camera raw dialog. Photoshop cs6 doesn't have FilterCamera Raw Filter. That's only in photoshop cc versions. Or use Bridge CS6, right click on the camera raw file and select Open in Camera Raw. Camera raw download for cc cs6 Once it import city converts it to an 8-bit image.So that basically reduces the amount of information that is in there but we all know that inside Photoshop,you can then upgrade it back up to 16 bit off of certain projects. Adobe Camera Raw, which lets you import and enhance raw images, has been a must-have tool for professional photographers right since it was first released in 2003. Applications that support Adobe Camera Raw include Photoshop, Photoshop Elements, After Effects, and Bridge. Additionally, Adobe Lightroom is built upon the same powerful raw image. For Mac: Adobe Camera Raw and DNG Converter for Macintosh for Windows: Adobe Camera Raw and DNG Converter for Win Please contact us if you have any questions or need support. Camera raw for cs6 for mac.
- Eclipse is nasty to use, convoluted resource-hog. It’s slower than a wet week on my Mac, plus it hasn’t functioned as it should when I’ve attempted to use it in the past (and man, that interface is yuck).
- See reason 1.
The other hassles I’ve had is with the lack of accurate documentation. The resources I’ve been reading have overlooked some vital steps in the process of installing the SDK and getting your first app up and running.
I’m going to explain the steps I took to install the latest version of the Android SDK on my Mac OS X 10.7, plus the extra steps needed to get my first app working. These instructions are based on the official developer.android.com instructions on “Building Your First App“, but instead of any IDE I’ll be using the command line and TextWrangler.
The first step is to download the SDK. I opted to download the non-bundle version (under the heading “Use an existing IDE”). Open this and extract it. I chose to locate it in the directory /Android/ (in the root of my main hard drive). I will be referring to this path from now on. If you want to save it elsewhere, please translate that path in your head.
Next, go to /Android/tools/ and run the android file. It will open up a Terminal window, and then launch a GUI. This is the Android SDK Manager, and it is how you obtain the latest copy of the SDK, as well as extra tools and libraries you may need. I opted to download the entire “Tools” folder, the entire folder of the latest SDK (Android 4.2 – SDK 17), and the Android Support Library (under “Extras”).
The next step is to install Apache ANT. ANT is used to automate the build process, and is necessary for most users. You could build manually, but the ANT tool will save you a lot of time. This step was left out of the guides I read, and caused some confusion when it came time to build. Download the binary, and extract it. I then created the folder /Android/ant/ and copied the entire bin and lib folders into there.
The next step is to add ANT’s bin folder to PATH. This is a system-wide variable used by the operating system to allow you to directly open the contents of a folder without needing to specify it’s full folder path. As an example, I could type /Android/ant/bin/ant into the command line, or I could just type ant – they both do the same thing.
On Mac OS X, you add a folder to the PATH variable by running this command in Terminal:
- PATH=$PATH:/Android/ant/
The manual also says you should add the environmental variable ANT_HOME and set it to the main ANT folder (/Android/ant/), but I didn’t do this and haven’t had any issues yet.
Check you’ve installed it correctly by typing ant into Terminal and looking for this output: “Buildfile: build.xml does not exist! Build failed”
You also need to add the /Android/platform-tools/ and /Android/tools/ folders to the path variable. Execute these commands one at a time:
Install Android Sdk Windows 7
- PATH=$PATH:/Android/platform-tools/
- PATH=$PATH:/Android/tools/
You are now ready to create, build, and run a bare bones app. The official instructions are fine here, so read the pages “Creating an Android Project“, “Running and Application“, and “Building a Simple User Interface“.
Android Sdk Mac Os
Tip about emulators: If your computer isn’t loaded up with a whole heap of CPU power, try create a virtual Android device with a smaller resolution and DPI. I’m running a 5.1″ WVGA 480 x 800 device on my several year old MacBook just fine, where as the higher res and DPI devices would take a long, long time to load and sometimes crash.
Tip about Reinstalling: The process where you install an app into the emulator doesn’t like it if you already have an older copy of that app installed. I have been manually deleting it each time by holding down the mouse on the icon and dragging it towards the “Uninstall” icon which appears. There is probably a way to automate this, but I haven’t found it yet.
The last page where you create another Activity lacks a few instructions. You need to manually add some imports to the top of your Java files before they will compile. These are listed in the instructions, except for one: import android.support.v4.app.NavUtils;
This last one tripped me up a bit, as I hadn’t installed the Android Support Library at the start. As you did, you shouldn’t have issues with this triggering a compile error.
By now you should have be able to run your app in the emulator and create a new view. For me, this whole process was incredibly painful and took well over an hour to figure out. Writing it all down, it does seem a lot easier than it felt at the time, but I suppose hindsight is 20/20. With any luck, my publication of these tips has helped you.
Android Sdk For Mac
Also, stay tuned for information about our upcoming Android products.