Home
last modified time | relevance | path

Searched refs:generate (Results 1 – 25 of 53) sorted by relevance

123

/ndk/tests/device/test-gnustl-full/unit/
Dgenerator_test.cpp43 generate(numbers, numbers + 10, ptr_gen(cxxrand)); in gener1()
45 generate(numbers, numbers + 10, cxxrand); in gener1()
53 generate(v1.begin(), v1.end(), generator); in gener2()
/ndk/tests/device/test-stlport/unit/
Dgenerator_test.cpp43 generate(numbers, numbers + 10, ptr_gen(cxxrand)); in gener1()
45 generate(numbers, numbers + 10, cxxrand); in gener1()
53 generate(v1.begin(), v1.end(), generator); in gener2()
/ndk/sources/cxx-stl/llvm-libc++/libcxx/test/numerics/rand/rand.util/rand.util.seedseq/
Dgenerate.pass.cpp801 s.generate(b, b + n); in main()
/ndk/sources/cxx-stl/llvm-libc++/libcxx/test/algorithms/alg.modifying.operations/alg.generate/
Dgenerate.pass.cpp34 std::generate(Iter(ia), Iter(ia+n), gen_test()); in test()
/ndk/docs/text/
DDEVELOPMENT.text4 This document describes how one can modify the NDK and generate
99 IMPORTANT: If you plan to generate NDK release packages, even
118 If you plan to generate your own NDK release packages, it is better
183 To generate Windows binaries on Windows, install the "mingw32"
211 This will generate a package file containing all the prebuilts, that
228 You can generate new experimental NDK release packages once you're satisfied
234 The simplest, and also the slowest way, to generate a new NDK release
249 This is the second simplest way to generate a new package, and it will
260 NOTE: This method can only be used to generate a single release package
266 in section III.3 above, you can use these to generate release packages
DNDK-DEPENDS.text10 With the --print-java option, it can also be used to generate a Java
50 > Prints the dependency graph as Graphviz .dot file, then generate
DANDROID-MK.text31 application package. Static libraries can be used to generate
114 a shared library module named 'foo' will generate 'libfoo.so'.
118 add another 'lib' prefix and will generate libfoo.so as well.
141 exactly. There is also BUILD_STATIC_LIBRARY to generate a static library.
198 > note that this will generate a file named `lib$(LOCAL_MODULE).so`.
210 > Note that this will generate a file named `lib$(LOCAL_MODULE).a`.
435 > generated files. By default, module <foo> will always generate a
540 > your Application.mk, and will let the NDK generate
606 > following will tell the linker to generate a module that links to
835 > generate a 'thin archive', i.e. a library file (e.g. `libfoo.a`) which
[all …]
DAPPLICATION-MK.text61 > will generate a file in `libs/$ABI/`.
80 > A 'release' mode is the default, and will generate highly
81 > optimized binaries. The 'debug' mode will generate un-optimized
160 > By default, the NDK build system will generate machine code for the
DNDK-BUILD.text30 ndk-build NDK_DEBUG=1 --> generate debuggable native code.
98 Ie. 64-bit toolchains still generate 32-bit binaries for Android.
DCPU-X86-64.text25 will generate machine code for all supported ABIs with this NDK. Doing so
DINSTALL.text19 cannot generate final application packages (.apk files), only the shared library
DCPU-MIPS.text25 will generate machine code for all supported ABIs with this NDK. Doing so
DCPU-ARCH-ABIS.text79 will generate thumb code by default, unless you define LOCAL_ARM_MODE
274 By default, the NDK will generate machine code for the 'armeabi' ABI.
275 You can however add the following line to your Application.mk to generate
298 which will generate machine code for all supported ABIs with this NDK. Doing so
DOVERVIEW.text65 generate native ARM binaries on Linux, OS X and Windows (with Cygwin)
148 will then need to generate your final .apk through the usual means.
224 - The CPU architecture(s) to generate machine code for.
DCPU-X86.text25 will generate machine code for all supported ABIs with this NDK. Doing so
/ndk/build/tools/
DDEV-SCRIPTS-USAGE.TXT38 compiled to generate useful host programs for the final NDK
49 the dev-script 'build-cxx-stl.sh' can be used to generate prebuilt
55 The dev-script 'build-cxx-stl.sh' can be used to generate prebuilt
60 ndk-build. The dev-script 'build-cxx-stl.sh' can be used to generate
66 The dev-script 'build-gnu-libstdc++.sh' is used to generate prebuilt
147 These files were introduced in NDK r7 and are used to generate "shell"
181 to use the directories with --with-sysroot. For example, to generate
203 generate 32-bit programs by default. You can experiment with 64-bit binary
221 programs used to generate machine code for the target Android
350 Once you've completed your builds, you should be able to generate the other
[all …]
Dbuild-mingw64-toolchain.sh196 All toolchain binaries can generate both Win32 and Win64 executables.
202 toolchain prefix, e.g. <prefix>-gcc to compile. For example, to generate
/ndk/build/core/
Ddefinitions.mk83 define ev-generate-dir
98 generate-dir = $(eval $(call ev-generate-dir,$1))
113 define ev-generate-file-dir
115 $$(call generate-dir,$$(__ndk_file_dir))
119 generate-file-dir = $(eval $(call ev-generate-file-dir,$1))
294 define generate-list-file-ev
299 $$(call generate-file-dir,$$(__list_file).tmp)
316 generate-list-file = $(eval $(call generate-list-file-ev,$1,$2))
1428 $$(_OBJ): $$(call generate-list-file,$$(_FLAGS),$$(_OPTIONS_LISTFILE))
1433 $$(call generate-file-dir,$$(_OBJ))
[all …]
Dsetup-toolchain.mk182 $(call generate-file-dir,$(NDK_APP_GDBSERVER))
203 $(call generate-file-dir,$(NDK_APP_GDBSETUP))
Dbuild-binary.mk493 $(call generate-file-dir,$(LOCAL_BUILT_MODULE))
529 $(call generate-list-file,$(ar_objects),$(ar_list_file))
627 $(call generate-list-file,$(linker_options),$(linker_list_file))
695 $(call generate-file-dir,$(LOCAL_INSTALLED))
/ndk/sources/cxx-stl/stlport/
DREADME21 will be added to it. This option should also generate smaller
/ndk/build/tools/toolchain-patches/gcc/
D0003-gcc-prevent-crash-on-Eclair-and-older-platforms.patch8 libsupc++ and libstdc++ generate static C++ constructors that
/ndk/sources/third_party/googletest/googletest/
DCHANGES59 can now generate custom failure messages.
/ndk/sources/host-tools/make-3.81/tests/scripts/features/
Dtargetvars259 …nged_since : BUILD_OBJ=$(shell if [ -f "build_information.generate" ]; then echo "$(…
/ndk/sources/cxx-stl/llvm-libc++abi/libcxxabi/src/Unwind/
DUnwindRegistersSave.S345 @ want the compiler to generate instructions that access those) but this is

123