| /ndk/docs/ |
| APPLICATION-MK.TXT | 6 This document describes the syntax of Application.mk build files
32 to the NDK build system (this name doesn't go into your generated
48 This variable is optional. If not defined, the NDK will build by
83 of any of the modules. This can be used to change the build of a given
110 This has been corrected to match the full Android build system.
120 This has been corrected to match the full Android build system.
125 By default, the NDK build system will look for a file named Android.mk
131 to point to an alternate build script. A non-absolute path will always
135 By default, the NDK build system will generate machine code for the
|
| /bootable/recovery/updater/ |
| Android.mk | 10 # Build a statically-linked binary to include in OTA packages
14 # Build only in eng, so we don't end up with a copy of this in /system
15 # on user builds. (TODO: find a better way to build device binaries
|
| /cts/tools/vm-tests/src/util/build/ |
| JarBuildStep.java | 17 package util.build;
38 boolean build() { method in class:JarBuildStep
39 if (super.build()) {
|
| JavacBuildStep.java | 17 package util.build;
42 boolean build() { method in class:JavacBuildStep
43 if (super.build())
|
| /development/host/windows/usb/legacy/driver/ |
| sources.inc | 24 sources files needed to build that driver. Also specifies optional
32 TARGETPATH=..\build\Debug
34 TARGETPATH=..\build\Release
|
| /development/testrunner/test_defs/ |
| test_suite.py | 44 """Returns the build path of this test, relative to source tree root."""
52 """Returns a list of dependent build paths."""
84 """Returns the extra build args if available, an empty string otherwise."""
|
| /external/bison/ |
| GNUmakefile | 4 # It is necessary if you want to build targets usually of interest
55 # Tell version 3.79 and up of GNU make to not build goals in this
57 # build multiple targets on one command line.
|
| /external/dnsmasq/contrib/slackware-dnsmasq/ |
| dnsmasq.SlackBuild | 7 BUILD=${BUILD:-1}
55 makepkg -l y -c n ../dnsmasq-$VERSION-$ARCH-$BUILD.tgz
|
| /external/dropbear/libtomcrypt/ |
| testme.sh | 17 # stock build
50 # test build with no testing
53 # test build with no file routines
|
| /external/icu4c/data/rbnf/ |
| rbnffiles.mk | 4 # A list of txt's to build
20 # * To REPLACE the default list and only build with a few
28 # Aliases which do not have a corresponding xx.xml file (see icu-config.xml & build.xml)
|
| /external/icu4c/samples/ |
| readme.txt | 58 * How do I build the samples?
62 To build all samples at once:
64 Unix: - build and install (make install) ICU
|
| /external/iptables/ |
| INSTALL | 33 4) If you want to build a statically linked version of the iptables binary,
39 5) If you want to build a single BusyBox style multipurpose binary instead of
45 NOTE: make sure you build with at least the correct LIBDIR=
|
| /external/openssl/crypto/des/ |
| README | 16 The best way to build this library is to build it as part of SSLeay.
39 after the build to make sure everything works.
|
| /external/openssl/crypto/threads/ |
| netware.bat | 2 rem batch file to build multi-thread test ( mttest.nlm )
5 rem debug => build using debug settings
37 echo # dynamically generated command file for metrowerks build > mttest.def
|
| /external/quake/ |
| Android.mk | 9 # Build Quake activity
25 # Build Quake Shared Library
109 # Build stand-alone quake executable on device
|
| /external/sqlite/dist/ |
| Android.mk | 3 ## Build the library
50 ## Build the device command line tool sqlite3
83 ## Build the host command line tool sqlite3
|
| /external/stlport/doc/ |
| README.msvc | 21 To build and use STLport you will need following tools and libraries:
28 In a console window go to the STLport build/lib folder. Run
32 This command will present you the different available build options. Just follow
52 to have the MSVC++ compiler run during the build process. The most important
57 4. Go to the STLport build/lib folder:
58 cd C:\STLport\build\lib
75 STLports 'build/test/unit' folder and type:
105 d : debug build
106 stld: debug build with _STLP_DEBUG (STL safe) mode
107 _x: Build of STLport as a dll but statically link to the native runtime
[all...] |
| /external/webkit/JavaScriptCore/Configurations/ |
| Version.xcconfig | 29 // The bundle version and short version string are set based on the current build configuration, see below.
41 // The production build always uses the full version with a system version prefix.
45 // The production build always uses the major version with a system version prefix
|
| /external/webkit/JavaScriptGlue/Configurations/ |
| Version.xcconfig | 29 // The bundle version and short version string are set based on the current build configuration, see below.
41 // The production build always uses the full version with a system version prefix.
45 // The production build always uses the major version with a system version prefix
|
| /external/webkit/WebCore/Configurations/ |
| Version.xcconfig | 29 // The bundle version and short version string are set based on the current build configuration, see below.
41 // The production build always uses the full version with a system version prefix.
45 // The production build always uses the major version with a system version prefix
|
| /external/webkit/WebKit/mac/Configurations/ |
| Version.xcconfig | 29 // The bundle version and short version string are set based on the current build configuration, see below.
41 // The production build always uses the full version with a system version prefix.
45 // The production build always uses the major version with a system version prefix
|
| /external/webkit/WebKitTools/Scripts/webkitpy/steps/ |
| completerollout.py | 30 from webkitpy.steps.build import Build
39 Build,
|
| /frameworks/base/docs/html/guide/developing/testing/ |
| index.jd | 25 the Eclipse UI. Once you have written your tests, you can build and run them and
32 use them to set up and manage test projects, build your test application,
34 the <code>android</code> tool to create and manage test projects, the Ant build system
|
| /frameworks/base/docs/html/guide/developing/ |
| other-ide.jd | 51 includes all the tools you need to set up an Android project, build it, debug it and then
76 <dd>To compile and build your Android project into an installable .apk file.</dd>
91 with some default application files, stub files, configuration files and a build file.</p>
111 <li><code>target</code> is the "build target" for your application. It corresponds
113 build your project against. To see a list of available targets and their corresponding IDs,
117 for your .apk filename when you build your application.</li>
147 <li><code>build.xml</code> - Build file for Ant.</li>
148 <li><code>default.properties</code> - Properties for the build system. <em>Do not modify
150 <li><code>build.properties</code> - Customizable properties for the build system. You can edi
[all...] |
| /external/qemu/distrib/sdl-1.2.12/ |
| android-configure.sh | 4 # directory. It depends on the Android emulator build scripts
5 # that should normally be located in ../emulator/android/build
14 # try to find the Android build directory automatically
16 if [ -f ../../android/build/common.sh ] ; then
30 if [ ! -f $ANDROID_QEMU_PATH/android/build/common.sh ] ; then
32 echo "contains the Android emulator build scripts."
37 . $ANDROID_QEMU_PATH/android/build/common.sh
89 echo " --try-64 try to build a 64-bit executable (may crash)"
110 # we can build SDL with Cygwin, so enable it
150 # BUILD_CFLAGS are used to build SDL, but SDL_CFLAGS are use
[all...] |
