| /external/python/google-api-python-client/docs/dyn/ |
| D | admin_directory_v1.resources.buildings.html | 82 <p class="firstline">Deletes a building.</p>
85 <p class="firstline">Retrieves a building.</p>
88 <p class="firstline">Inserts a building.</p>
97 <p class="firstline">Patches a building.</p>
100 <p class="firstline">Updates a building.</p>
109 <pre>Deletes a building.
113 buildingId: string, The id of the building to delete. (required)
123 <pre>Retrieves a building.
127 buildingId: string, The unique ID of the building to retrieve. (required)
137 …"address": { # Public API: Resources.buildings # The postal address of the building. See…
[all …]
|
| /external/tensorflow/third_party/mkl/ |
| D | build_defs.bzl | 3 if_mkl is a conditional to check if we are building with MKL.
4 if_mkl_ml is a conditional to check if we are building with MKL-ML.
7 if_enable_mkl is a conditional to check if building with MKL and MKL is enabled.
18 """Shorthand for select()'ing on whether we're building with oneDNN.
20 OneDNN gets built if we are building on platforms that support oneDNN
24 if_true: expression to evaluate if building with oneDNN.
25 if_false: expression to evaluate if building without oneDNN.
42 """Shorthand for select()'ing on whether we're building with MKL-ML.
45 if_true: expression to evaluate if building with MKL-ML.
46 if_false: expression to evaluate if building without MKL-ML
[all …]
|
| /external/python/cffi/c/ |
| D | cdlopen.c | 122 char *ffiname = "?", *types = NULL, *building = NULL; in ffiobj_init() local
160 building = PyMem_Malloc(n * sizeof(_cffi_opcode_t)); in ffiobj_init()
161 if (building == NULL) in ffiobj_init()
163 ntypes = (_cffi_opcode_t *)building; in ffiobj_init()
171 building = NULL; in ffiobj_init()
183 building = PyMem_Malloc(i); in ffiobj_init()
184 if (building == NULL) in ffiobj_init()
186 memset(building, 0, i); in ffiobj_init()
187 nglobs = (struct _cffi_global_s *)building; in ffiobj_init()
216 building = NULL; in ffiobj_init()
[all …]
|
| /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'
|
| /external/mesa3d/docs/ |
| D | install.rst | 10 1. Prerequisites for building
19 - `Meson <https://mesonbuild.com>`__ is required when building on \*nix
21 - `SCons <http://www.scons.org/>`__ is an alternative for building on
23 - Android Build system when building as native Android component. Meson
24 is used when when building ARC.
34 - Microsoft Visual Studio 2015 or later is required, for building on
41 building with SCons 2.7 is required. When building with meson 3.5 or
45 - lex / yacc - for building the Mesa IR and GLSL compiler.
81 2. Building with meson
108 3. Building with SCons (Windows/Linux)
[all …]
|
| /external/cronet/net/cert/pki/ |
| D | path_builder.h | 87 // path building.
91 // This is called during path building on candidate paths which have already
94 // building by adding high severity errors.
98 // This is called during path building in between attempts to build candidate
99 // paths. Delegates can cause path building to stop and return indicating
104 // Checks whether a certificate is trusted by building candidate paths to trust
112 // Provides the overall result of path building. This includes the paths that
145 // The iteration count reached by path building.
148 // The max depth seen while path building.
170 // path building to verify specific parts of certificates or the
[all …]
|
| /external/gfxstream-protocols/registry/vulkan/ |
| D | BUILD.adoc | 21 [[building]] anchor
22 == Building The Spec
73 <<building-extensions, below>>, simplifies this process for common
83 Building the `validusage` target will fail otherwise.
100 <<building-diff,Diff spec>>::
122 [[building-versions]]
123 === Building Specifications For Different API Versions
125 The `Makefile` defaults to building a Vulkan 1.2 specification.
137 [[building-extensions]]
138 === Building With Extensions Included
[all …]
|
| /external/tensorflow/third_party/gpus/cuda/ |
| D | build_defs.bzl.tpl | 1 # Macros for building CUDA code.
3 """Shorthand for select()'ing on whether we're building with CUDA.
5 Returns a select statement which evaluates to if_true if we're building
15 """Shorthand for select()'ing on wheteher we're building with cuda-clang.
17 Returns a select statement which evaluates to if_true if we're building
27 """Shorthand for select()'ing on wheteher we're building with cuda-clang
30 Returns a select statement which evaluates to if_true if we're building
58 Unlike if_cuda(), this does not require that we are building with
|
| /external/rust/crates/protobuf/src/reflect/service/ |
| D | index.rs | 4 use crate::reflect::file::building::FileDescriptorBuilding;
14 building: &FileDescriptorBuilding, in index()
19 .map(|method| MethodIndex::index(method, building)) in index()
34 building: &FileDescriptorBuilding, in index()
36 let input_type = building.resolve_message(proto.input_type())?; in index()
37 let output_type = building.resolve_message(proto.output_type())?; in index()
|
| /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/rust/crates/grpcio-sys/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/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/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
79 ## Building On Windows
161 -- Building for: Visual Studio 14 2015
189 ## Building On Linux
194 building this repository. The required tools are
263 ## Building on MacOS
[all …]
|
| /external/rust/crates/grpcio-sys/grpc/src/cpp/ |
| D | README.md | 36 `cmake` is your best option if you cannot use bazel. It supports building on Linux,
41 To build gRPC C++ from source, follow the [BUILDING guide](../../BUILDING.md).
90 [install the prerequisites](../../BUILDING.md#pre-requisites)
91 before building gRPC.
127 The default choice for building on UNIX based systems used to be `make`, but we are no longer recom…
130 To install gRPC for C++ on your system using `make`, follow the [Building gRPC C++](../../BUILDING.…
180 …tructions on how to build gRPC C++ from source, follow the [Building gRPC C++](../../BUILDING.md) …
|
| /external/rust/crates/grpcio-sys/grpc/ |
| D | BUILDING.md | 1 gRPC C++ - Building from source
46 *Tip*: when building,
66 Before building, you need to clone the gRPC github repository and download submodules containing so…
86 …rent model for dependencies. You only need to worry about downloading submodules if you're building
93 we recommend building using `bazel` or `cmake`.
95 ## Building with bazel (recommended)
102 We support building with `bazel` on Linux, MacOS and Windows.
118 ## Building with CMake
165 ### Windows: A note on building shared libs (DLLs)
169 That said, we don't actively prohibit building DLLs on windows (it can be enabled in cmake with `-D…
[all …]
|
| /external/conscrypt/ |
| D | BUILDING.md | 1 Building Conscrypt
38 [prerequisites](https://boringssl.googlesource.com/boringssl/+/HEAD/BUILDING.md#Build-Prerequisites…
53 ##### Building on Linux
65 ##### Building on macOS.
66 When building Conscrypt on macOS it will build libraries for both x86 and ARM, and so BoringSSL
94 ##### Building on Windows
100 environment variable to simplify building from the command line. The
|
| /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 …]
|
| /external/rust/crates/protobuf/src/reflect/field/ |
| D | index.rs | 9 use crate::reflect::file::building::FileDescriptorBuilding;
110 building: &FileDescriptorBuilding, in enum_default_value()
112 let en = building.find_enum(field.type_name()); in enum_default_value()
129 building: &FileDescriptorBuilding, in parse_default_value()
139 return Self::enum_default_value(field, building); in parse_default_value()
152 building: &FileDescriptorBuilding, in index()
155 Some(Self::parse_default_value(&field, building)?) in index()
167 Some(building.resolve_message(field.extendee())?) in index()
178 let field_type = building.resolve_field_type(&field)?; in index()
|
| /external/pcre/ |
| 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
88 are building on a system that uses EBCDIC code.
226 COMMENTS ABOUT WIN32 BUILDS (see also "BUILDING PCRE2 ON WINDOWS WITH CMAKE")
228 There are two ways of building PCRE2 using the "configure, make, make install"
231 support for building using CMake, which some users find a more straightforward
[all …]
|
| /external/pcre/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
88 are building on a system that uses EBCDIC code.
226 COMMENTS ABOUT WIN32 BUILDS (see also "BUILDING PCRE2 ON WINDOWS WITH CMAKE")
228 There are two ways of building PCRE2 using the "configure, make, make install"
231 support for building using CMake, which some users find a more straightforward
[all …]
|
| /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/mesa3d/docs/relnotes/ |
| D | 17.1.2.rst | 71 - configure: error out when building GLX w/o the X11 platform
74 - configure: error out when building X11 Vulkan without DRI3
75 - auxiliary/vl: use vl_*_screen_create stubs when building w/o platform
78 - st/omx: fix building against X11-less setups
80 - configure: error out if building VA w/o supported platform
81 - configure: error out if building OMX w/o supported platform
82 - configure: error out if building VDPAU w/o supported platform
83 - configure: error out if building XVMC w/o supported platform
|
| /external/angle/doc/ |
| D | DevSetup.md | 13 Note: If you are building inside a Chromium checkout [see these instructions instead](https://chrom…
59 If building for Android (which requires Linux), switch to the [Android steps](https://chromium.goog…
108 ### Building with Goma (Google employees only)
118 ### Building and Debugging with Visual Studio
133 ### Building ANGLE for Android
178 …` and `libGLESv2.lib` found in the build output directory (see [Building ANGLE](#building-with-vis…
183 ….dll` and `libGLESv2.dll` from the build output directory (see [Building ANGLE](#building-with-vis…
199 ### Source and Building
203 [getting and building ANGLE](#getting-the-source) to build the translator on
|
| /external/harfbuzz_ng/docs/ |
| D | usermanual-install-harfbuzz.xml | 39 <section id="building">
40 <title>Building HarfBuzz</title>
42 <section id="building.linux">
43 <title>Building on Linux</title>
60 are building from the source in a downloaded release tarball or
80 <emphasis>(2)(b)</emphasis> If you are building from the source in the HarfBuzz git
100 <section id="building.windows">
101 <title>Building on Windows</title>
113 <section id="building.macos">
114 <title>Building on macOS</title>
[all …]
|
| /external/exoplayer/tree_15dc86382f17a24a3e881e52e31a810c1ea44b49/docs/ |
| D | drm.md | 18 [when building a media item]({{ site.baseurl }}/media-items.html#protected-content).
27 `MediaItem.DrmConfiguration.Builder.setMultiSession` when building the media
54 `MediaItem.DrmConfiguration.Builder.setMultiSession` when building the media
64 `MediaItem.DrmConfiguration.Builder.setKeySetId` when building the media item.
82 building the media item.
88 `MediaSource.Factory` which is [used when building the player]. The provider can
104 [used when building the player]: {{ site.baseurl }}/media-sources.html#customizing-media-source-cre…
|