| /build/tools/releasetools/ |
| sign_target_files_apks | 39 build/target/product/security/testkey ==> $dir/releasekey
40 build/target/product/security/media ==> $dir/media
41 build/target/product/security/shared ==> $dir/shared
42 build/target/product/security/platform ==> $dir/platform
55 the last component of the build fingerprint). Prefix each with
153 elif info.filename in ("SYSTEM/build.prop",
182 if key == "ro.build.fingerprint":
186 elif key == "ro.build.description":
191 elif key == "ro.build.tags":
220 OPTIONS.key_map["build/target/product/security/testkey"] + ".x509.pem"
[all...] |
| /development/pdk/docs/source/ |
| using-eclipse.jd | 20 : You will still be using "make" to build the files you will actually run (in the emulator or on a device). You will be using Eclipse to edit files and verify that they compile, but when you want to run something you will need to make sure files are saved in Eclipse and run "make" in a shell. The Eclipse build is just for error checking.
22 <p>Eclipse needs a list of directories to search for Java files. This is called the "Java Build Path" and can be set with the .classpath file. We have a sample version to start you off.
59 <p>Once the project workspace is created, Eclipse should start building. In theory, it should build with no errors and you should be set to go. If necessary, uncheck and re-check Project Build Automatically to force a rebuild.
78 Adding apps to the build path
84 <li>Select "Java Build Path" from the left-hand menu.
96 /src. Depending on which app(s) you include, you may also need to include othersrc/main/java directories under android/dalvik/libcore. Do this if you find you cannot build with the default set.
103 <p>Once the project is created, you need to set up the Java Build Path:
109 <li>Select "Java Build Path" from the left-hand menu
[all...] |
| /external/icu4c/test/testdata/ |
| Makefile | 18 ## Build directory information
30 check check-local check-recursive build-dir java-output
32 .NOTPARALLEL: build-dir
45 all-local: build-dir build-testdata testdata packagetest
83 BUILDDIR=$(OUTDIR)/build/$(ICUDATA_PLATFORM_NAME)
102 PKGDATA = $(BINDIR)/pkgdata $(PKGDATA_OPTS) -q -c -s $(CURDIR)/out/build/$(ICUDATA_PLATFORM_NAME)
106 TESTBUILDDIR=$(TESTOUTDIR)/build
143 build-testdata: build-dir $(ALL_TEST_FILES) $(TESTBUILDDIR)/testdata.lst $(TESTBUILDDIR)/iscii.re
[all...] |
| Makefile.in | 18 ## Build directory information
32 check check-local check-recursive build-dir java-output
34 .NOTPARALLEL: build-dir
47 all-local: build-dir build-testdata testdata packagetest
88 BUILDDIR=$(OUTDIR)/build/$(ICUDATA_PLATFORM_NAME)
108 PKGDATA = $(TOOLBINDIR)/pkgdata $(PKGDATA_OPTS) -q -c -s $(CURDIR)/out/build/$(ICUDATA_PLATFORM_NAME)
112 TESTBUILDDIR=$(TESTOUTDIR)/build
150 build-testdata: build-dir $(ALL_TEST_FILES) $(TESTBUILDDIR)/testdata.lst $(TESTBUILDDIR)/iscii.re
[all...] |
| /development/samples/TicTacToeMain/ |
| _index.html | 5 the TicTacToeLib library project. When you build the TicTacToeMain application,
6 the build tools look for the library project and compile it's code and resources
44 <p>If you want to build the TicTacToeMain application, you can obtain it by
48 — in order to build TicTacToeMain, you need to add both projects to your
51 <p>To build an application that uses a library project, you also need to update
|
| /device/sample/frameworks/PlatformLibrary/ |
| README.txt | 25 build targets and corresponding build outputs:
31 The top-level Android.mk defines the rules to build the shared library itself,
68 build system. The only two special things needed to use your library are:
70 - A LOCAL_JAVA_LIBRARIES line in the Android.mk to have the build system link
|
| /external/dhcpcd/dhcpcd-hooks/ |
| 20-resolv.conf | 16 # Build a list of interfaces
19 # Build the resolv.conf
21 # Build the header
26 # Build the search list
31 # Build the nameserver list
|
| /external/gtest/test/ |
| Android.mk | 18 # The linux build and tests are run under valgrind by 'runtest'.
23 # TODO: Refactor these as 1st class build templates as suggested in
26 # Gtest depends on STLPort which does not build on host/simulator.
86 # Cannot build simulator with STLport.
115 # Cannot build simulator with STLport.
|
| /external/libffi/testsuite/ |
| run-all-tests | 21 # the build system.
52 # a build directory).
55 if [ -d out -a -d build ]; then
71 : # Already have build system defs.
74 . build/envsetup.sh
|
| /external/openssl/ |
| README.android | 43 6) Build openssl from the external/openssl directory with:
47 If there are build errors, then patches/*.mk, openssl.config, or
55 8) Do a full build before checking in:
59 Optionally, check whether build flags (located in android-config.mk
62 update build flags:
|
| /external/v8/test/cctest/ |
| test-version.cc | 39 void SetVersion(int major, int minor, int build, int patch,
43 Version::build_ = build;
52 static void CheckVersion(int major, int minor, int build,
60 SetVersion(major, minor, build, patch, candidate, "");
68 SetVersion(major, minor, build, patch, candidate, soname);
|
| /external/webkit/WebKit/wx/bindings/python/ |
| wscript | 26 # wxWebKit Python bindings build script for the waf build system
63 def build(bld):
71 import wx.build.config
72 wx_swig_args += wx.build.config.swig_args
|
| /external/stlport/doc/ |
| README.evc4 | 20 To build and use the STLport you will need following tools and libraries:
32 This can be done by using batch files under your 'eMbedded Visual C++' directory(use either WCEemulator.BAT if you want to build STLport for the emulator or WCEARMV4.BAT if you intend to aim an ARM device).
37 Third, when you are 100percent sure you've set correctly systems variables go to the STLport/build/lib dir and run the configure.bat with
39 then invoke following command: 'nmake /fmsvc.mak install' to build the library.
42 At the end of build process you should have some libs installed in STLport/lib/evc4-arm or STLport/lib/evc4-x86 and dynamic libs in STLport/bin directory.
46 'nmake /fmsvc.mak clobber' before new build.
48 Note: MIPS platform is also available for build, but it may not compile or work properly. Use with caution!
53 When you successfuly build STLport libs, you should go to STLport/test/unit directory build and run the STLP test suite.
55 Once test build has finished upload and run stlp_unit_test.exe to your emulator or device
[all...] |
| README.dmc | 5 Build of STLport with Digital Mars C++ compiler is very similar
32 - In a console window go to the STLport build\lib folder. Run
40 - To build STLport libraries:
42 cd [STLport dir]\build\lib
45 - To build STLport (dynamic) unit tests:
47 cd [STLport dir]\build\test\unit
68 avoid conflicts with other vendors' linkers and archivers. To build STLport
|
| /dalvik/tests/ |
| run-test | 41 build="build"
45 build_output="build-output.txt"
188 if [ '!' -r "$build" ]; then
189 cp "${progdir}/etc/default-build" build
196 chmod 755 "$build"
201 "./${build}" 2>&1
202 echo "build exit status: $?" 1>&2
207 "./${build}" >"$build_output" 2>&
[all...] |
| /external/guava/src/com/google/common/collect/ |
| ImmutableListMultimap.java | 70 return builder.build();
81 return builder.build();
94 return builder.build();
108 return builder.build();
123 return builder.build();
146 * .build();}</pre>
148 * <p>Builder instances can be reused - it is safe to call {@link #build}
149 * multiple times to build multiple multimaps in series. Each multimap
209 @Override public ImmutableListMultimap<K, V> build() { method in class:ImmutableListMultimap.Builder
210 return (ImmutableListMultimap<K, V>) super.build();
[all...] |
| /external/webkit/WebKitTools/BuildSlaveSupport/build.webkit.org-config/webkit/ |
| steps.py | 129 def setBuild(self, build):
130 ShellCommand.setBuild(self, build)
149 command = ["perl", "./WebKitTools/Scripts/build-webkit"]
166 command = 'rm -rf WebKitBuild && perl ./WebKitTools/Scripts/build-webkit --no-svg'
169 command = ['perl', './WebKitTools/Scripts/build-webkit', '--gtk', '--qmake=qmake-qt4']
177 command = ['perl', './WebKitTools/Scripts/build-webkit', '--wx']
185 def setBuild(self, build):
186 CompileWebKit.setBuild(self, build)
190 ./WebKitTools/Scripts/build-webkit; \
230 # self.command = 'umask 002 && ./WebKitTools/BuildSlaveSupport/build-launcher-app && ./WebKitTools/BuildSlaveSupport/build-launcher-dmg --upload-to-host %s' % (self.ge (…)
[all...] |
| /external/webkit/WebKitTools/Scripts/webkitpy/commands/ |
| download.py | 48 class Build(AbstractSequencedCommand):
49 name = "build"
50 help_text = "Update working copy and build"
54 steps.Build,
59 name = "build-and-test"
60 help_text = "Update working copy, build, and run the tests"
64 steps.Build,
78 steps.Build,
84 land will build and run the tests before committing.
166 name = "build-attachment
[all...] |
| /external/zlib/win32/ |
| DLL_FAQ.txt | 6 of the official DLL build of zlib, named ZLIB1.DLL. If you have
14 - ZLIB1.DLL is the official build of zlib as a DLL.
33 test programs that must run with a valid build of ZLIB1.DLL.
37 and build settings. If you do build the DLL yourself, please
42 If, for any reason, you need to build an incompatible DLL,
51 a static build. The DLL settings were supposed to be enabled
54 build time, resulting in two major problems:
57 the DLL, not all people added it to the build options. In
65 that were unable to run with the official ZLIB.DLL build
[all...] |
| /external/libpng/projects/visualc6/ |
| pngtest.dsp | 2 # Microsoft Developer Studio Generated Build File, Format Version 6.00
8 !MESSAGE This is not a valid makefile. To build this project using NMAKE,
62 # Begin Special Build Tool
67 # End Special Build Tool
94 # Begin Special Build Tool
99 # End Special Build Tool
126 # Begin Special Build Tool
131 # End Special Build Tool
158 # Begin Special Build Tool
163 # End Special Build Tool
[all...] |
| /frameworks/base/core/tests/coretests/src/android/content/ |
| ContentProviderOperationTest.java | 55 .build();
60 return uri.buildUpon().appendPath("19").build();
68 .build();
73 return uri.buildUpon().appendPath("19").build();
82 .build();
107 .build();
115 return uri.buildUpon().appendPath("19").build();
124 .build();
130 return uri.buildUpon().appendPath("19").build();
137 // Build an operation to assert values match provide
[all...] |
| /external/zlib/contrib/vstudio/ |
| readme.txt | 4 This directory contains projects that build zlib and minizip using
7 You don't need to build these projects yourself. You can download the
14 Build instructions for Visual Studio 7.x (32 bits)
23 Build instructions for Visual Studio 2005 (32 bits or 64 bits)
31 Build instructions for Visual Studio 2005 64 bits, PSDK compiler
58 particular build of zlib.dll, you can rename zlibwapi.dll to zlib.dll.
63 - There is also an official DLL build of zlib, named zlib1.dll. This one
|
| /frameworks/base/docs/html/sdk/api_diff/4/changes/ |
| android.os.Build.html | 10 android.os.Build
74 Class android.os.<A HREF="../../../../reference/android/os/Build.html" target="_top"><font size="+2"><code>Build</code></font></A>
87 <A NAME="android.os.Build.CPU_ABI"></A>
88 <nobr><code>String</code> <A HREF="../../../../reference/android/os/Build.html#CPU_ABI" target="_top"><code>CPU_ABI</code></A></nobr>
94 <A NAME="android.os.Build.MANUFACTURER"></A>
95 <nobr><code>String</code> <A HREF="../../../../reference/android/os/Build.html#MANUFACTURER" target="_top"><code>MANUFACTURER</code></A></nobr>
|
| android.os.Build.VERSION.html | 10 android.os.Build.VERSION
74 Class android.os.<A HREF="../../../../reference/android/os/Build.VERSION.html" target="_top"><font size="+2"><code>Build.VERSION</code></font></A>
87 <A NAME="android.os.Build.VERSION.CODENAME"></A>
88 <nobr><code>String</code> <A HREF="../../../../reference/android/os/Build.VERSION.html#CODENAME" target="_top"><code>CODENAME</code></A></nobr>
94 <A NAME="android.os.Build.VERSION.SDK_INT"></A>
95 <nobr><code>int</code> <A HREF="../../../../reference/android/os/Build.VERSION.html#SDK_INT" target="_top"><code>SDK_INT</code></A></nobr>
109 <A NAME="android.os.Build.VERSION.SDK"></A>
110 <nobr><code>String</code> <A HREF="../../../../reference/android/os/Build.VERSION.html#SDK" target="_top"><code>SDK</code></font></A></nobr> </TD>
|
| pkg_android.os.html | 84 <A NAME="Build.VERSION_CODES"></A>
85 <nobr><A HREF="../../../../reference/android/os/Build.VERSION_CODES.html" target="_top"><code>Build.VERSION_CODES</code></A></nobr>
99 <A NAME="Build"></A>
100 <nobr><A HREF="android.os.Build.html">Build</A></nobr>
106 <A NAME="Build.VERSION"></A>
107 <nobr><A HREF="android.os.Build.VERSION.html">Build.VERSION</A></nobr>
|
