Home
last modified time | relevance | path

Searched refs:build (Results 1 – 25 of 331) sorted by relevance

12345678910>>...14

/frameworks/base/core/tests/benchmarks/src/com/android/internal/util/
DIndentingPrintWriterBenchmark.java42 final Node manyChildren = Node.build("ManyChildren", Node.build("1"), Node.build("2"), in setUp()
43 Node.build("3"), Node.build("4"), Node.build("5"), Node.build("6"), Node.build("7"), in setUp()
44 Node.build("8"), Node.build("9"), Node.build("10")); in setUp()
46 mSimple = Node.build("RED"); in setUp()
47 mComplex = Node.build("PARENT", Node.build("RED"), Node.build("GREEN", in setUp()
48 Node.build("BLUE", manyChildren, manyChildren), manyChildren, manyChildren), in setUp()
105 public static Node build(String name, Node... children) { in build() method in IndentingPrintWriterBenchmark.Node
/frameworks/base/docs/html/sdk/installing/
Dmigrate.jd8 Gradle build files. You can then import your project into Android Studio.</p>
17 build files</strong>.</li>
22 <p>Your selected project remains in the same location but now contains a {@code build.gradle}
32 <strong>build.gradle</strong> file and click <strong>OK</strong>.</li>
45 don't generate a Gradle build file from Eclipse&mdash;Android Studio will successfully build and
46 run projects using an existing Ant build file. However, in order to take advantage of build
48 we strongly suggest that you generate a Gradle build file using
49 the ADT plugin or write your own Gradle build file for use with Android Studio.
50 For more information about the Gradle build system, see the
51 <a href="http://tools.android.com/tech-docs/new-build-system/user-guide">Gradle
/frameworks/base/docs/html/tools/building/
Dindex.jd8 <li><a href="#detailed-build">A Detailed Look at the Build Process</a></li>
13 <p>During the build process, your Android projects are compiled and packaged into an .apk file,
23 <p>If you are developing in a non-Eclipse environment, you can build your project with the
24 …generated <code>build.xml</code> Ant file that is in the project directory. The Ant file calls tar…
25 automatically call the build tools for you.</p>
29 your application, because the build tools use a debug key with a known password so you do not have
30 to enter it every time you build. When you are ready to release the application to Google
33 <p>Fortunately, Eclipse or your Ant build script signs the application for you in debug mode
34 when you build your application. You can also easily setup Eclipse or your Ant build to sign your
40 <img src="{@docRoot}images/build-simplified.png" />
[all …]
Dbuilding-eclipse.jd20 <p>Eclipse and ADT provide an environment where most of the details of the build process are
21 hidden from you. By default, the build process constantly runs in the background as you make
27 manually perform these tasks. Since most of the build process is taken care of by Eclipse, the
28 following topics show you how to run an application, which will automatically build your
31 …<p>To distribute your application, however, you must build your application in release mode and si…
50 <li>Compile the project (if there have been changes since the last build).</li>
85 …element to <code>true</code>. As of ADT 8.0, this is done by default when you build in debug mode.…
155 requirements of the application's build target, the application is installed and run upon
159 of the build target, a "device chooser" is shown to let you select which device to use.</li>
161 <li>If there are no devices or emulators running that meet the requirements of the build
[all …]
Dbuilding-cmdline.jd34 <p>There are two ways to build your application using the Ant build script: one for
36 …final package for release &mdash; <em>release mode</em>. Regardless of which way you build your ap…
41 …and build your project. This will create the .apk file that you can install on an emulator or devi…
42 When you build in debug mode, the .apk file is automatically signed by the SDK tools with
45 When you build in release mode, the .apk file is <em>unsigned</em>, so you
71 <p>For immediate application testing and debugging, you can build your application in debug mode
72 and immediately install it on an emulator. In debug mode, the build tools automatically sign your
75 <p>To build in debug mode:</p>
100 <p>When you're ready to release and distribute your application to end-users, you must build your
106 zipalign} tool. There are two approaches to building in release mode: build an unsigned package
[all …]
/frameworks/base/core/tests/coretests/src/android/net/
DUriTest.java37 Uri uri = builder.build(); in testToStringWithPathOnly()
51 .build()); in testParcelling()
62 u = u.buildUpon().build(); in parcelAndUnparcel()
74 Uri u = Uri.parse("bob:lee").buildUpon().scheme("robert").build(); in testBuildUponOpaqueStringUri()
144 .build(); in testEqualsAndHashCode()
153 .build(); in testEqualsAndHashCode()
193 Uri b = a.buildUpon().fragment("new").build(); in testBuildUponOpaqueUri()
205 .build(); in testBuildUponEncodedOpaqueUri()
206 Uri b = a.buildUpon().fragment("new").build(); in testBuildUponEncodedOpaqueUri()
224 .build(); in testSms()
[all …]
/frameworks/testing/androidtestlib/tests/src/com/android/test/runner/
DTestRequestBuilderTest.java89 TestRequest request = b.build(mInstr, mBundle); in testNoSize()
103 TestRequest request = b.build(mInstr, mBundle); in testSize()
118 TestRequest request = b.build(mInstr, mBundle); in testSize_class()
133 TestRequest request = b.build(mInstr, mBundle); in testSize_classFiltered()
158 TestRequest request = b.build(mInstr, mBundle); in testAddAnnotationInclusionFilter()
173 TestRequest request = b.build(mInstr, mBundle); in testAddAnnotationExclusionFilter()
/frameworks/base/core/tests/coretests/src/android/text/
DStaticLayoutTest.java49 Layout l = b.build(); in testGetters1()
73 Layout l = b.build(); in testGetters2()
89 Layout l = b.build(); in testGetters3()
107 Layout l = b.build(); in testGetters4()
135 Layout l = b.build(); in testGetters5()
156 Layout l = b.build(); in testGetters6()
178 Layout l = b.build(); in testGetters7()
200 Layout l = b.build(); in testGetters8()
279 Layout build() { in build() method in StaticLayoutTest.LayoutBuilder
DStaticLayoutDirectionsTest.java117 checkDirections(b.build(), i, b.text, expected, f); in testDirections()
130 Layout l = b.build(); in testTrailingWhitespace()
150 Layout l = b.build(); in testNextToRightOf()
166 Layout l = b.build(); in testNextToLeftOf()
/frameworks/base/keystore/tests/src/android/security/
DAndroidKeyPairGeneratorTest.java90 .build()); in testKeyPairGenerator_Initialize_Params_Encrypted_Success()
126 .build(), in testKeyPairGenerator_Initialize_ParamsAndSecureRandom_Encrypted_Failure()
140 .build()); in testKeyPairGenerator_GenerateKeyPair_Encrypted_Success()
155 .build()); in testKeyPairGenerator_GenerateKeyPair_Unencrypted_Success()
172 .build()); in testKeyPairGenerator_GenerateKeyPair_Replaced_Success()
187 .build()); in testKeyPairGenerator_GenerateKeyPair_Replaced_Success()
205 .build()); in testKeyPairGenerator_GenerateKeyPair_Replaced_UnencryptedToEncrypted_Success()
221 .build()); in testKeyPairGenerator_GenerateKeyPair_Replaced_UnencryptedToEncrypted_Success()
/frameworks/support/v4/java/android/support/v4/app/
DNotificationCompat.java82 public Notification build(Builder b); in build() method
86 public Notification build(Builder b) { in build() method in NotificationCompat.NotificationCompatImplBase
99 public Notification build(Builder b) { in build() method in NotificationCompat.NotificationCompatImplHoneycomb
107 public Notification build(Builder b) { in build() method in NotificationCompat.NotificationCompatImplIceCreamSandwich
116 public Notification build(Builder b) { in build() method in NotificationCompat.NotificationCompatImplJellybean
148 return(jbBuilder.build()); in build()
587 return (Notification) IMPL.build(this); in getNotification()
594 public Notification build() { in build() method in NotificationCompat.Builder
595 return (Notification) IMPL.build(this); in build()
622 public Notification build() { in build() method in NotificationCompat.Style
[all …]
/frameworks/base/core/tests/coretests/src/android/content/
DContentProviderOperationTest.java55 .build(); in testInsert()
60 return uri.buildUpon().appendPath("19").build(); in testInsert()
68 .build(); in testInsertNoValues()
73 return uri.buildUpon().appendPath("19").build(); in testInsertNoValues()
82 .build(); in testInsertFailed()
107 .build(); in testInsertWithBackRefs()
115 return uri.buildUpon().appendPath("19").build(); in testInsertWithBackRefs()
124 .build(); in testUpdate()
130 return uri.buildUpon().appendPath("19").build(); in testUpdate()
139 .withValues(sTestValues1).build(); in testAssert()
[all …]
/frameworks/compile/libbcc/tests/debuginfo/
DREADME7 build machine (currently, only Linux has been tested extensively) and target
10 Host tests use clang to build bytecode (bc) files, which are then executed
17 llvm-rs-cc from the Android SDK to build a test binary package (apk)
29 the build environment variables set (i.e. ANDROID_BUILD_TOP)
31 You need the following tools (not built by the android build system) on
35 In addition, you need a build of gdbserver available in the prebuilt directory.
/frameworks/compile/mclinker/
Dmcld.mk5 MCLD_HOST_BUILD_MK := $(MCLD_ROOT_PATH)/mcld-host-build.mk
6 MCLD_DEVICE_BUILD_MK := $(MCLD_ROOT_PATH)/mcld-device-build.mk
/frameworks/compile/libbcc/
Dlibbcc-gen-config-from-mk.mk24 $(PRIVATE_PATH)/tools/build/gen-config-from-mk.py < $< > $@
26 $(LIBBCC_ROOT_PATH)/tools/build/gen-config-from-mk.py
Dlibbcc.mk33 LIBBCC_HOST_BUILD_MK := $(LIBBCC_ROOT_PATH)/libbcc-host-build.mk
34 LIBBCC_DEVICE_BUILD_MK := $(LIBBCC_ROOT_PATH)/libbcc-device-build.mk
Dlibbcc-gen-build-info.mk47 gen_build_info := $(LOCAL_PATH)/tools/build/gen-build-info.py
/frameworks/base/tests/HwAccelerationTest/
Ddefault.properties6 # To customize properties used by the Ant build system use,
7 # "build.properties", and override values to adapt the script to your
/frameworks/base/tests/SmokeTest/
DREADME2 the build system on every single build. They are intended to run very quickly.
/frameworks/base/docs/html/tools/projects/
Dprojects-cmdline.jd39 projects. An Android project contains all of the files and resources that are needed to build a
43 …<li>An Android project contains all of the files and resources that are needed to build a project …
61 application files, stub files, configuration files and a build file.</p>
75 <li><code>target</code> is the "build target" for your application. It corresponds to an
77 build your project against. To see a list of available targets and their corresponding IDs,
81 will be used for your .apk filename when you build your application.</li>
123 project to the new development environment. You can also use this command to revise the build
137 <li><code>target</code> is the "build target" for your application. It corresponds to an
139 build your project against. To see a list of available targets and their corresponding IDs,
169 preset property that indicates to the build system that the project is a library. It does this by
[all …]
Dindex.jd34 files such as the Ant build and Android Manifest file. An application project is the main type
48 pulled into the <code>.apk</code> file at build time.</dd>
73 …<dd>Output directory of the build. This is where you can find the final <code>.apk</code> file and…
173 <dd>This file contains project settings, such as the build target. This file is integral to
180 <dd>Customizable computer-specific properties for the build system. If you use Ant to build
188 <dd>Customizable properties for the build system. You can edit this file to override default
189 build settings used by Ant and also provide the location of your keystore and key alias so that
190 the build tools can sign your application when building in release mode. This file is integral
194 <dt><code>build.xml</code></dt>
196 <dd>The Ant build file for your project. This is only applicable for projects that
[all …]
/frameworks/base/docs/html/guide/practices/app-design/
Dindex.jd4 …build applications on a new platform, you first learn what APIs are available and how to use them.…
14 different ways; the documents below explain how you can build Android
/frameworks/base/docs/html/tools/help/
Dproguard.jd44 <p>ProGuard is integrated into the Android build system, so you do not have to invoke it
45 manually. ProGuard runs only when you build your application in release mode, so you do not
46 have to deal with obfuscated code when you build your application in debug mode.
61 <p>To enable ProGuard so that it runs as part of an Ant or Eclipse build, set the
77 <p>When you build your application in release mode, either by running <code>ant release</code> or
78 by using the <em>Export Wizard</em> in Eclipse, the build system automatically checks to see if
91 This file is important when you receive a bug report from a release build, because it
111 …<p class="caution"><strong>Caution:</strong> Every time you run a build in release mode, these fil…
174 By retaining a copy of the <code>mapping.txt</code> file for each release build,
176 …A project's <code>mapping.txt</code> file is overwritten every time you do a release build, so you…
[all …]
/frameworks/compile/libbcc/include/bcc/Renderscript/
DRSCompilerDriver.h84 RSExecutable *build(BCCContext &pContext,
89 RSExecutable *build(RSScript &pScript, const char *pOut,
/frameworks/base/native/
Dcopy-to-ndk.sh51 sh $ANDROID_BUILD_TOP/ndk/build/tools/build-platforms.sh

12345678910>>...14