| /sdk/sdkmanager/libs/sdklib/src/com/android/sdklib/ |
| IAndroidTarget.java | 66 /** OS Path to the target's version of the aapt tool. */
68 /** OS Path to the target's version of the aidl tool. */
|
| /sdk/sdkmanager/libs/sdklib/src/com/android/sdklib/internal/repository/ |
| ExtraPackage.java | 55 * Creates a new tool package from the attributes and elements of the given XML node.
215 * A "tool" package should always be located in SDK/tools.
|
| /sdk/sdkmanager/libs/sdklib/src/com/android/sdklib/repository/ |
| SdkRepository.java | 55 /** A tool package. */
56 public static final String NODE_TOOL = "tool"; //$NON-NLS-1$
|
| /external/libffi/testsuite/ |
| Makefile.in | 48 RUNTESTDEFAULTFLAGS = --tool $$tool --srcdir $$srcdir
288 exit_status=0; l='$(DEJATOOL)'; for tool in $$l; do \
317 -l='$(DEJATOOL)'; for tool in $$l; do \
318 rm -f $$tool.sum $$tool.log; \
|
| /frameworks/base/docs/html/sdk/ |
| RELEASENOTES.jd | 31 includes the Android SDK and AVD Manager tool. To develop against Android 2.0.1,
66 SDK and AVD environments more easily. The tool lets you create and manage
101 and zipalign tool. In addition, the New Project Wizard now
116 <p>The SDK offers a new tool called Android SDK and AVD Manager that lets you
119 <p>Using the tool, you can quickly check what Android platforms, add-ons,
123 your SDK environment. For example, the tool lets you obtain updates to SDK tools
128 <p>The tool also lets you quickly create new AVDs, manage
135 AVD Manager through the <code>android</code> command-line tool, located in the
136 <sdk>/tools directory. You can launch the tool with a graphical UI by
149 a tool called <code>zipalign</code> that you can run against your .apks, t
[all...] |
| /frameworks/base/docs/html/guide/publishing/ |
| app-signing.jd | 75 <li>Once you have signed the application, use the <code>zipalign</code> tool to optimize the final APK package.</li>
84 for Eclipse and the Ant build tool offer two signing modes — <em>debug mode</em>
101 using Jarsigner (or similar tool). If you do not have a suitable private key already,
192 the Jarsigner tool available on your machine. Both Jarsigner and Keytool are included
238 <code>android</code> tool). When you run <code>ant debug</code> to
240 The script then also aligns the .apk with the <code>zipalign</code> tool.
451 using the Jarsigner tool. Make sure that you have Jarsigner available on your
528 This tool ensures that all uncompressed data starts with a particular byte alignment,
536 <p>The <code>zipalign</code> tool is provided with the Android SDK, inside the
551 <a href="{@docRoot}guide/developing/tools/zipalign.html">zipalign</a> tool
[all...] |
| /prebuilt/darwin-x86/toolchain/arm-eabi-4.2.1/info/ |
| configure.info | 173 The X Window system is built using the imake tool, which uses a
175 tool which was developed using imake requires that the builder have
205 Most readers of this document should already know how to build a tool by
209 Building a tool is normally as simple as running `configure'
322 Another handy tool for an existing body of code is `ifnames'. This
448 The different macro prefixes indicate which tool defines the macro.
[all...] |
| /prebuilt/darwin-x86/toolchain/arm-eabi-4.3.1/info/ |
| configure.info | 173 The X Window system is built using the imake tool, which uses a
175 tool which was developed using imake requires that the builder have
205 Most readers of this document should already know how to build a tool by
209 Building a tool is normally as simple as running `configure'
322 Another handy tool for an existing body of code is `ifnames'. This
448 The different macro prefixes indicate which tool defines the macro.
[all...] |
| /prebuilt/darwin-x86/toolchain/arm-eabi-4.4.0/info/ |
| configure.info | 173 The X Window system is built using the imake tool, which uses a
175 tool which was developed using imake requires that the builder have
205 Most readers of this document should already know how to build a tool by
209 Building a tool is normally as simple as running `configure'
322 Another handy tool for an existing body of code is `ifnames'. This
448 The different macro prefixes indicate which tool defines the macro.
[all...] |
| /prebuilt/darwin-x86/toolchain/arm-eabi-4.4.0/share/info/ |
| configure.info | 173 The X Window system is built using the imake tool, which uses a
175 tool which was developed using imake requires that the builder have
205 Most readers of this document should already know how to build a tool by
209 Building a tool is normally as simple as running `configure'
322 Another handy tool for an existing body of code is `ifnames'. This
448 The different macro prefixes indicate which tool defines the macro.
[all...] |
| /prebuilt/linux-x86/toolchain/arm-eabi-4.2.1/info/ |
| configure.info | 173 The X Window system is built using the imake tool, which uses a
175 tool which was developed using imake requires that the builder have
205 Most readers of this document should already know how to build a tool by
209 Building a tool is normally as simple as running `configure'
322 Another handy tool for an existing body of code is `ifnames'. This
448 The different macro prefixes indicate which tool defines the macro.
[all...] |
| /prebuilt/linux-x86/toolchain/arm-eabi-4.3.1/info/ |
| configure.info | 173 The X Window system is built using the imake tool, which uses a
175 tool which was developed using imake requires that the builder have
205 Most readers of this document should already know how to build a tool by
209 Building a tool is normally as simple as running `configure'
322 Another handy tool for an existing body of code is `ifnames'. This
448 The different macro prefixes indicate which tool defines the macro.
[all...] |
| /prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/info/ |
| configure.info | 173 The X Window system is built using the imake tool, which uses a
175 tool which was developed using imake requires that the builder have
205 Most readers of this document should already know how to build a tool by
209 Building a tool is normally as simple as running `configure'
322 Another handy tool for an existing body of code is `ifnames'. This
448 The different macro prefixes indicate which tool defines the macro.
[all...] |
| /prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/share/info/ |
| configure.info | 173 The X Window system is built using the imake tool, which uses a
175 tool which was developed using imake requires that the builder have
205 Most readers of this document should already know how to build a tool by
209 Building a tool is normally as simple as running `configure'
322 Another handy tool for an existing body of code is `ifnames'. This
448 The different macro prefixes indicate which tool defines the macro.
[all...] |
| /prebuilt/linux-x86/toolchain/i686-unknown-linux-gnu-4.2.1/info/ |
| configure.info | 173 The X Window system is built using the imake tool, which uses a
175 tool which was developed using imake requires that the builder have
205 Most readers of this document should already know how to build a tool by
209 Building a tool is normally as simple as running `configure'
322 Another handy tool for an existing body of code is `ifnames'. This
448 The different macro prefixes indicate which tool defines the macro.
[all...] |
| /frameworks/base/docs/html/guide/developing/ |
| other-ide.jd | 37 <li><a href="{@docRoot}guide/developing/tools/othertools.html#android">android Tool</a></li>
79 <dt>Jarsigner (or similar signing tool)</dt>
84 For more advanced operations, please read the respective documentation for each tool.</p>
89 <p>To create an Android project, you must use the <code>android</code> tool. When you create
142 <p>The tool generates the following files and directories:</p>
186 option). The <code>android</code> tool will generate any files and
244 need to use the Ant tool to compile and build your project. This will create the .apk file
308 {@code zipalign} tool. There are two approaches to building in release mode:
351 may prefer to perform the application signing manually, via Jarsigner (or a similar tool). To
407 tool with no arguments
[all...] |
| /frameworks/base/docs/html/guide/practices/ui_guidelines/ |
| icon_design_1.jd | 204 <li>Create the basic shapes with a tool like Adobe Illustrator, using the
212 <li>Import the icon into a tool like Adobe Photoshop and scale to fit an image
325 <li>Create the basic shapes using a tool like Adobe Illustrator.</li>
326 <li>Import the shape into a tool like Adobe Photoshop and scale to fit an image
442 <li>In a tool like Adobe Photoshop, create the base shape within a 25x25 px
546 <li>Create the basic shapes using a tool like Adobe Illustrator.</li>
547 <li>Import the shape to a tool like Adobe Photoshop and scale to fit an image of
605 <li>Create the basic shape using a tool like Adobe Illustrator.</li>
606 <li>Import the shape into a tool like Adobe Photoshop and scale to fit a 32x32
690 <li>Create the basic shapes using a tool like Adobe Illustrator.</li
[all...] |
| /development/docs/ |
| howto_use_cupcake_sdk.txt | 167 Then use the new "android" tool to create a new build.xml:
186 Note that the "activitycreator" tool has been replaced by the new "android"
187 tool too. Example of how to create a new Ant project:
237 There is a new tool called "android" in the SDK that lets you know which
295 The android tool will automatically print an explanation of required arguments.
|
| /frameworks/base/docs/html/sdk/1.5_r1/ |
| upgrading.jd | 243 <p>If you build your projects using the Ant tool (rather than with Eclipse), note the
257 <p>Now use the new <code>android</code> tool (located in <code><em>your_sdk</em>/tools/</code>)
275 <p class="note"><strong>Note:</strong> The "activitycreator" tool has been replaced
276 by the new "android" tool. For information on creating new projects with the android tool,
|
| /frameworks/base/docs/html/sdk/1.5_r2/ |
| upgrading.jd | 243 <p>If you build your projects using the Ant tool (rather than with Eclipse), note the
257 <p>Now use the new <code>android</code> tool (located in <code><em>your_sdk</em>/tools/</code>)
275 <p class="note"><strong>Note:</strong> The "activitycreator" tool has been replaced
276 by the new "android" tool. For information on creating new projects with the android tool,
|
| /frameworks/base/docs/html/sdk/1.5_r3/ |
| upgrading.jd | 245 <p>If you build your projects using the Ant tool (rather than with Eclipse), note the
259 <p>Now use the new <code>android</code> tool (located in <code><em>your_sdk</em>/tools/</code>)
277 <p class="note"><strong>Note:</strong> The "activitycreator" tool has been replaced
278 by the new "android" tool. For information on creating new projects with the android tool,
|
| /external/icu4c/test/testdata/ |
| ra.xlf | 5 <tool tool-id = "genrb-3.3-icu-4.0" tool-name = "genrb"/>
|
| /external/proguard/docs/ |
| FAQ.html | 177 Yes. First of all, <b>ProGuard</b> is perfectly usable as a command-line tool
210 is ever incorporated, I'll provide a tool to decrypt the strings as well.
240 Yes. <b>ProGuard</b> comes with a companion tool, <b>ReTrace</b>, that can
|
| /frameworks/base/docs/html/resources/articles/ |
| index.jd | 106 <dd>This article discusses how to use the Allocation Tracker tool to observe memory allocations and avoid performance problems that would otherwise be caused by ignoring the effect of Dalvik's garbage collector.</dd>
156 <dd>The Android SDK includes a tool called zipalign that optimizes the way an application is packaged. Running zipalign against your application enables Android to interact with it more efficiently at run time and thus has the potential to make it and the overall system run faster. This article provides a high-level overview of the zipalign tool and its use.</dd>
|
| /external/e2fsprogs/debian/ |
| control | 57 This package includes a tool that parses a command table to generate
69 This package includes a tool that parses a command table to generate
|
