| /external/libwebsockets/READMEs/ |
| D | README.release-policy.md | 12 backported from the development branch. So you should not consume tags like
24 ## Development section in lws release policy
30 usable shape. See "Why no history on development" below for why it's managed like
45 This fetches current remote development branch into local branch `m`, and then forces your
48 to pop them before updating your basis against lws development.
52 Master is very useful for coordinating development, and integrating WIP,
54 more desirable than the latest development work.
56 Periodically, when development seems in good shape and various new developments seem
59 
63 (At that time, development's logical version is set to "...99", eg, `v4.0.99` so
[all …]
|
| /external/pigweed/docs/concepts/ |
| D | index.rst | 9 Our goal is to make embedded software development efficient, robust, and
13 Embedded software development is notoriously arcane. Developers often have to
23 hardware the framework supports, and you get an efficient embedded development
36 Pigweed provides four foundational pillars to support your embedded development:
38 … :ref:`A comprehensive set of libraries for embedded development<docs-concepts-embedded-developmen…
39 * :ref:`A hermetic and replicable development environment<docs-concepts-development-environment>`
43 .. _docs-concepts-embedded-development-libraries:
45 Embedded Development Libraries
47 Pigweed enables you to use modern C++ and software development best practices in
62 .. _docs-concepts-development-environment:
[all …]
|
| /external/webrtc/docs/native-code/ |
| D | index.md | 33 * [Development][webrtc-development]
34 * [Android][webtc-android-development]
35 * [iOS][webrtc-ios-development]
38 …tps://webrtc.googlesource.com/src/+/refs/heads/master/docs/native-code/development/prerequisite-sw…
39 [webrtc-development]: https://webrtc.googlesource.com/src/+/refs/heads/master/docs/native-code/deve…
40 [webtc-android-development]: https://webrtc.googlesource.com/src/+/refs/heads/master/docs/native-co…
41 [webrtc-ios-development]: https://webrtc.googlesource.com/src/+/refs/heads/master/docs/native-code/…
|
| /external/apache-xml/src/main/java/org/apache/xalan/processor/ |
| D | XSLProcessorVersion.src | 83 * development drop for a release.
88 * Development Drop Number.
89 * Optional identifier designates development drop of
90 * a specific release. D01 is the first development drop
93 * Development drops are works in progress towards a
94 * compeleted, final release. A specific development drop
96 * feature, which may take several development drops to
104 public static final int DEVELOPMENT = 0;
113 +(DEVELOPMENT > 0 ? ("D"+DEVELOPMENT)
|
| /external/webrtc/docs/native-code/development/ |
| D | index.md | 1 # WebRTC development
4 iOS. See the [Android][webrtc-android-development] and [iOS][webrtc-ios-development]
12 …tps://webrtc.googlesource.com/src/+/refs/heads/master/docs/native-code/development/prerequisite-sw…
17 For desktop development:
51 See the [Android][webrtc-android-development] and [iOS][webrtc-ios-development] pages for separate …
72 See the [Android][webrtc-android-development] and [iOS][webrtc-ios-development] pages for build
102 platform specific tips on the [Android][webrtc-android-development] and
103 [iOS][webrtc-ios-development] instructions.
259 [webrtc-android-development]: https://webrtc.googlesource.com/src/+/refs/heads/master/docs/native-c…
260 [webrtc-ios-development]: https://webrtc.googlesource.com/src/+/refs/heads/master/docs/native-code/…
|
| /external/crosvm/docs/book/src/building_crosvm/ |
| D | linux.md | 11 ## Setting up the development environment
27 Crosvm development best works on Debian derivatives. First install rust via https://rustup.rs/. Then
35 [Using the development container](#using-the-development-container).
55 [Using the development container](#using-the-development-container).
64 ### Using the development container
93 ## Development section in Building for Linux
95 ### Iterative development
97 You can use cargo as usual for crosvm development to `cargo build` and `cargo test` single crates
|
| /external/python/cpython3/Doc/library/ |
| D | devmode.rst | 3 Python Development Mode
8 The Python Development Mode introduces additional runtime checks that are too
18 Effects of the Python Development Mode
21 Enabling the Python Development Mode is similar to the following command, but
26 Effects of the Python Development Mode:
57 To enable the Python Development Mode without installing debug hooks on
87 The Python Development Mode does not enable the :mod:`tracemalloc` module by
94 The Python Development Mode does not prevent the :option:`-O` command line
98 The Python Development Mode can only be enabled at the Python startup. Its
134 Enabling the Python Development Mode displays a :exc:`ResourceWarning` warning:
[all …]
|
| /external/brotli/python/ |
| D | README.md | 6 We provide a `Makefile` to simplify common development commands.
20 ### Development subsection
32 "[development mode][]":
34 $ make develop # Install the module in "development mode"
51 [development mode]: https://setuptools.readthedocs.io/en/latest/setuptools.html#development-mode
|
| /external/webrtc/docs/native-code/android/ |
| D | index.md | 1 # WebRTC Android development
5 Android development is only supported on Linux.
19 The same checkout can be used for both Linux and Android development since you
23 See [Development][webrtc-development] for instructions on how to update
153 …tps://webrtc.googlesource.com/src/+/refs/heads/master/docs/native-code/development/prerequisite-sw…
158 [webrtc-development]: https://webrtc.googlesource.com/src/+/refs/heads/master/docs/native-code/deve…
|
| /external/python/setuptools/docs/userguide/ |
| D | development_mode.rst | 1 "Development Mode"
8 change to it during development.
11 need to do development on two related projects at the same time. You may need
32 script directory that will run your in-development scripts after ensuring that
37 doing development work.
39 When you're done with a given development task, you can remove the project
|
| /external/apache-xml/src/main/java/org/apache/xml/serializer/ |
| D | Version.java | 115 * development drop for a release.
123 * Development Drop Number.
124 * Optional identifier designates development drop of
125 * a specific release. D01 is the first development drop
128 * Development drops are works in progress towards a
129 * compeleted, final release. A specific development drop
131 * feature, which may take several development drops to
|
| D | Version.src | 115 * development drop for a release.
123 * Development Drop Number.
124 * Optional identifier designates development drop of
125 * a specific release. D01 is the first development drop
128 * Development drops are works in progress towards a
129 * compeleted, final release. A specific development drop
131 * feature, which may take several development drops to
|
| /external/jacoco/org.jacoco.doc/docroot/doc/ |
| D | environment.html | 8 <title>JaCoCo - Development Environment</title>
15 <span class="el_source">Development Environment</span>
19 <h1>Development Environment</h1>
44 JaCoCo development is done with the latest version of
97 <h3>Development Build Artifacts</h3>
102 development cycle:
125 The development team communicates through a mailing list. The list is closed
129 with the development team.
|
| /external/OpenCL-CTS/test_common/ |
| D | config.hpp | 19 // Enable development options for OpenCL C++ tests (test_conformance/clpp)
20 // #define DEVELOPMENT
21 #if defined(CLPP_DEVELOPMENT_OPTIONS) && !defined(DEVELOPMENT)
22 #define DEVELOPMENT macro
25 #ifdef DEVELOPMENT
|
| /external/apache-xml/src/main/java/org/apache/xalan/ |
| D | Version.src | 118 * development drop for a release.
126 * Development Drop Number.
127 * Optional identifier designates development drop of
128 * a specific release. D01 is the first development drop
131 * Development drops are works in progress towards a
132 * compeleted, final release. A specific development drop
134 * feature, which may take several development drops to
|
| D | Version.java | 118 * development drop for a release.
126 * Development Drop Number.
127 * Optional identifier designates development drop of
128 * a specific release. D01 is the first development drop
131 * Development drops are works in progress towards a
132 * compeleted, final release. A specific development drop
134 * feature, which may take several development drops to
|
| /external/webrtc/docs/native-code/ios/ |
| D | index.md | 1 # WebRTC iOS development
3 ## Development Environment
9 A macOS machine is required for iOS development. While it's possible to
26 for both Mac and iOS development, since GN allows you to generate your
40 See [Development][webrtc-development] for generic instructions on how
188 …tps://webrtc.googlesource.com/src/+/refs/heads/master/docs/native-code/development/prerequisite-sw…
189 [webrtc-development]: https://webrtc.googlesource.com/src/+/refs/heads/master/docs/native-code/deve…
|
| /external/guice/core/src/com/google/inject/ |
| D | Guice.java | 25 * <p>Guice supports a model of development that draws clear boundaries between APIs,
54 * #createInjector(Stage, Module...)} with Stage.DEVELOPMENT.
64 * #createInjector(Stage, Iterable)} with Stage.DEVELOPMENT.
69 return createInjector(Stage.DEVELOPMENT, modules); in createInjector()
73 * Creates an injector for the given set of modules, in a given development stage.
82 * Creates an injector for the given set of modules, in a given development stage.
|
| /external/python/cryptography/docs/development/custom-vectors/ |
| D | hkdf.rst | 13 .. literalinclude:: /development/custom-vectors/hkdf/generate_hkdf.py
16 </development/custom-vectors/hkdf/generate_hkdf.py>`
24 .. literalinclude:: /development/custom-vectors/hkdf/verify_hkdf.go
28 </development/custom-vectors/hkdf/verify_hkdf.go>`
|
| D | arc4.rst | 15 .. literalinclude:: /development/custom-vectors/arc4/generate_arc4.py
18 </development/custom-vectors/arc4/generate_arc4.py>`
26 .. literalinclude:: /development/custom-vectors/arc4/verify_arc4.go
30 </development/custom-vectors/arc4/verify_arc4.go>`
|
| D | secp256k1.rst | 15 .. literalinclude:: /development/custom-vectors/secp256k1/generate_secp256k1.py
18 </development/custom-vectors/secp256k1/generate_secp256k1.py>`
27 .. literalinclude:: /development/custom-vectors/secp256k1/verify_secp256k1.py
30 </development/custom-vectors/secp256k1/verify_secp256k1.py>`
|
| D | seed.rst | 15 .. literalinclude:: /development/custom-vectors/seed/generate_seed.py
18 </development/custom-vectors/seed/generate_seed.py>`
27 .. literalinclude:: /development/custom-vectors/seed/verify_seed.py
30 </development/custom-vectors/seed/verify_seed.py>`
|
| D | cast5.rst | 16 .. literalinclude:: /development/custom-vectors/cast5/generate_cast5.py
19 </development/custom-vectors/cast5/generate_cast5.py>`
27 .. literalinclude:: /development/custom-vectors/cast5/verify_cast5.go
31 </development/custom-vectors/cast5/verify_cast5.go>`
|
| D | idea.rst | 15 .. literalinclude:: /development/custom-vectors/idea/generate_idea.py
18 </development/custom-vectors/idea/generate_idea.py>`
27 .. literalinclude:: /development/custom-vectors/idea/verify_idea.py
30 </development/custom-vectors/idea/verify_idea.py>`
|
| /external/libxml2/ |
| D | CMakeLists.txt | 82 find_package(Python COMPONENTS Interpreter Development REQUIRED)
84 find_package(Python2 COMPONENTS Interpreter Development REQUIRED)
512 …FILES ${LIBXML2_HDRS} DESTINATION ${CMAKE_INSTALL_INCLUDEDIR}/libxml2/libxml COMPONENT development)
517 ARCHIVE DESTINATION ${CMAKE_INSTALL_LIBDIR} COMPONENT development
518 LIBRARY DESTINATION ${CMAKE_INSTALL_LIBDIR} COMPONENT runtime NAMELINK_COMPONENT development
639 ARCHIVE DESTINATION ${LIBXML2_PYTHON_INSTALL_DIR} COMPONENT development
640 LIBRARY DESTINATION ${LIBXML2_PYTHON_INSTALL_DIR} COMPONENT runtime NAMELINK_COMPONENT development
663 COMPONENT development
675 COMPONENT development
683 COMPONENT development
[all …]
|