Home
last modified time | relevance | path

Searched refs:built (Results 1 – 25 of 768) sorted by relevance

12345678910>>...31

/external/chromium_org/tools/gyp/tools/
Dpretty_sln.py22 def BuildProject(project, built, projects, deps): argument
27 if dep not in built:
28 BuildProject(dep, built, projects, deps)
30 built.append(project)
123 built = []
125 if project not in built:
126 BuildProject(project, built, projects, deps)
/external/clang/include/clang/Basic/
DDiagnosticSerializationKinds.td21 "file '%0' has been modified since the precompiled header '%1' was built">,
45 "PCH file built from a different branch (%0) than the compiler (%1)">;
60 "%select{command line contains|precompiled header was built with}0 "
61 "'-undef' but %select{precompiled header was not built with it|"
64 "%select{command line contains|precompiled header was built with}0 "
66 "built with it|it is not present on the command line}0">;
/external/chromium_org/third_party/icu/patches/
Ddata.build.win.patch13 +# ALL except that testdata.dat is not built.
17 + @echo Data library is built
23 …# They are not built by default but need to be built for ICU4J data and for getting the .c source …
/external/clang/test/SemaOpenCL/
Dvec_step.cl29 …int res13 = vec_step(*incomplete1); // expected-error {{'vec_step' requires built-in scalar or vec…
30 …int res14 = vec_step(int16*); // expected-error {{'vec_step' requires built-in scalar or vector ty…
31 …int res15 = vec_step(void(void)); // expected-error {{'vec_step' requires built-in scalar or vecto…
/external/elfutils/tests/
Dtest-wrapper.sh46 elfutils_testrun=built
55 if [ $elfutils_testrun = built ]; then
/external/stlport/doc/
DREADME.windows26 libraries built for Windows 95 cannot be used to generate an application
27 built for Windows XP for instance. So, if you build STLport with a Windows
33 with the libraries built for Windows 95.
42 if you are trying to use STLport libraries built for Windows 98 or later
45 if you are trying to use STLport libraries built for Windows 95 to generate
/external/mdnsresponder/Clients/
DReadMe.txt6 Some of the clients, like the "dns-sd" command-line tool, can be built
11 Some of the clients can be built more than one way. For example, the
12 "dns-sd" command-line tool can be built for OS X using both the XCode
/external/eigen/blas/
DREADME.txt2 This directory contains a BLAS library built on top of Eigen.
7 This module is not built by default. In order to compile it, you need to
/external/chromium_org/tools/gyp/test/win/compiler-flags/
Dtreat-wchar-t-as-built-in-type.gyp16 'treat-wchar-t-as-built-in-type1.cc',
28 'treat-wchar-t-as-built-in-type2.cc',
/external/chromium_org/native_client_sdk/src/
DREADME.naclports4 This folder contains headers and pre-built libraries for several
7 These libraries were built from the naclports project. For access
/external/chromium_org/third_party/mesa/src/docs/
DREADME.WIN3243 The DLL files are built so that the external entry points use the
46 Static LIB files are not built. The LIB files that are built with are
/external/mesa3d/docs/
DREADME.WIN3243 The DLL files are built so that the external entry points use the
46 Static LIB files are not built. The LIB files that are built with are
/external/chromium_org/net/spdy/
Dspdy_frame_builder_test.cc57 scoped_ptr<SpdyFrame> built(builder.take()); in TEST_P() local
59 base::StringPiece(built->data(), expected->size())); in TEST_P()
/external/chromium_org/chrome/app/
Dapp_asan.saves6 # helper app executables built with AddressSanitizer
11 # The list of symbols that should be preserved in all the binaries built with
/external/libpng/projects/visualc6/
DREADME.txt21 (Choose libpng or pngtest; zlib will be built automatically.)
28 5) If you built the sample program (pngtest),
53 All DLLs built by this project use the Microsoft dynamic C runtime library
/external/llvm/docs/CommandGuide/
Dllvm-config.rst61 Print the source root from which LLVM was built.
130 **--targets-built**
138 Print the build mode used when LLVM was built (e.g. Debug or Release)
/external/llvm/docs/
DProjects.rst194 This is a space separated list of subdirectories that should be built. They
195 will be built, one at a time, in the order specified.
199 This is a list of directories that can be built in parallel. These will be
200 built after the directories in DIRS have been built.
204 This is a list of directories that can be built if they exist, but will not
205 cause an error if they do not exist. They are built serially in the order
213 This variable contains the base name of the library that will be built. For
226 library will be built.
233 This variable contains the name of the program that will be built. For
302 The final location of built libraries and executables will depend upon whether
DMakefileGuide.rst46 quickly by utilizing the built-in features that are used to compile LLVM. LLVM
149 you can ask for a shared library (.so) or archive library (.a) built. Archive
225 directory. ``USEDLIBS`` refers to the libraries built by your project. In the
239 built with the ``ARCHIVE_LIBRARY`` option set.
267 This section describes each of the targets that can be built using the LLVM
279 ``clean`` \ Remove built objects recursively.
280 ``clean-local`` \ Remove built objects from the local directory only.
284 ``install`` ``all`` Copy built objects to installation directory.
288 ``uninstall`` \ Remove built objects from installation directory.
363 to make sure that the distributed tarball can actually be built into a working
[all …]
/external/chromium/testing/gtest/cmake/
Dinternal_utils.cmake28 # When Google Test is built as a shared library, it should also use
31 # hard-to-find crashes. When it is built as a static library, it is
142 # is built from the given source files with the given compiler flags.
164 # creates a named target that depends on the given libs and is built
177 # creates a named C++ test that depends on the given libs and is built
187 # built from the given source files. Unlike cxx_test_with_flags,
/external/valgrind/main/docs/internals/
Dmultiple-architectures.txt18 system is built in its entirety for the primary platform, including
24 respectively. The tools are built again for the secondary target, and
58 all the tools will be built. Similarly on a ppc64 system both
72 Each tool will then be built twice, along with any preload library
109 The launcher program (ie the valgrind binary itself) is always built
149 Most of them are architecture-neutral and so should be built for the
/external/valgrind/main/helgrind/
DREADME_YARD.txt2 YARD, Yet Another Race Detector, built on the Helgrind framework
19 be built as a standalone executable with test harness using "make -f
/external/chromium_org/native_client_sdk/src/libraries/third_party/pthreads-win32/
DREADME43 and pre-built forms). Currently this is a separate LGPL package to
62 Because the library is being built using various exception
70 built with a different compiler. If you use an EH version of
104 compatibility with applications built against
320 Versions built with MSVC++ later than version 6 may not be broken, but I
360 The pre-built dlls are normally built using the *-inlined targets.
386 The dll can be built easily with recent versions of Mingw32.
387 (The distributed versions are built using Mingw32 and MsysDTK
406 The pre-built dlls are normally built using the *-inlined targets.
488 pthreadVC.dll - built with MSVC compiler using C setjmp/longjmp
[all …]
/external/chromium/testing/gtest/
DCMakeLists.txt16 "Use shared (DLL) run-time lib even when Google Test is built as static lib."
78 # They are not built by default. To build them, set the
102 # The tests are not built by default. To build them, set the
112 # C++ tests built with standard compiler flags.
141 # C++ tests built with non-standard compiler flags.
/external/qemu/
DINSTALL6 The Android emulator can be built on the following platforms:
18 The Windows emulator binary is built using the -no-cygwin option
31 can only be built properly with a small number of compilers. Moreover,
67 Simply type 'emulator' to start it with the currently built system
/external/qemu/distrib/sdl-1.2.15/
DREADME.Watcom45 4) All tests from the test directory are working and can be built by
51 The makefile offers some options to tweak the way the library is built.
69 the way the tests are built as base of your own build environment.
71 The library can also be built with the stack calling convention of the

12345678910>>...31