| /external/clang/test/Modules/ |
| D | Rmodule-build.m | 13 @import A; // expected-remark{{building module 'A' as}} expected-remark {{finished building module …
14 @import B; // expected-remark{{building module 'B' as}} expected-remark {{finished building module …
35 // CHECK-NOT: building module 'A'
36 // CHECK: building module 'B'
37 // CHECK: building module 'C'
38 // CHECK: finished building module 'C'
39 // CHECK: finished building module 'B'
40 // NO-REMARKS-NOT: building module 'A'
41 // NO-REMARKS-NOT: building module 'B'
|
| D | build-fail-notes.m | 6 // CHECK: While building module 'DependsOnModule' imported from
7 // CHECK: While building module 'Module' imported from
25 // CHECK-SDIAG: build-fail-notes.m:4:9: note: while building module 'DependsOnModule' imported from
26 // CHECK-SDIAG: DependsOnModule.h:1:10: note: while building module 'Module' imported from
30 // CHECK-SDIAG: build-fail-notes.m:4:9: note: while building module 'DependsOnModule' imported from
|
| D | no-stale-modtime.m | 2 // building modules that depend on it.
28 // REBUILD-ALL: building module 'b'
29 // REBUILD-ALL: building module 'l'
30 // REBUILD-ALL: building module 't'
31 // REBUILD-ALL: building module 'r'
|
| /external/mesa3d/docs/ |
| D | install.html | 20 <li><a href="#prereq-general">Prerequisites for building</a>
25 <li><a href="#autoconf">Building with autoconf (Linux/Unix/X11)</a>
26 <li><a href="#scons">Building with SCons (Windows/Linux)</a>
27 <li><a href="#android">Building with AOSP (Android)</a>
29 <li><a href="#pkg-config">Building OpenGL programs with pkg-config</a>
33 <h1 id="prereq-general">1. Prerequisites for building</h1>
42 <li>Autoconf is required when building on *nix platforms.
43 <li><a href="http://www.scons.org/">SCons</a> is required for building on
46 <li>Android Build system when building as native Android component. Autoconf
47 is used when when building ARC.
[all …]
|
| /external/icu/icu4c/source/test/testdata/ |
| D | testdata.mak | 34 @echo Building test data
107 @echo Building $@
112 @echo Building $@
117 @echo Building $@
122 @echo Building $@
127 @echo Building $@
133 @echo Building $@
137 @echo Building $@
141 @echo Building $@
145 @echo Building $@
[all …]
|
| /external/vulkan-headers/ |
| D | BUILD.md | 3 Instructions for building this repository on Windows, Linux, and MacOS.
10 1. [Windows Build](#building-on-windows)
11 1. [Linux Build](#building-on-linux)
12 1. [MacOS Build](#building-on-macos)
30 If you are building other Vulkan-related repositories such as
68 ## Building On Windows
147 -- Building for: Visual Studio 14 2015
182 > solution, building the solution from the command line may be more efficient
185 ## Building On Linux
190 building this repository. The required tools are
[all …]
|
| /external/freetype/docs/ |
| D | INSTALL.CROSS | 2 library on Unix systems, for example, building binaries for Linux/MIPS
4 file `INSTALL.UNIX' for required tools and the basic self-building
11 For self-building the FreeType library on a Unix system, GNU Make
18 example, if your building system is FreeBSD/i386 and the target
30 2.1. Building and target system
66 cross-building system, the prefix is expected to be different
67 from the self-building system. For example, a configuration
121 3. Building command
148 should not be installed in the cross-building system. In such
161 Cross building between Cygwin (or MSys) and Unix must be tested.
|
| /external/swiftshader/third_party/llvm-7.0/llvm/docs/ |
| D | CMake.rst | 2 Building LLVM with CMake
13 (GNU make, Visual Studio, etc.) for building LLVM.
42 #. Create a build directory. Building LLVM in the source
58 generate the files required for building LLVM. CMake will use default values
83 #. After LLVM has finished building, install it from the build directory:
138 for building with NMake. By default, CMake chooses the most specific generator
213 Semicolon-separated list of targets to build, or *all* for building all
218 Build LLVM tools. Defaults to ON. Targets for building each tool are generated
232 Build LLVM examples. Defaults to OFF. Targets for building each example are
241 Build LLVM unit tests. Defaults to OFF. Targets for building each unit test
[all …]
|
| D | HowToBuildOnARM.rst | 8 This document contains information about building/testing LLVM and
15 Notes On Building LLVM/Clang on ARM
17 Here are some notes on building/testing LLVM/Clang on ARM. Note that
25 Building LLVM/Clang in ``Relese`` mode is preferred since it consumes
26 a lot less memory. Otherwise, the building process will very likely
52 #. If you are building LLVM/Clang on an ARM board with 1G of memory or less,
|
| /external/grpc-grpc/summerofcode/2018/ |
| D | naresh.md | 5 Enable Building of gRPC Python with Bazel
12 system, Blaze, which is an ideal replacement for building such projects in a
33 though. There's still challenges when it comes to building for Python 2 vs 3.
44 Cross contribution surprisingly came up because of building protobuf sources
56 ### Building Cython code
58 Building Cython code is still not supported by Bazel, but the team at
61 dependency and using custom Bazel rules for building our Cython code using the
69 by the contributors and developers for building and testing the gRPC code. But
72 ### Building gRPC Python with Bazel on Kokoro (internal CI)
95 operating system the code is building on. To make this easier, the folks at
[all …]
|
| /external/pcre/dist2/doc/html/ |
| D | NON-AUTOTOOLS-BUILD.txt | 1 Building PCRE2 without using autotools
12 Building PCRE2 on Windows with CMake
13 Building PCRE2 on Windows with Visual Studio
15 Building PCRE2 on native z/OS and z/VM
31 section entitled "Building PCRE2 on Windows with CMake" below.
41 The following are generic instructions for building the PCRE2 C library "by
78 the dftables command. You must use this method if you are building on a
211 COMMENTS ABOUT WIN32 BUILDS (see also "BUILDING PCRE2 ON WINDOWS WITH CMAKE")
213 There are two ways of building PCRE2 using the "configure, make, make install"
216 support for building using CMake, which some users find a more straightforward
[all …]
|
| /external/pcre/dist2/ |
| D | NON-AUTOTOOLS-BUILD | 1 Building PCRE2 without using autotools
12 Building PCRE2 on Windows with CMake
13 Building PCRE2 on Windows with Visual Studio
15 Building PCRE2 on native z/OS and z/VM
31 section entitled "Building PCRE2 on Windows with CMake" below.
41 The following are generic instructions for building the PCRE2 C library "by
78 the dftables command. You must use this method if you are building on a
211 COMMENTS ABOUT WIN32 BUILDS (see also "BUILDING PCRE2 ON WINDOWS WITH CMAKE")
213 There are two ways of building PCRE2 using the "configure, make, make install"
216 support for building using CMake, which some users find a more straightforward
[all …]
|
| /external/llvm/docs/ |
| D | CMake.rst | 2 Building LLVM with CMake
13 (GNU make, Visual Studio, etc.) for building LLVM.
42 #. Create a build directory. Building LLVM in the source
58 generate the files required for building LLVM. CMake will use default values
83 #. After LLVM has finished building, install it from the build directory:
138 for building with NMake. By default, CMake chooses the most specific generator
211 Semicolon-separated list of targets to build, or *all* for building all
216 Build LLVM tools. Defaults to ON. Targets for building each tool are generated
226 Build LLVM examples. Defaults to OFF. Targets for building each example are
235 Build LLVM unit tests. Defaults to OFF. Targets for building each unit test
[all …]
|
| D | HowToBuildOnARM.rst | 8 This document contains information about building/testing LLVM and
15 Notes On Building LLVM/Clang on ARM
17 Here are some notes on building/testing LLVM/Clang on ARM. Note that
25 Building LLVM/Clang in ``Relese`` mode is preferred since it consumes
26 a lot less memory. Otherwise, the building process will very likely
52 #. If you are building LLVM/Clang on an ARM board with 1G of memory or less,
|
| /external/python/cpython2/Doc/extending/ |
| D | building.rst | 7 Building C and C++ Extensions with distutils
14 building make files for building dynamically-linked extensions and custom
16 Makefile.pre.in, and Setup files) is no longer supported. Building custom
20 Building an extension module using distutils requires that distutils is
58 distutils; this section explains building extension modules only.
67 In many cases, building an extension is more complex, since additional
88 url = 'https://docs.python.org/extending/building',
|
| /external/libunwind/ |
| D | README | 24 $ autoreconf -i # Needed only for building from git. Depends on libtool.
35 * Building with Intel compiler
47 * Building on HP-UX
70 * Building for PowerPC64 / Linux
72 For building for power64 you should use:
88 * Building on FreeBSD
90 General building instructions apply. To build and execute several tests,
99 After building the library, you can run a set of regression tests with:
194 building the library, you can run these tests with the following
|
| /external/grpc-grpc/ |
| D | CONTRIBUTING.md | 17 Please follow the instructions in [Building gRPC C++: Clone the repository](BUILDING.md#clone-the-r…
19 ## Building & Running tests
23 script that unifies the experience of building and testing gRPC in different
29 …[Building gRPC C++: Prerequisites](BUILDING.md#pre-requisites). This is because gRPC implementatio…
35 - To also run all the unit tests after building
|
| /external/v8/src/compiler/ |
| D | schedule.h | 211 // BasicBlock building: create a new block. in NON_EXPORTED_BASE()
214 // BasicBlock building: records that a node will later be added to a block but in NON_EXPORTED_BASE()
218 // BasicBlock building: add a node to the end of the block. in NON_EXPORTED_BASE()
221 // BasicBlock building: add a goto to the end of {block}. in NON_EXPORTED_BASE()
224 // BasicBlock building: add a call at the end of {block}. in NON_EXPORTED_BASE()
228 // BasicBlock building: add a branch at the end of {block}. in NON_EXPORTED_BASE()
232 // BasicBlock building: add a switch at the end of {block}. in NON_EXPORTED_BASE()
236 // BasicBlock building: add a deoptimize at the end of {block}. in NON_EXPORTED_BASE()
239 // BasicBlock building: add a tailcall at the end of {block}. in NON_EXPORTED_BASE()
242 // BasicBlock building: add a return at the end of {block}. in NON_EXPORTED_BASE()
[all …]
|
| /external/grpc-grpc/src/cpp/ |
| D | README.md | 33 NOTE: currently bazel is only supported for building gRPC on Linux.
37 Currently the default choice for building on UNIX based systems is `make`.
39 To install gRPC for C++ on your system using `make`, follow the [Building gRPC C++](../../BUILDING.…
83 …tructions on how to build gRPC C++ from source, follow the [Building gRPC C++](../../BUILDING.md) …
|
| /external/python/cpython3/PCbuild/ |
| D | readme.txt | 13 Building Python using Microsoft Visual C++
23 Building from the command line is recommended in order to obtain any
32 win32 sub-directory. The x64 platform is used for building 64-bit AMD64
43 option for debug builds. If you are building Python to help with
57 Building Python using the build.bat script
61 building Python on Windows simpler. This script will use the env.bat
157 about getting the source for building these libraries. The sub-projects
175 Building OpenSSL requires Perl on your path, and can be performed by
184 again when building.
198 Building Tcl and Tk can be performed by running
|
| /external/vulkan-validation-layers/ |
| D | BUILD.md | 3 Instructions for building this repository on Linux, Windows, Android, and
11 1. [Windows Build](#building-on-windows)
12 1. [Linux Build](#building-on-linux)
13 1. [Android Build](#building-on-android)
14 1. [MacOS build](#building-on-macos)
73 building this repository. The Vulkan-Headers repository is required because it
76 directory and pass it on the CMake command line for building this repository,
88 of building glslang. You must also take note of the glslang install directory
89 and pass it on the CMake command line for building this repository, as
123 it on the CMake command line for building this repository, as described below.
[all …]
|
| /external/flac/ |
| D | config.h | 4 /* Define if building universal (internal helper macro) */
19 /* define if building for ia32/i386 */
22 /* define if building for PowerPC */
25 /* define if building for PowerPC with SPE ABI */
28 /* define if building for SPARC */
31 /* define if building for x86_64 */
49 /* define if building for Darwin / MacOS X */
52 /* define if building for Linux */
|
| /external/libogg/ |
| D | README | 34 ./debian Rules/spec files for building Debian .deb packages
51 BUILDING FROM REPOSITORY SOURCE:
66 BUILDING FROM TARBALL DISTRIBUTIONS:
74 BUILDING RPMS:
81 BUILDING ON WIN32:
115 BUILDING ON MACOS 9:
|
| /external/grpc-grpc-java/ |
| D | COMPILING.md | 1 Building gRPC-Java
4 Building is only necessary if you are making changes to gRPC-Java.
6 Building requires JDK 8, as our tests use TLS.
25 Building in IntelliJ works best when you import the project as a Gradle project and delegate IDE
57 environment variables will be used when building grpc-java.
81 When building on Windows and VC++, you need to specify project properties for
|
| /external/mesa3d/src/gallium/docs/source/drivers/openswr/ |
| D | usage.rst | 11 Building chapter
14 To build with GNU automake, select building the swr driver at
22 On Linux, building with autotools will create a drop-in alternative
29 Alternatively, building with SCons will produce::
|