- Navigation
- Main Page
- Community portal
- Current events
- Recent changes
- Random page
- Help
- Eclipse Sdk For Mac Download
- Eclipse Ide For Mac Os X El Capitan
- Eclipse Sdk For Mac Desktop
- Eclipse Sdk For Mac
Eclipse 4.16.0 Release Build: 4.16. This page provides access to the various deliverables of Eclipse Platform build along with its logs and tests. New and Noteworthy Acknowledgments Eclipse Project 4.16 Readme Eclipse Project Plan Logs and Test Links. View the logs for the current build. View the integration and unit test results for the. Eclipse SDK for Mac. Free Eclipse Foundation Mac OS X 10.6/10.7/10.8/10.9 Version 4.4 Full Specs. Visit Site External Download Site. Clicking on the Download Now (Visit Site) button above.
- Toolbox
- Page information
- Permanent link
- Printable version
- Special pages
- Related changes
- What links here
- The Eclipse software development kit (SDK), which includes the Java development tools, is meant for Java developers. Users can extend its abilities by installing plug-ins written for the Eclipse Platform, such as development toolkits for other programming languages, and can write and contribute their own plug-in.
- Eclipse 4.17.0 Release Build: 4.17. This page provides access to the various deliverables of Eclipse Platform build along with its logs and tests. New and Noteworthy Acknowledgments Eclipse Project 4.17 Readme Eclipse Project Plan Logs and Test Links. View the logs for the current build. View the integration and unit test results for the.
Powered by Oomph
This page provides step-by-step instructions for how to provision a dedicated development environment for the complete set of projects that comprise the Eclipse Platform's SDK, i.e., the projects used to build the downloads of the Eclipse Platform Project.The provisioning process is entirely automated, except for course from user input to choose configurable options, e.g., where in the file system to place the installation, but even for these, defaults are provided.
If you encounter problems or have suggestions for improvements, please use Bug 536533 for that purpose.
Launch the Eclipse Installer
If you don't already have the Eclipse Installer on your system, download the installer that is appropriate for your operating system's architecture. For Windows, the installer is distributed as an executable. It will start without a JRE or JDK installed, but if you don't have at Java 8 installed, it will guide you to install that. For Mac and Linux, you must unpack the installer before you can run the application. In all cases, you must install a JRE or JDK (currently at least Java 8) before you can successfully use the installer, and of course the installation you will create needs it too. Please look at these instructions if you need further details. And note that on Mac you must install a JDK, not merely a JRE.
The latest version if the installer can be registered to automatically launch when clicking on a hyperlink.This can be used to further automate the initial steps in this tutorial.As such, you can open this link in a new tab to configure the installer to launch automatically.
Now launch the installer application.Unless you just downloaded a new installer, the one you have probably needs to be updated. In simple mode, you'll see a '!' indicator on the menu button in the upper right corner; the menu will have an update item to start an update:
In advanced mode, the right-most toolbar button at the bottom can be pressed to start an update.
Note that the installer will by default use a shared bundle pool for creating installations. This defaults to the .p2 folder in the home folder.If the file system for the home folder is relatively small, you can change the default location using the Bundle Pools menu option in simple mode, or the right-most toolbar button in the Bundle Pool section in advanced mode, as seen in each of the corresponding screen captures in the following section.
Note also that you can choose which Java VM is used by the installation you are about to create.The installer will generally detected the JREs and JDKs installed on your system, choosing an appropriate default, and remembering it for the next time you use the installer.But failing that, the installer will stay on the product page and you must use the tool button to locate a Java VM that is suitable for the installation being created.
Apply the Platform SDK Configuration
We will use a so-called Oomph configuration to automate the selection of the product and projects to provision.
![Sdk Sdk](/uploads/1/1/7/8/117888688/164310213.jpg)
If you've registered the installer to launch automatically for links with scheme
eclipse+install
as described in the previous section,you can open this link in a new tab and click the Launch...
button on that page.Doing so automates the following equivalent alternative steps.Drag and drop the Platform SDK Configuration link on the title area of the installer. If the installer is in simple mode, it will ask to Switch to Advanced Mode; confirm that prompt. When the configuration is successfully applied, the installer will be in advanced mode and will automatically turn to the Variables page.
NOTE: Drag and drop does not work reliable on Linux, please use the next approach if you are also facing this.
As an alternative to drag-and-drop, you can copy the Platform SDK Configuration link, and apply it to the installer. In simple mode, this is done via the menu action; this action will appear in the menu only if the clipboard contains a valid configuration:
In advanced mode, this is done via the left-most button in the toolbar; this button will appear in the toolbar only if the clipboard contains a valid configuration:
Review the Variables
After applying the configuration, you'll be on the Variable page of the install wizard's advanced mode:
Of course you can use the Back button to review the selections that were made on the previous two pages, i.e., on the Product page and the Projects page.If this is the first time you've used the installer, there will be large number of variables, but all have suitable defaults.Of particular note, you may wish to change the 'Root install folder' to a different location, it defaults to your home folder, keeping in mind that this location will use a significant amount of disk space.The three so-called location rule variables, for this tutorial's example scenario, will create the installation in D:sandboxUSER-HOME-CLEANplatform-sdkeclipse (Eclipse.app on Mac), the workspace in D:sandboxUSER-HOME-CLEANplatform-sdkws, and all the Git clones under D:sandboxUSER-HOME-CLEANplatform-sdkgit.
The long list of variables is mostly the result of the different choices available for the URI used to clone each Git repository.Currently there are six choices, but that may soon be reduced to three if the Eclipse Foundation eliminates the non-Gerrit servers.All the clone URIs for the Platform SDK Configuration's repositories default to anonymous, read-only Gerrit access.If you are a committer, or a contributor with a Gerrit account, you will want to change each of these URIs to a form that allows read-write access.If you do not have a Gerrit account, you should get one immediately!When you select the SSH (read-write, Gerrit) choice,a new variable prompt, Eclipse Git/Gerrit user ID, will appear at the very bottom.Here you should enter your Eclipse account ID, e.g., for me, emerks.
Note that if you find it very painful to change each of the many URIs in the dialog,you'll only ever have to do this once,because the installer will remember this choice and will no longer display the variable, unless you check Show all variables, in which case you can change the choice you made previously.In addition, the latest version of the installer has simplified these steps.There is now a prompted variable that you can exploit to change all the prompted clone URIs to use your preferred style of authentication.
It still defaults to anonymous, but ideally you will get an Eclipse account and specify ssh.
Press the Next button.
Confirm the Tasks
After pressing the Next button, you'll be on the Confirmation page:
Here you can see all the setup tasks that must be performed before the installation can be launched.You can select each task to review its nested element structure and its properties; you can also select a nested element to review its properties. The most important task is the so-called P2 Director task, it specifies the requirements of what needs to be installed and the update sites from which to install them.Note in particular that the Platform SDK Configuration will install using the Eclipse Platform Project's most recent Integration build.
Press the Finish button and accept the license that is likely associated with the features you are about to install.
Monitor the Progress
After pressing the Finish button, you'll be on the Progress page where you can review the progress of the tasks being performed.
After the P2 Director task's repositories are loaded, when it's time to download the artifacts to install, you'll likely be prompted to accept all the specific licenses.Note that this confirmation dialog has a 'Remember accepted licenses' check box,be sure to click it so that you'll never be asked to review these licenses again.
If this is the first time you've created an installation using the installer you may wish to go for a quick coffee break while the artifacts download.Be sure the Launch automatically check box is checked so that the installation will automatically be launched upon completion (in case your coffee break turned out to be longer than expected).Unfortunately the platform's integration build is not mirrored, and there are frequent new builds, so this process can take a while.Also the download.eclipse.org server sometimes gets overloaded, so if there is a timeout failure, you can press the Back button, followed by the Finish button,to resume downloading.
Provision the Workspace
When you get back from your coffee break, the installation will have launched and the setup engine will be working hard to provision its workspace.Note that there will be an animated button at the bottom of the window, near the right-hand side.You can press that control to bring up the Eclipse Updater dialog, so you can review the progress of provisioning the workspace:
There's nothing else you need to do.Cloning all these repositories will definitely take some time, some are very large, and the update sites might be slow, so you can go on your lunch break now because this could take 90 minutes.
Review the Result
The end result is a workspace like this:
All the projects are organized into sensible working sets. All the Git clones are Gerrit enabled for easy contribution.And the setup even created a feature-based 'Runtime Workspace' launcher and added it to the favorites list, so it's already in the menu.Now you can make changes to any project to fix bugs or to add new features and you can launch a runtime instance to test any of your changes.
Note that PDE's target platform for this workspace also contains binary equivalents of all projects in the workspace,so you can close any combination of projects to improve build time without causing compile errors.
Update the Installation and Workspace
Suppose you've performed these steps a few weeks ago and would like to update the installation and workspace to the latest and greatest state.Of course you can easily select all Git repositories in the Git Repositories view and do a Pull.But you can also easily update the installation and the workspace using the tool bar contributions provided by Oomph.The Perform Setup Tasks tool bar menu button is useful for this purpose:
It launches the Eclipse Updater.
The P2 Director task will update the installation with the latest Eclipse Platform integration build.The Modular Target task will update the target platform with the latest dependencies;it will even import new projects if there are any.The API baseline changes rarely, i.e., only between releases, so you won't need to perform the tasks for updating the API baseline nearly as frequently.Note that you can selectively enable tasks.In the above I have only enabled the first and the last task.It's very convenient to enable a single task with a double-click; all other tasks will be unchecked and only the selected task will be checked.Hitting Finish will perform the enabled tasks.By default the dialog will minimize to the status bar, where it will be visible as an animated icon.It's a non-modal dialog, so you can make it visible by clicking the status icon.The status icon will eventually disappear if the tasks perform successfully; if not, you'll need to open the dialog to see what's going on.For example, when the installation is updated, you'll need to restart the IDE, which you can do by pressing the Finish button of the wizard.
You may also wish to view the setup definitions provided for the various projects.The Open setup menu button is useful for this purpose:
Please refer to the authoring guide if you're interested in the details.Many of the project setups are located within the Git clones themselves, so you can contribute changes to them, and can test the impact in the running installation;the long term goal is for each project to maintain its own project setup, but we're not quite there.In any case, you might get some good ideas for how best to author an Oomph setup for your own projects!
Retrieved from 'https://wiki.eclipse.org/index.php?title=Eclipse_Platform_SDK_Provisioning&oldid=437051'
In this document
- 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.
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
Eclipse Sdk For Mac Download
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.
Eclipse Ide For Mac Os X El Capitan
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.
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.
Eclipse Sdk For Mac Desktop
Troubleshooting
Eclipse Sdk For Mac
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.