| /external/libwebsockets/READMEs/ |
| D | README.release-policy.md | 10 The stable releases go on to a branch like v4.0-stable as described below, over
12 backported from the development branch. So you should not consume tags like
13 v4.0.0 but build into your planning that you will need to follow v4.0-stable in
24 ## Development section in lws release policy
27 subject to history rewrites, patches moving about and being squashed etc. In
29 runtime tests, so if it is passing CI as it usually is then it's probably in
30 usable shape. See "Why no history on development" below for why it's managed like
33 
42 $ git fetch https://libwebsockets.org/repo/libwebsockets +main:m && git reset --hard m
45 This fetches current remote development branch into local branch `m`, and then forces your
[all …]
|
| /external/pigweed/docs/ |
| D | overview.rst | 1 .. _docs-overview:
11 See our :ref:`docs-mission` for more details.
13 Our goal is to make embedded software development efficient, robust, and
15 to commercial products selling in the millions.
17 Embedded software development is notoriously arcane. Developers often have to
19 their code against hardware-specfic SDKs/HALs, and limit themselves to a small
27 hardware the framework supports, and you get an efficient embedded development
35 what Pigweed provides as they need, in the way that works best for their
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…
[all …]
|
| /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]
10 First, be sure to install the [prerequisite software][webrtc-prerequisite-sw].
12 [webrtc-prerequisite-sw]: https://webrtc.googlesource.com/src/+/main/docs/native-code/development/p…
17 For desktop development:
22 $ mkdir webrtc-checkout
23 $ cd webrtc-checkout
24 $ fetch --nohooks webrtc
48 $ git new-branch your-branch-name
51 See the [Android][webrtc-android-development] and [iOS][webrtc-ios-development] pages for separate …
[all …]
|
| /external/apache-xml/src/main/java/org/apache/xalan/processor/ |
| D | XSLProcessorVersion.src | 7 * you may not use this file except in compliance with the License.
10 * http://www.apache.org/licenses/LICENSE-2.0
12 * Unless required by applicable law or agreed to in writing, software
19 * $Id: XSLProcessorVersion.src 468640 2006-10-28 06:53:53Z minchau $
69 * - a new set of functionality is to be added, eg,
71 * - API or behaviour change.
72 * - its designated as a reference release.
83 * development drop for a release.
88 * Development Drop Number.
89 * Optional identifier designates development drop of
[all …]
|
| /external/tensorflow/tensorflow/lite/g3doc/android/ |
| D | index.md | 3 TensorFlow Lite lets you run TensorFlow machine learning (ML) models in your
8 ## Learning roadmap {:.hide-from-toc}
10 <section class="devsite-landing-row devsite-landing-row-3-up devsite-landing-row-100" header-positi…
11 <div class="devsite-landing-row-inner">
12 <div class="devsite-landing-row-group">
13 …<div class="devsite-landing-row-item devsite-landing-row-item-no-media tfo-landing-page-card" desc…
14 <div class="devsite-landing-row-item-description">
15 <div class="devsite-landing-row-item-body">
16 <div class="devsite-landing-row-item-description-content">
18 … <h3 class="no-link hide-from-toc" id="code-design" data-text="Code design">Code design</h3></a>
[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
13 It can be enabled using the :option:`-X dev <-X>` command line option or by
16 See also :ref:`Python debug build <debug-build>`.
18 Effects of the Python Development Mode
21 Enabling the Python Development Mode is similar to the following command, but
24 PYTHONMALLOC=debug PYTHONASYNCIODEBUG=1 python3 -W default -X faulthandler
26 Effects of the Python Development Mode:
28 * Add ``default`` :ref:`warning filter <describing-warning-filters>`. The
37 filters <describing-warning-filters>`.
[all …]
|
| /external/webrtc/docs/native-code/android/ |
| D | index.md | 1 # WebRTC Android development
5 Android development is only supported on Linux.
7 1. Install [prerequisite software][webrtc-prerequisite-sw]
12 $ fetch --nohooks webrtc_android
16 This will fetch a regular WebRTC checkout with the Android-specific parts
19 The same checkout can be used for both Linux and Android development since you
20 can generate your [Ninja][ninja] project files in different directories for each
23 See [Development][webrtc-development] for instructions on how to update
35 $ gn gen out/Debug --args='target_os="android" target_cpu="arm"'
39 to enable managing multiple configurations in parallel.
[all …]
|
| /external/webrtc/docs/native-code/ |
| D | index.md | 5 API][webrtc-api] instead.
7 [webrtc-api]: http://dev.w3.org/2011/webrtc/editor/webrtc.html
10 [https://webrtc.googlesource.com/src][webrtc-repo].
12 [webrtc-repo]: https://webrtc.googlesource.com/src/
15 [https://webrtc.googlesource.com/src/+log][webrtc-change-log]
17 [webrtc-change-log]: https://webrtc.googlesource.com/src/+log
19 Please read the [License & Rights][webrtc-license] and [FAQ][webrtc-faq]
22 [webrtc-license]: https://webrtc.org/support/license
23 [webrtc-faq]: https://webrtc.googlesource.com/src/+/main/docs/faq.md
25 The WebRTC [issue tracker][webrtc-issue-tracker] can be used for submitting
[all …]
|
| /external/webrtc/docs/native-code/ios/ |
| D | index.md | 1 # WebRTC iOS development
3 ## Development Environment
5 In case you need to build the framework manually or you want to try out the
8 A macOS machine is required for iOS development. While it's possible to
12 _NOTICE:_ You will need to install [Chromium depot_tools][webrtc-prerequisite-sw].
19 $ fetch --nohooks webrtc_ios
23 This will fetch a regular WebRTC checkout with the iOS-specific parts
25 for both Mac and iOS development, since GN allows you to generate your
26 [Ninja][ninja] project files in different directories for each build config.
31 Note that the git repository root is in `src`.
[all …]
|
| /external/brotli/python/ |
| D | README.md | 6 We provide a `Makefile` to simplify common development commands.
20 ### Development subsection
24 $ make # Build the module in-place
32 "[development mode][]":
34 $ make develop # Install the module in "development mode"
43 Then, to format all files in the project, you can run:
51 [development mode]: https://setuptools.readthedocs.io/en/latest/setuptools.html#development-mode
|
| /external/python/setuptools/docs/userguide/ |
| D | development_mode.rst | 1 "Development Mode"
5 build a distribution of your project, not use it in its "raw" or "unbuilt"
8 change to it during development.
11 need to do development on two related projects at the same time. You may need
12 to put both projects' packages in the same directory to run them, but need to
15 Setuptools allows you to deploy your projects for use in a common directory or
17 code in its checkout directory, and only need to run build commands when you
21 or the site-packages directory).
25 Instead, it creates a special ``.egg-link`` file in the deployment directory,
27 Python's ``site-packages`` directory, it will also update the
[all …]
|
| /external/crosvm/docs/book/src/building_crosvm/ |
| D | linux.md | 14 ## Setting up the development environment
19 git submodule update --init
22 It is recommended to enable automatic recursive operations to keep the submodules in sync with the
30 Crosvm development best works on Debian derivatives. We provide a script to install the necessary
34 ./tools/install-deps
38 [Using the development container](#using-the-development-container).
40 ### Using the development container
43 [Podman](https://podman.io/getting-started/installation) or
44 [Docker](https://docs.docker.com/get-docker/) installed, it can be started with:
51 follow all instructions in this document within the container shell.**
[all …]
|
| /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
9 significantly from the state proposed in these documents.*
11 * [S3 Transfer Manager](services/s3/transfermanager/README.md) -
16 *These features are being proposed for development. These features will
17 either transition to "In Development" when development begins, or
22 * [Event Streaming Alternate Syntax](core/event-streaming/alternate-syntax/README.md)
23 \- Simplifies interacting with event streaming services for
24 non-power-users.
25 * [Event Streaming Auto-Reconnect](core/event-streaming/reconnect/README.md)
[all …]
|
| /external/jacoco/org.jacoco.doc/docroot/doc/ |
| D | environment.html | 1 <?xml version="1.0" encoding="UTF-8" ?>
2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-st…
5 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
6 <link rel="stylesheet" href="resources/doc.css" charset="UTF-8" type="text/css" />
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
46 the <a href="http://www.eclipse.org/m2e/">m2e plug-in</a> to get all
48 Eclipse projects that can be imported in a Eclipse workspace.
[all …]
|
| /external/openthread/third_party/mbedtls/repo/ |
| D | CONTRIBUTING.md | 7 -----------------------------------
8 More details on all of these points may be found in the sections below.
10 - [Sign-off](#license-and-copyright): all commits must be signed off.
11 - [Tests](#tests): please ensure the PR includes adequate tests.
12 - [Changelog](#documentation): if needed, please provide a changelog entry.
13 - [Backports](#long-term-support-branches): provide a backport if needed (it's fine to wait until t…
16 ----------------
17 - Contributions should include tests, as mentioned in the [Tests](#tests) and [Continuous Integrati…
18 - The code should be written in a clean and readable style, and must follow [our coding standards](…
19 - The code should be written in a portable generic way, that will benefit the whole community, and …
[all …]
|
| /external/mbedtls/ |
| D | CONTRIBUTING.md | 7 -----------------------------------
8 More details on all of these points may be found in the sections below.
10 - [Sign-off](#license-and-copyright): all commits must be signed off.
11 - [Tests](#tests): please ensure the PR includes adequate tests.
12 - [Changelog](#documentation): if needed, please provide a changelog entry.
13 - [Backports](#long-term-support-branches): provide a backport if needed (it's fine to wait until t…
16 ----------------
17 - Contributions should include tests, as mentioned in the [Tests](#tests) and [Continuous Integrati…
18 - The code should be written in a clean and readable style, and must follow [our coding standards](…
19 - The code should be written in a portable generic way, that will benefit the whole community, and …
[all …]
|
| /external/perfetto/docs/contributing/ |
| D | ui-development.md | 1 # UI development
3 Some tips to get started with the UI development:
5 ## Development environment
10 located in the `ui` folder.
14 See [Build Instructions](build-instructions.md) page for the details about
15 starting the local development server.
17 The devserver has a live reload functionality: once you make a change in
19 reload automatically. By default, this logic uses a timeout in order to prevent
21 development-only "Rapid live reload" flag in the UI. Disabling it will reload
22 the page earlier, at the cost of sometimes making multiple reloads in a row.
[all …]
|
| /external/apache-xml/src/main/java/org/apache/xml/serializer/ |
| D | Version.java | 7 * you may not use this file except in compliance with the License.
10 * http://www.apache.org/licenses/LICENSE-2.0
12 * Unless required by applicable law or agreed to in writing, software
19 * $Id: Version.java 477252 2006-11-20 16:52:00Z minchau $
27 * org.apache.project-name.Version.getVersion() be a standard way
98 * - a new set of functionality is to be added, eg,
100 * - API or behaviour change.
101 * - its designated as a reference release.
115 * development drop for a release.
123 * Development Drop Number.
[all …]
|
| D | Version.src | 7 * you may not use this file except in compliance with the License.
10 * http://www.apache.org/licenses/LICENSE-2.0
12 * Unless required by applicable law or agreed to in writing, software
19 * $Id: Version.src 468654 2006-10-28 07:09:23Z minchau $
27 * org.apache.project-name.Version.getVersion() be a standard way
98 * - a new set of functionality is to be added, eg,
100 * - API or behaviour change.
101 * - its designated as a reference release.
115 * development drop for a release.
123 * Development Drop Number.
[all …]
|
| /external/pigweed/pw_watch/ |
| D | docs.rst | 1 .. _module-pw_watch:
3 .. rst-class:: with-subtitle
8 .. pigweed-module::
13 ----------
15 ----------
16 In the web development space, file system watchers like `nodemon
19 actions when files change (such as reloading a web server), making development
20 much faster. In the embedded space, file system watchers are less prevalent but
23 .. _module-pw_watch-design:
25 ------------
[all …]
|
| /external/apache-xml/src/main/java/org/apache/xalan/ |
| D | Version.java | 7 * you may not use this file except in compliance with the License.
10 * http://www.apache.org/licenses/LICENSE-2.0
12 * Unless required by applicable law or agreed to in writing, software
19 * $Id: Version.java 577939 2007-09-20 21:45:37Z minchau $
27 * org.apache.project-name.Version.getVersion() be a standard way
101 * - a new set of functionality is to be added, eg,
103 * - API or behaviour change.
104 * - its designated as a reference release.
118 * development drop for a release.
126 * Development Drop Number.
[all …]
|
| D | Version.src | 7 * you may not use this file except in compliance with the License.
10 * http://www.apache.org/licenses/LICENSE-2.0
12 * Unless required by applicable law or agreed to in writing, software
27 * org.apache.project-name.Version.getVersion() be a standard way
101 * - a new set of functionality is to be added, eg,
103 * - API or behaviour change.
104 * - its designated as a reference release.
118 * development drop for a release.
126 * Development Drop Number.
127 * Optional identifier designates development drop of
[all …]
|
| /external/guice/core/src/com/google/inject/ |
| D | Guice.java | 5 * you may not use this file except in compliance with the License.
8 * http://www.apache.org/licenses/LICENSE-2.0
10 * Unless required by applicable law or agreed to in writing, software
25 * <p>Guice supports a model of development that draws clear boundaries between APIs,
29 * class, as in this example:
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/OpenCL-CTS/test_common/ |
| D | config.hpp | 5 // you may not use this file except in compliance with the License.
8 // http://www.apache.org/licenses/LICENSE-2.0
10 // Unless required by applicable law or agreed to in writing, software
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/angle/doc/ |
| D | Update20130618.md | 1 # ANGLE Development Update - June 18, 2013
4 covering in a development update.
10 but please note that this repository is now read-only, and no further updates
11 will be made there. To continue tracking new development and issue fixes, you'll
17 ANGLE now provides both a DirectX 9 and a DirectX 11-backed renderer in the same
23 This work originally appeared in our dx11proto branch, which, with the move to
24 the new repository, has been promoted to master. Code previously located in the
25 trunk of the svn repository will now be located in the git legacy branch, and
26 active development will now move to the newly promoted master.
|