Adt For Eclipse Mac Os

Posted on 23-04-2021 by admin

SDK Tools is a downloadable component for the Android SDK. It includes thecomplete set of development and debugging tools for the Android SDK.

Android Eclipse Adt
Download Eclipse Adt For Android
Adt For Eclipse Mac Os High Sierra
Adt For Eclipse Mac Os Versions

If you are new to the Android SDK, the SDK starter package installs thelatest revision of the SDK Tools in the <sdk>/tools directory.

Android Eclipse Adt

Setting Up the ADT Bundle. It extends the capabilities of Eclipse to let you quickly set up new Android projects, build an app UI, debug. Eclipse menu in Window (on Mac OS X, Eclipse) Preferences General Network Connections. If you are still unable to use Eclipse to. In general, developing in Eclipse with ADT is a highly 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 for step-by-step installation instructions. If you develop on Mac OS X or Linux, you do not need a.

If you are already using the SDK and you want to update to the latest versionof the SDK Tools, use the Android SDK and AVD Manager to get theupdate, rather than downloading a new SDK starter package. For more informationabout how to update, see Updating SDKComponents.

Revisions

The sections below provide notes about successive releases ofthe SDK Tools, as denoted by revision number. To determine what revision of the SDKTools you are using, refer to the 'Installed Packages' listing in the Android SDKand AVD Manager.

SDK Tools, Revision 9(January 2011)

Dependencies:

If you are developing in Eclipse with ADT, note that the SDK Tools r9 isdesigned for use with ADT 9.0.0 and later. After installing SDK Tools r9, wehighly recommend updating your ADT Plugin to 9.0.0.

If you are developing outside Eclipse, you must have ApacheAnt 1.8 or later.

Upgrading to SDK Tools r9:

If you are upgrading to SDK Tools r9 from SDK Tools r7 or earlier, the default installed locationfor the adb tool has changed from <SDK>/tools/adb to<SDK>/platform-tools/adb. This means that you shouldadd the new location to your PATH and modify any custom build scripts toreference the new location. Copying the adb executable from the newlocation to the old is not recommended, since subsequent updates to the SDKTools will delete the file.

General notes:

The default ProGuard configuration, proguard.cfg, now ignores the following classes:
- classes that extend Preference
- classes that extend BackupAgentHelper
Ant lib rules now allow you to override java.encoding, java.source, and java.target properties.
The default encoding for the javac Ant task is now UTF-8.
The LogCat view in DDMS now properly displays UTF-8 characters.
The SDK Manager is more reliable on Windows. For details on the improvements, see the Android Tools Project Site.
Early look at the new snapshot feature: To improve startup time for the emulator, you canenable snapshots for the system state. The emulator will then restore to the state when it lastclosed almost instantly. Note: The snapshot feature is still under activedevelopment and might not always perform as expected.
Fixed the missing JAR file error that prevented draw9patch from running.
Fixed the Windows launch scripts hierarchyviewer and ddms to support the new location of adb.
Known issues with emulator performance: Because the Android emulator must simulate the ARMinstruction set architecture on your computer, emulator performance is slow. We're working hard toresolve the performance issues and it will improve in future releases.

SDK Tools, Revision 8(December 2010)

Dependencies:

If you are developing in Eclipse with ADT, note that SDK Tools r8 isdesigned for use with ADT 8.0.0 and later. After installing SDK Tools r8, wehighly recommend updating your ADT Plugin to 8.0.0.

If you are developing outside Eclipse, you must have ApacheAnt 1.8 or later.

Also note that SDK Tools r8 requires a new SDK component calledPlatform-tools. The new Platform-tools component lets all SDK platforms(Android 2.1, Android 2.2, and so on) use the same (latest) version of buildtools such as adb, aapt, aidl, anddx. To download the Platform-tools component, use the Android SDKManager, as described in Adding SDKComponents

Upgrading from SDK Tools r7:

If you are upgrading to SDK Tools r8 from an earlier version, note that thethe default installed location for the adb tool has changed from<SDK>/tools/adb to<SDK>/platform-tools/adb. This means that you shouldadd the new location to your PATH and modify any custom build scripts toreference the new location. Copying the adb executable from the newlocation to the old is not recommended, since subsequent updates to the SDKTools will delete the file.

General notes:

All SDK platforms now support Library Projects.
Support for a true debug build. Developers no longer need to add theandroid:debuggable attribute to the<application> tag in the manifest — the build tools addthe attribute automatically. In Eclipse/ADT, all incremental builds are assumedto be debug builds, so the tools insert android:debuggable='true'.When exporting a signed release build, the tools do not add the attribute. InAnt, a ant debug command automatically inserts theandroid:debuggable='true' attribute, while ant releasedoes not. If android:debuggable='true' is manually set, thenant release will actually do a debug build, rather than a releasebuild.
Automatic ProGuard support in release builds. Developers generate a ProGuardconfiguration file using the android tool — the build toolsthen automatically run ProGuard against the project sources during the build.For more information, see the ProGuarddocumentation.
New overridable Ant javac properties: java.encoding,java.source, and java.target (default values are'ascii', '1.5', and '1.5', respectively).
New UI for the HierarchyViewer tool.

SDK Tools, Revision 7

(September 2010)

Dependencies:

If you are developing in Eclipse with ADT, note that SDK Tools r7 isdesigned for use with ADT 0.9.8 and later. After installing SDK Tools r7, wehighly recommend updating your ADT Plugin to 0.9.8.

General notes:

Added support for library projects that depend on other library projects.
Adds support for aidl files in library projects.
Adds support for extension targets in Ant build to perform tasks between thenormal tasks: -pre-build, -pre-compile, and-post-compile.
Adds support for 'headless' SDK update. See android -h update sdkfor more information.
Fixes location control in DDMS to work in any locale not using '.' as adecimal point.

SDK Tools, Revision 6(May 2010)

Dependencies:

If you are developing in Eclipse with ADT, note that SDK Tools r6 isdesigned for use with ADT 0.9.7 and later. After installing SDK Tools r6, wehighly recommend updating your ADT Plugin to 0.9.7.

Library projects:

The SDK Tools now support 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 Developing in Other IDEs document.

If you are developing in Eclipse, ADT 0.9.7provides the equivalent library project support.

SDK Tools, Revision 5(March 2010)

Dependencies:

If you are developing in Eclipse with ADT, note that SDK Tools r5 isdesigned for use with ADT 0.9.6 and later. After installing SDK Tools r5, wehighly recommend updating your ADT Plugin to 0.9.6.
For Mac OS platforms, OS X 10.4.x (Tiger) is no longerofficially supported.

SDK and AVD Manager:

Fixes SSL download for the standalone version of the SDK Updater.
Fixes issue with 64-bit JVM on Windows.
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.
Settings are now automatically saved, no need to click 'Apply'.

Emulator:

Emulator now requires SD card to be 9MB or more.

Layoutopt:

Fixes layoutopt.bat to execute correctly on Windows.

SDK Tools, Revision 4(December 2009)

Dependencies:

SDK Tools r4 is compatible with ADT 0.9.5 and later, but notcompatible with earlier versions. If you are developing in Eclipse with ADT, youmust update your ADT plugin to version 0.9.5 or higher if youinstall SDK Tools r4 in your SDK.

General notes:

Launcher script now forces GDK_NATIVE_WINDOW=true (linux only), to fix a compatibility issue between GTK and SWT.

Android SDK and AVD Manager:

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.
No longer forces the use of Java 1.5 on Mac OS X.

Emulator:

Download Eclipse Adt For Android

No longer limits the size of the system partition.

Ant build tools:

.apk packaging now properly ignores vi swap files as well as hidden files.

SDK Tools, Revision 3(October 2009)

Dependencies:

SDK Tools r3 is compatible with ADT 0.9.4 and later, but notcompatible with earlier versions. If you are developing in Eclipse with ADT, youmust update your ADT plugin to version 0.9.4 or higher if youinstall SDK Tools r3 in your SDK.

Android tool:

Adds new android create test-project and android updatetest-project commands to allow for greater flexibility in the location of themain and test projects.

DDMS:

Adds a button to dump HPROF file for running appplications (app must be ableto write to the sdcard).
Button to start/stop profiling of a running application (app must be able towrite to the sdcard). Upon stop, Traceview will automatically be launched todisplay the trace.
Fixed DDMS, Traceview, and the AVD Mananger/SDK Updater to run on Mac OS X10.6.
Fixed screenshot support for devices running 32-bit framebuffer.

Android SDK and AVD Manager:

Provides a new UI that lets you set options for controllingthe emulator skin, screen size/density, and scale factor used when launching an AVD.
Provides improved AVD creation UI, which lets you customize the hardwareproperties of your AVDs.
Now enforces dependencies between platforms and tools components, andbetween SDK add-ons and platforms.

Layoutopt, a new tool for optimizing layouts:

The SDK Tools r3 package includes layoutopt, a new command-line tool that helps you optimize your layout hierarchies. When run against your layout files, the tool analyzes their hierarchies and notifies you of inefficiencies and other potential issues. The tool also provides simple solutions for the issues it finds. For usage, see layoutopt.

There are times when we need to make certain configurational changes for the eclipse, one of such file is eclipse.ini (informal standard for configuration). If you have worked with Eclipse on Windows Operating System then you would see the file inside eclipse folder, but I was not able to locate it on Mac OS X,

The ini file is bundled within the executable eclipse file (icon), to access it, Right-click on Eclipse icon, Show Package Contents, now you would be able to see a directory: Contents, Click on it and you would see MacOS directory, get in it, and you would be able to see the eclipse.ini file.

eclipse.ini