|
|
|
|
@@ -64,6 +64,70 @@ padding: .25em 1em;
|
|
|
|
|
<div class="toggleable opened">
|
|
|
|
|
<a href="#" onclick="return toggleDiv(this)">
|
|
|
|
|
<img src="{@docRoot}assets/images/triangle-opened.png" class="toggle-img" height="9px" width="9px" />
|
|
|
|
|
SDK Tools, Revision 8</a> <em>(December 2010)</em>
|
|
|
|
|
<div class="toggleme">
|
|
|
|
|
|
|
|
|
|
<dl>
|
|
|
|
|
<dt>Dependencies:</dt>
|
|
|
|
|
<dd>
|
|
|
|
|
<p>If you are developing in Eclipse with ADT, note that SDK Tools r8 is
|
|
|
|
|
designed for use with ADT 8.0.0 and later. After installing SDK Tools r8, we
|
|
|
|
|
highly recommend updating your ADT Plugin to 8.0.0.</p>
|
|
|
|
|
|
|
|
|
|
<p>Also note that SDK Tools r8 requires a new SDK component called
|
|
|
|
|
<em>Platform-tools</em>. The new Platform-tools component lets all SDK platforms
|
|
|
|
|
(Android 2.1, Android 2.2, and so on) use the same (latest) version of build
|
|
|
|
|
tools such as <code>adb</code>, <code>aapt</code>, <code>aidl</code>, and
|
|
|
|
|
<code>dx</code>. To download the Platform-tools component, use the Android SDK
|
|
|
|
|
Manager, as described in <a href="adding-components.html">Adding SDK
|
|
|
|
|
Components</a></p>
|
|
|
|
|
|
|
|
|
|
<dt>Upgrading from SDK Tools r7:</dt>
|
|
|
|
|
<dd>
|
|
|
|
|
<p>If you are upgrading to SDK Tools r8 from an earlier version, note that the
|
|
|
|
|
the default installed location for the <code>adb</code> tool has changed from
|
|
|
|
|
<code><<em>SDK</em>>/tools/adb</code> to
|
|
|
|
|
<code><<em>SDK</em>>/platform-tools/adb</code>. This means that you should
|
|
|
|
|
add the new location to your PATH and modify any custom build scripts to
|
|
|
|
|
reference the new location. Copying the <code>adb</code> executable from the new
|
|
|
|
|
location to the old is not recommended, since subsequent updates to the SDK
|
|
|
|
|
Tools will delete the file.</p>
|
|
|
|
|
</dd>
|
|
|
|
|
|
|
|
|
|
<dt>General notes:</dt>
|
|
|
|
|
<dd>
|
|
|
|
|
<ul>
|
|
|
|
|
<li>All SDK platforms now support Library Projects.</li>
|
|
|
|
|
<li>Support for a true debug build. Developers no longer need to add the
|
|
|
|
|
<code>android:debuggable</code> attribute to the
|
|
|
|
|
<code><application></code> tag in the manifest — the build tools add
|
|
|
|
|
the attribute automatically. In Eclipse/ADT, all incremental builds are assumed
|
|
|
|
|
to be debug builds, so the tools insert <code>android:debuggable="true"</code>.
|
|
|
|
|
When exporting a signed release build, the tools do not add the attribute. In
|
|
|
|
|
Ant, a <code>ant debug</code> command automatically inserts the
|
|
|
|
|
<code>android:debuggable="true"</code> attribute, while <code>ant release</code>
|
|
|
|
|
does not. If <code>android:debuggable="true"</code> is manually set, then
|
|
|
|
|
<code>ant release</code> will actually do a debug build, rather than a release
|
|
|
|
|
build.</li>
|
|
|
|
|
<li>Automatic ProGuard support in release builds. Developers generate a ProGuard
|
|
|
|
|
configuration file using the <code>android</code> tool — the build tools
|
|
|
|
|
then automatically run ProGuard against the project sources during the build.
|
|
|
|
|
For more information, see the <a
|
|
|
|
|
href="{@docRoot}guide/developing/tools/proguard.html">ProGuard</a>
|
|
|
|
|
documentation. </li>
|
|
|
|
|
<li>New overridable Ant javac properties: <code>java.encoding</code>,
|
|
|
|
|
<code>java.source</code>, and <code>java.target</code> (default values are
|
|
|
|
|
"ascii", "1.5", and "1.5", respectively).</li>
|
|
|
|
|
<li>New UI for the HierarchyViewer tool.</li>
|
|
|
|
|
</ul>
|
|
|
|
|
</dd>
|
|
|
|
|
</dl>
|
|
|
|
|
</div>
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
<div class="toggleable closed">
|
|
|
|
|
<a href="#" onclick="return toggleDiv(this)">
|
|
|
|
|
<img src="{@docRoot}assets/images/triangle-closed.png" class="toggle-img" height="9px" width="9px" />
|
|
|
|
|
SDK Tools, Revision 7</a> <em>(September 2010)</em>
|
|
|
|
|
<div class="toggleme">
|
|
|
|
|
|
|
|
|
|
|