/ndk/tests/device/test-stlport/unit/ |
D | generator_test.cpp | 43 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-gnustl-full/unit/ |
D | generator_test.cpp | 43 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/ |
D | generate.pass.cpp | 801 s.generate(b, b + n); in main()
|
/ndk/sources/cxx-stl/llvm-libc++/libcxx/test/algorithms/alg.modifying.operations/alg.generate/ |
D | generate.pass.cpp | 34 std::generate(Iter(ia), Iter(ia+n), gen_test()); in test()
|
/ndk/build/tools/ |
D | README.md | 30 All dev-scripts rebuilding host programs on Linux and Darwin will only generate 63 generate useful host programs for the final NDK installation. For example, 83 dev-script `build-cxx-stl.sh` can be used to generate prebuilt libraries from 90 The dev-script `build-cxx-stl.sh` can be used to generate prebuilt libraries 97 dev-script `build-gnu-libstdc++.sh` is used to generate prebuilt libraries from 184 These files were introduced in NDK r7 and are used to generate stub shared 215 directories with --with-sysroot. For example, to generate binaries that target 229 programs used to generate machine code for the target Android system supported 309 Once you've completed your builds, you should be able to generate the other 323 script require that you generate a fully populated $NDK/platforms/ directory [all …]
|
D | build-mingw64-toolchain.sh | 196 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/ |
D | definitions.mk | 83 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)) 1443 $$(_OBJ): $$(call generate-list-file,$$(_FLAGS),$$(_OPTIONS_LISTFILE)) 1448 $$(call generate-file-dir,$$(_OBJ)) [all …]
|
D | setup-toolchain.mk | 182 $(call generate-file-dir,$(NDK_APP_GDBSERVER)) 203 $(call generate-file-dir,$(NDK_APP_GDBSETUP))
|
D | build-binary.mk | 511 $(call generate-file-dir,$(LOCAL_BUILT_MODULE)) 547 $(call generate-list-file,$(ar_objects),$(ar_list_file)) 645 $(call generate-list-file,$(linker_options),$(linker_list_file)) 713 $(call generate-file-dir,$(LOCAL_INSTALLED))
|
/ndk/sources/cxx-stl/stlport/ |
D | README | 21 will be added to it. This option should also generate smaller
|
/ndk/ |
D | README.md | 19 compiler can use `build/tools/build-mingw64-toolchain.sh` to generate their own
|
/ndk/sources/third_party/googletest/googletest/ |
D | CHANGES | 59 can now generate custom failure messages.
|
D | README | 414 where FOO is the name of the file it will generate. For example, the 415 file include/gtest/internal/gtest-type-util.h.pump is used to generate
|
/ndk/sources/host-tools/make-3.81/tests/scripts/features/ |
D | targetvars | 259 …nged_since : BUILD_OBJ=$(shell if [ -f "build_information.generate" ]; then echo "$(…
|
/ndk/sources/cxx-stl/llvm-libc++abi/libcxxabi/src/Unwind/ |
D | UnwindRegistersSave.S | 364 @ want the compiler to generate instructions that access those) but this is
|
D | UnwindRegistersRestore.S | 354 @ want the compiler to generate instructions that access those) but this is
|
/ndk/sources/host-tools/make-3.81/config/ |
D | gettext.m4 | 233 dnl Mark actions used to generate GNU NLS library. 435 dnl bison-1.26 because earlier versions generate a plural.c that doesn't
|
/ndk/sources/host-tools/make-3.81/ |
D | INSTALL | 206 Print the version of Autoconf used to generate the `configure'
|
D | configure.in | 451 # We only generate the build.sh if we have a build.sh.in; we won't have
|
D | readme.vms | 15 Use the 1st version to generate a 2nd version
|
D | aclocal.m4 | 470 # loop where config.status creates the headers, so we can generate
|
/ndk/sources/cxx-stl/stlport/stlport/stl/ |
D | _algo.h | 222 generate(_ForwardIter __first, _ForwardIter __last, _Generator __gen) { in generate() function
|
/ndk/sources/third_party/googletest/googletest/include/gtest/ |
D | gtest-param-test.h.pump | 267 // passed in and keeps them to generate tests in RUN_ALL_TESTS().
|
/ndk/sources/cxx-stl/llvm-libc++/libcxx/include/ |
D | random | 419 void generate(RandomAccessIterator begin, RandomAccessIterator end); 1957 __q.generate(__ar, __ar + __k + 3); 1970 __q.generate(__ar, __ar + __k + 3); 2326 __q.generate(__ar, __ar + __n * __k); 2351 __q.generate(__ar, __ar + __n * __k); 2678 __q.generate(__ar, __ar + __r * __k); 2693 __q.generate(__ar, __ar + __r * __k); 3540 void generate(_RandomAccessIterator __first, _RandomAccessIterator __last); 3569 seed_seq::generate(_RandomAccessIterator __first, _RandomAccessIterator __last)
|
/ndk/sources/host-tools/make-3.81/doc/ |
D | make.info-1 | 144 * Automatic Prerequisites:: How to automatically generate rules giving 968 Another such occasion is when you want to generate prerequisites from 1600 * Automatic Prerequisites:: How to automatically generate rules giving 2485 assumes that these files are created by commands that generate low 2574 generate text.g -$(subst output,,$@) > $@ 2579 generate text.g -big > bigoutput 2581 generate text.g -little > littleoutput 2583 Here we assume the hypothetical program `generate' makes two types 2746 generate text.g -$* > $@ 2748 When the `generate' command is run, `$*' will expand to the stem, [all …]
|