| /external/cldr/docs/site/ |
| D | sitemap.tsv | 123 development
124 development/getting-started
125 development/cldr-development-site
126 development/development-process
127 development/new-cldr-developers
128 development/guidance-on-direct-modifications-to-cldr-data
129 development/maven
130 development/creating-the-archive
131 development/tests-and-tools
132 development/running-tests
[all …]
|
| /external/cldr/docs/site/development/development-process/ |
| D | design-proposals.md | 9 …cture in [Proposed Collation Additions](https://cldr.unicode.org/development/development-process/d…
11 [Alternate Time Formats](https://cldr.unicode.org/development/development-process/design-proposals/…
13 [BCP 47 Changes (DRAFT)](https://cldr.unicode.org/development/development-process/design-proposals/…
15 [BCP47 Syntax Mapping](https://cldr.unicode.org/development/development-process/design-proposals/bc…
17 [BCP47 Validation and Canonicalization](https://cldr.unicode.org/development/development-process/de…
19 [BIDI handling of Structured Text](https://cldr.unicode.org/development/development-process/design-…
21 [Change to Sites?](https://cldr.unicode.org/development/development-process/design-proposals/change…
23 …pport, intercalary months, year cycles](https://cldr.unicode.org/development/development-process/d…
25 [Consistent Casing](https://cldr.unicode.org/development/development-process/design-proposals/consi…
27 [Coverage Revision](https://cldr.unicode.org/development/development-process/design-proposals/cover…
[all …]
|
| /external/openthread/third_party/mbedtls/repo/docs/ |
| D | psa-transition.md | 24 …sa/crypto*.h` headers](https://mbed-tls.readthedocs.io/projects/api/en/development/api/file/crypto…
51 …MBEDTLS_PSA_CRYPTO_C`](https://mbed-tls.readthedocs.io/projects/api/en/development/api/file/mbedtl…
53 …EDTLS_USE_PSA_CRYPTO`](https://mbed-tls.readthedocs.io/projects/api/en/development/api/file/mbedtl…
66 …ll [`psa_crypto_init`](https://mbed-tls.readthedocs.io/projects/api/en/development/api/group/group…
68 …dtls_psa_crypto_free`](https://mbed-tls.readthedocs.io/projects/api/en/development/api/file/crypto…
76 …development/api/group/group__error/#group__error_1ga05676e70ba5c6a7565aff3c36677c1f9): `PSA_SUCCES…
88 … type [`psa_key_id_t`](https://mbed-tls.readthedocs.io/projects/api/en/development/api/file/crypto…
92 …development/api/group/group__import__export/#group__import__export_1ga0336ea76bf30587ab204a8296462…
94 …th [`psa_destroy_key`](https://mbed-tls.readthedocs.io/projects/api/en/development/api/group/group…
98 …development/api/group/group__import__export/#group__import__export_1ga668e35be8d2852ad3feeef74ac6f…
[all …]
|
| /external/cldr/docs/site/development/ |
| D | cldr-development-site.md | 2 title: CLDR Development Site
5 # CLDR Development Site
9 1. [New CLDR Developers](https://cldr.unicode.org/development/new-cldr-developers)
10 1. [Maven Setup](https://cldr.unicode.org/development/maven) (for command line & Eclipse)
11 … still contain useful nuggets): [Eclipse Setup](https://cldr.unicode.org/development/eclipse-setup)
12 …2. [Eclipse](https://cldr.unicode.org/development/running-survey-tool/building-and-running-the-sur…
13 2. [Handling Tickets (bugs/enhancements)](https://cldr.unicode.org/development/development-process)
14 3. [Updating DTDs](https://cldr.unicode.org/development/updating-dtds)
15 4. [Editing CLDR Spec](https://cldr.unicode.org/development/editing-cldr-spec)
16 …1. [CLDR: Big Red Switch](https://cldr.unicode.org/development/cldr-big-red-switch) (checklist for…
[all …]
|
| D | updating-codes.md | 11 First read [Running Tools](https://cldr.unicode.org/development/running-tools)
13 1. Update [Script Metadata](https://cldr.unicode.org/development/updating-codes/updating-script-met…
14 2. [Update Population/GDP/Literacy](https://cldr.unicode.org/development/updating-codes/updating-po…
15 3. [Update Language/Script/Region Subtags](https://cldr.unicode.org/development/updating-codes/upda…
16 4. [Update Subdivision Codes](https://cldr.unicode.org/development/updating-codes/updating-subdivis…
17 5. [Update Subdivision translations](https://cldr.unicode.org/development/updating-codes/updating-s…
18 6. [Update Currency Codes](https://cldr.unicode.org/development/updating-codes/update-currency-code…
19 7. [Update Time Zone Data for ZoneParser](https://cldr.unicode.org/development/updating-codes/updat…
20 8. [Update Validity XML](https://cldr.unicode.org/development/updating-codes/update-validity-xml)
21 …1. [Update Language/Script/Country Information](https://cldr.unicode.org/development/updating-code…
[all …]
|
| D | new-cldr-developers.md | 7 Here is a quick overview of what you need to know to do development work on CLDR.
23 1. http://cldr.unicode.org/development/eclipse-setup
24 2. http://cldr.unicode.org/development/running-survey-tool/eclipse
45 1. Go [here](https://cldr.unicode.org/development/eclipse-setup%23TOC-Test)
47 Once you are all set up, be sure to read the development process, for how to handle tickets, when y…
49 at: http://cldr.unicode.org/development/development-process (TBD update for migration to Jira/Githu…
55 …a over to ICU by editing ldml2icu_locale.txt | http://cldr.unicode.org/development/coding-cldr-too…
56 | performance work | http://cldr.unicode.org/development/perf-testing |
57 | survey tool database work | http://cldr.unicode.org/development/running-survey-tool/cldr-properti…
59 Other useful pages are under [CLDR Development Site](https://cldr.unicode.org/development/cldr-deve…
|
| D | creating-the-archive.md | 9 - [Generating Charts](https://cldr.unicode.org/development/cldr-big-red-switch/generating-charts)
10 - [Update Validity XML](https://cldr.unicode.org/development/updating-codes/update-validity-xml)
11 - [Updating English/Root](https://cldr.unicode.org/development/cldr-development-site/updating-engli…
23 … In other words, if your [CLDR\_DIR](https://cldr.unicode.org/development/cldr-development-site/ru…
41 - Also update **DEV\_VERSION** to "43" (the next development version)
54 
|
| /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/ |
| D | overview.rst | 13 Our goal is to make embedded software development efficient, robust, and
17 Embedded software development is notoriously arcane. Developers often have to
27 hardware the framework supports, and you get an efficient embedded development
40 Pigweed provides four foundational pillars to support your embedded development:
42 … :ref:`A comprehensive set of libraries for embedded development<docs-concepts-embedded-developmen…
43 * :ref:`A hermetic and replicable development environment<docs-concepts-development-environment>`
47 .. _docs-concepts-embedded-development-libraries:
49 Embedded Development Libraries
51 Pigweed enables you to use modern C++ and software development best practices in
66 .. _docs-concepts-development-environment:
[all …]
|
| /external/pigweed/pw_ide/design/ |
| D | projects.rst | 12 * Bootstrap projects, in which a development environment is populated by
17 * Bazel projects, in which Bazel is the build system, Bazel manages development
38 * Development tools and dependences are located in an ``environment`` directory.
46 * Access to the development environment is provided through mutations to the
49 configure the development environment.
52 with development tools and dependencies, and modifies the environment of the
53 shell in which the script was run to provide access to the development
58 environment required to provide access to the development environment.
62 Assuming the environment has already been bootstrapped, exposing the development
92 * Development tools and dependences are managed by Bazel. There are multiple
[all …]
|
| /external/webrtc/docs/native-code/ |
| D | index.md | 33 * [Development][webrtc-development]
34 * [Android][webtc-android-development]
35 * [iOS][webrtc-ios-development]
38 [webrtc-prerequitite-sw]: https://webrtc.googlesource.com/src/+/main/docs/native-code/development/p…
39 [webrtc-development]: https://webrtc.googlesource.com/src/+/main/docs/native-code/development/index…
40 [webtc-android-development]: https://webrtc.googlesource.com/src/+/main/docs/native-code/android/in…
41 [webrtc-ios-development]: https://webrtc.googlesource.com/src/+/main/docs/native-code/ios/index.md
|
| /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/coreboot/Documentation/soc/intel/code_development_model/ |
| D | code_development_model.md | 1 # Intel common code development strategy
5 This document captures the development strategy for Intel SOC code development
6 of coreboot. As Intel keeps advancing hardware development and as new generation
34 "converged IP model" was propsed as the new firmware development model to create
36 future SoCs. This will make development much simpler by using those common APIs
39 ## Common Code Development and Status
46 SoC development model,the PCH has been made into a separate component for the
72 | 1.1 |Create PCH binding for big core SoCs. SoCs |In development|
76 | 2.0 |Use common stage files (bootblock, romstage) |In development|
92 development continues.
|
| /external/crosvm/docs/book/src/building_crosvm/ |
| D | linux.md | 14 ## Setting up the development environment
30 Crosvm development best works on Debian derivatives. We provide a script to install the necessary
38 [Using the development container](#using-the-development-container).
40 ### Using the development container
65 `./target/debug/crosvm`. In case you are using development container, the executable will be inside
73 ## Development section in Building Crosvm on Linux
136 [development container](#using-the-development-container), which will have everything configured.
138 Note: Cross-compilation is **not supported on gLinux**. Please use the development container.
186 cross-compiling inside development container, the executable would be inside dev container at
|
| /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/development/ |
| D | index.md | 1 # WebRTC development
4 iOS. See the [Android][webrtc-android-development] and [iOS][webrtc-ios-development]
12 [webrtc-prerequisite-sw]: https://webrtc.googlesource.com/src/+/main/docs/native-code/development/p…
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
108 platform specific tips on the [Android][webrtc-android-development] and
109 [iOS][webrtc-ios-development] instructions.
193 [contributing]: https://webrtc.googlesource.com/src/+/refs/heads/main/docs/native-code/development/…
281 [webrtc-android-development]: https://webrtc.googlesource.com/src/+/main/docs/native-code/android/i…
[all …]
|
| /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
88 The Python Development Mode does not enable the :mod:`tracemalloc` module by
95 The Python Development Mode does not prevent the :option:`-O` command line
99 The Python Development Mode can only be enabled at the Python startup. Its
135 Enabling the Python Development Mode displays a :exc:`ResourceWarning` warning:
[all …]
|
| /external/tensorflow/tensorflow/lite/g3doc/android/ |
| D | index.md | 101 [runtime environment](#runtime) and [development
103 model, make sure to review the [Advanced development
124 Lite development libraries to your app development environment. For information
129 ### Development APIs and libraries {:#apis}
154 library](./development#lite_lib). Alternatively, you can include [Google Play
159 The [TensorFlow Lite Support library](./development#support_lib) is also
165 [Development tools for Android](./development).
221 ## Advanced development paths {:#adv_development}
224 need to use more advanced development approaches than what is described above.
251 about this development option, see the
[all …]
|
| /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/aws-sdk-java-v2/docs/design/ |
| D | README.md | 5 **In Development**
7 *Development on these features has started. No date can be shared for
16 *These features are being proposed for development. These features will
17 either transition to "In Development" when development begins, or
33 *These features are considered "mostly implemented". Development on new features
|
| /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 [webrtc-prerequisite-sw]: https://webrtc.googlesource.com/src/+/main/docs/native-code/development/p…
158 [webrtc-development]: https://webrtc.googlesource.com/src/+/main/docs/native-code/development/index…
|
| /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/webrtc/docs/native-code/ios/ |
| D | index.md | 1 # WebRTC iOS development
3 ## Development Environment
8 A macOS machine is required for iOS development. While it's possible to
25 for both Mac and iOS development, since GN allows you to generate your
39 See [Development][webrtc-development] for generic instructions on how
182 [webrtc-prerequisite-sw]: https://webrtc.googlesource.com/src/+/main/docs/native-code/development/p…
183 [webrtc-development]: https://webrtc.googlesource.com/src/+/main/docs/native-code/development/index…
|
| /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.
|