| /external/python/google-api-python-client/docs/ |
| D | auth.md | 3 …omplished. For all API calls, your application needs to be authenticated. When an API accesses a u…
11 … do not access any private user data. Your application must authenticate itself as an application …
13 …key:** To authenticate your application, use an [API key](api-keys.md) for your API Console projec…
15 …Warning:** Keep your API key private. If someone obtains your key, they could use it to consume yo…
19 …vate data must grant your application access. Therefore, your application must be authenticated, t…
21 …When your application requests access to user data, the request must include one or more scopes. T…
23 …your application access, the OAuth 2.0 authorization server provides your application with refresh…
25 > **Warning:** Keep refresh and access tokens private. If someone obtains your tokens, they could u…
27 …your application and are used to acquire tokens. They are created for your project on the [API Con…
33 …:** Keep your client secret private. If someone obtains your client secret, they could use it to c…
|
| D | oauth-installed.md | 8 - Your installed app will run on devices that have a system browser and rich input capabilities, su…
10 … [Google Sign-In](https://developers.google.com/identity) to authenticate your users. The Google S…
12 If your app will run on devices that do not have access to a system browser, or devices with limite…
16 To use OAuth 2.0 in a locally-installed application, first create application credentials for your …
18 …your application needs to access a user's data with a Google API, your application sends the user …
20 …zation code to your application, either in the title bar of the browser or in the query string of …
22 Finally, your application can use the access token to call Google APIs.
26 - When creating a client ID, you specify that your application is an Installed application. This re…
27 …t secret obtained from the API Console are embedded in the source code of your application. In thi…
28 - The authorization code can be returned to your application in the title bar of the browser or in …
[all …]
|
| D | start.md | 19 … do not access any private user data. Your application must authenticate itself as an application …
21 …your application, use an [API key](https://cloud.google.com/docs/authentication/api-keys) for your…
23 …Warning**: Keep your API key private. If someone obtains your key, they could use it to consume yo…
27 …vate data must grant your application access. Therefore, your application must be authenticated, t…
29 …When your application requests access to user data, the request must include one or more scopes. T…
30 …your application access, the OAuth 2.0 authorization server provides your application with refresh…
32 …> **Warning**: Keep refresh and access tokens private. If someone obtains your tokens, they could …
34 …your application and are used to acquire tokens. They are created for your Google Cloud project on…
40 …**: Keep your client secret private. If someone obtains your client secret, they could use it to c…
148 …m/apis-explorer/) to browse APIs, list available methods, and even try API calls from your browser.
|
| /external/licenseclassifier/v2/assets/License/Xcode/ |
| D | license.txt | 3 …ING ANY PART OF THE APPLE SERVICES, YOU ARE AGREEING ON YOUR OWN BEHALF AND/OR ON BEHALF OF YOUR C…
16 …vices that Apple provides to You under this Agreement solely for use with Your Applications and no…
22 …ed in a single software bundle) developed by You hereunder, for use under Your own name, trademark…
26 …zed Developers” means Your employees and contractors, members of Your organization or, if You are …
28 …Your own testing and development purposes, and, if You permit, Apple-branded hardware units owned …
40 …ntifiers) that may be provided by Apple for use by You in connection with Your Application develop…
46 …Your” means the person(s) or entity using the Apple Software or Services or otherwise exercising r…
50 …Your own behalf, or if You are entering into this Agreement on behalf of Your company, organizatio…
55 …uters that are owned or controlled by You to be used internally by You or Your Authorized Develope…
67 …Your Applications onto a reasonable, limited number of Authorized Test Units solely for use by You…
[all …]
|
| /external/zstd/ |
| D | CONTRIBUTING.md | 14 We actively welcome your pull requests.
16 1. Fork the repo and create your branch from `dev`.
20 5. Make sure your code lints.
24 In order to accept your pull request, we need you to submit a CLA. You only need
27 Complete your CLA here: <https://code.facebook.com/cla>
37 * Checkout your fork of zstd if you have not already
42 * Update your local dev branch
48 * Make a new branch on your fork about the topic you're developing for
60 * Note: run local tests to ensure that your changes didn't break existing functionality
71 …* Before sharing anything to the community, create a pull request in your own fork against the dev…
[all …]
|
| /external/google-breakpad/docs/ |
| D | mac_breakpad_starter_guide.md | 1 # How To Add Breakpad To Your Mac Client Application
3 This document is a step-by-step recipe to get your Mac client app to build with
6 ## Preparing a binary build of Breakpad for use in your tree
9 build it as a dependency of your project. The former is recommended, and
12 change nearly often enough as your application's will.
19 * Execute `cp -R client/mac/build/Release/Breakpad.framework <location in your
27 Inside your application's framework, add the Breakpad.Framework to your
30 to your application.
32 ## Copy Breakpad into your Application Package
34 Copy Breakpad into your Application Package, so it will be around at run time.
[all …]
|
| /external/tensorflow/tensorflow/lite/g3doc/guide/ |
| D | build_ios.md | 3 This document describes how to build TensorFlow Lite iOS library on your own.
7 details on how to use them in your iOS projects.
13 changes in your iOS app or you prefer using static framework to our provided
48 Note: This step is not necessary if (1) you are using Bazel for your app, or (2)
50 cases, skip to the [Use in your own application](#use_in_your_own_application)
62 `bazel-bin/tensorflow/lite/ios/` directory under your TensorFlow root directory.
80 under `bazel-bin/tensorflow/lite/ios/` directory under your TensorFlow root
87 build, which will skip unused operations in your model set and only include the
100 your models contain Select TensorFlow ops. Note that the `--target_archs` flag
101 can be used to specify your deployment architectures.
[all …]
|
| /external/ot-br-posix/ |
| D | CONTRIBUTING.md | 27 …ew) and communicate your proposal so that the community can review and provide feedback. Getting e…
37 Setup your GitHub fork and continuous-integration services:
40 …le [Travis CI](https://travis-ci.org/) by logging in with your GitHub account and enabling your ne…
42 Setup your local development environment:
45 # Clone your fork
54 …your employer) retain the copyright to your contribution; this simply gives us permission to use a…
65 # Create a working branch for your new feature
82 This will open up a text editor where you can craft your commit message.
86 …your pull request, you might want to do a few things to clean up your branch and make it as simple…
88 If any commits have been made to the upstream main branch, you should rebase your development branc…
[all …]
|
| /external/python/jinja/ |
| D | CONTRIBUTING.rst | 13 your own code:
28 Include the following information in your post:
33 your own code.
36 - List your Python and Jinja versions. If possible, check if this
52 Include the following in your patch:
54 - Use `Black`_ to format your code. This and other tools will run
57 - Include tests if your patch adds or changes code. Make sure the test
58 fails without your patch.
73 - Configure git with your `username`_ and `email`_.
77 $ git config --global user.name 'your name'
[all …]
|
| /external/python/cpython3/Doc/howto/ |
| D | pyporting.rst | 12 use, it is good to have your project available for both major releases of
29 To make your project be single-source Python 2/3 compatible, the basic steps
36 #. Use Futurize_ (or Modernize_) to update your code (e.g. ``python -m pip install future``)
37 #. Use Pylint_ to help make sure you don't regress on your Python 3 support
39 #. Use caniusepython3_ to find out which of your dependencies are blocking your
41 #. Once your dependencies are no longer blocking you, use continuous integration
44 #. Consider using optional static type checking to make sure your type usage
45 works in both Python 2 & 3 (e.g. use mypy_ to check your typing under both
59 **today**! Even if your dependencies are not supporting Python 3 yet that does
60 not mean you can't modernize your code **now** to support Python 3. Most changes
[all …]
|
| /external/python/cpython2/Doc/howto/ |
| D | pyporting.rst | 12 use, it is good to have your project available for both major releases of
29 To make your project be single-source Python 2/3 compatible, the basic steps
36 #. Use Futurize_ (or Modernize_) to update your code (e.g. ``pip install future``)
37 #. Use Pylint_ to help make sure you don't regress on your Python 3 support
39 #. Use caniusepython3_ to find out which of your dependencies are blocking your
41 #. Once your dependencies are no longer blocking you, use continuous integration
44 #. Consider using optional static type checking to make sure your type usage
45 works in both Python 2 & 3 (e.g. use mypy_ to check your typing under both
53 **today**! Even if your dependencies are not supporting Python 3 yet that does
54 not mean you can't modernize your code **now** to support Python 3. Most changes
[all …]
|
| /external/skia/site/docs/dev/contrib/ |
| D | submit.md | 10 git config --global user.name "Your Name"
15 First create a branch for your changes:
22 After making your changes, create a commit
29 If your branch gets out of date, you will need to update it:
45 Unit tests are best, but if your change touches rendering and you can't think of
47 your change is in the GPU code, you may not be able to write it as part of the
59 If your feature will be conditionally enabled (e.g. like the GPU backends or image codecs), you
66 For your code to be accepted into the codebase, you must complete the
71 and send it to us as described on that page. Add your (or your organization's)
72 name and contact info to the AUTHORS file as a part of your CL.
[all …]
|
| /external/autotest/docs/ |
| D | loading-autotest-extension-on-device.md | 1 # Loading autotestPrivate extension on your device
5 the extension on your device.
13 checkout. To load a test image on your device follow [these steps] from the
20 autotest extension on your device](#Loading-autotest-extension-on-your-device)
24 1. Run in your workstation:
39 1. Reboot your device for rootfs changes to take effect. Run:
45 ## Loading autotest extension on your device
47 1. Enter a ChromeOS chroot. Inside of your ChromeOS checkout directory run:
51 1. From inside your ChromeOS chroot run:
55 This will install the autotestPrivate extension manifest to your device.
[all …]
|
| /external/llvm/docs/ |
| D | ExtendingLLVM.rst | 9 During the course of using LLVM, you may wish to customize it for your research
20 that you intend to use with your extension, and there are ``many`` LLVM analyses
24 instruction, and is transparent to optimization passes. If your added
50 Add an entry for your intrinsic. Describe its memory access characteristics
58 If it is possible to constant fold your intrinsic, add support to it in the
63 Add test cases for your test cases to the test suite
68 Add support to the .td file for the target(s) of your choice in
93 Add code to print the node to ``getOperationName``. If your new node can be
96 appropriate number of arguments, and add a case for your node to the switch
98 of arguments as your new node.
[all …]
|
| D | Projects.rst | 18 * ``PROJECT_NAME`` - The name by which your project is known.
33 * You can write your own ``Makefiles`` which hard-code these values.
40 If you want to devise your own build system, studying other projects and LLVM
41 ``Makefiles`` will probably provide enough information on how to write your own
47 In order to use the LLVM build system, you will want to organize your source
49 your source tree layout to look similar to the LLVM source tree layout.
51 Underneath your top level directory, you should have the following directories:
55 This subdirectory should contain all of your library source code. For each
65 This subdirectory should contain any header files that are global to your
67 executable of your project.
[all …]
|
| /external/rust/cxx/book/src/build/ |
| D | cargo.md | 51 spend time recompiling your C++ code when only non-C++ code has changed since
61 With cxx-build, by default your include paths always start with the crate name.
62 This applies to both `#include` within your C++ code, and `include!` in the
63 `extern "C++"` section of your Rust cxx::bridge.
65 Your crate name is determined by the `name` entry in Cargo.toml.
67 For example if your crate is named `yourcratename` and contains a C++ header
99 have `#include "path/to/header.h"`. However, if your crate is a library, be
101 using an empty include prefix, you'll want to make sure your headers' local path
106 If your `#[cxx::bridge]` module contains an `extern "Rust"` block i.e. types or
125 You get to include headers from your dependencies, both handwritten ones
[all …]
|
| /external/clang/docs/ |
| D | CrossCompilation.rst | 9 for cross-compiling your code to a different architecture. It assumes you
13 However, this document is *not* a "how to" and won't help you setting your
31 when compiling your code.
44 you're compiling to, where your tools are, etc.
49 to build your software, that is specific to your target. It's not enough to
50 have your host's libraries installed.
55 all your binaries and libraries are in the same directory, which may not
56 true when your cross-compiler was installed by the distribution's package
63 * be in a single directory, or spread out across your system
65 * need special options, which your build system won't be able to figure
[all …]
|
| /external/cronet/testing/libfuzzer/ |
| D | efficient_fuzzing.md | 5 maximize your results.
8 **Note:** If you haven’t created your first fuzz target yet, see the [Getting
12 The most direct way to gauge the effectiveness of your fuzz target is to collect
14 page after your fuzz target is checked into the Chromium repository.
33 You should aim for at least 1,000 exec/s from your fuzz target locally before
42 If your `LLVMFuzzerTestOneInput` function is too complex, it can decrease the
63 **Note:** It’s always a good idea to try different variants for your fuzz target
69 You can check the percentage of code covered by your fuzz target to gauge
75 * Generate a source-level coverage report for your fuzzer by running the
107 are checksums and magic numbers. Or, it may be impossible for your fuzzer to
[all …]
|
| /external/libusb/ |
| D | PORTING | 13 your target platform.
15 In terms of USB I/O, your backend provides functionality to submit
17 layers, based on the async interface). Your backend must also provide
20 Your backend must also provide an event handling function to "reap" ongoing
30 For libusb to work, your event handling function obviously needs to be called
31 at various points in time. Your backend must provide a set of file descriptors
36 which can be passed to poll(). If something similar is not true for your
48 Your implementations of these functions will need to call various internal
52 You probably want to skim over *all* the documentation before starting your
64 1. Modify configure.ac to detect your platform appropriately (see the OS_LINUX
[all …]
|
| /external/openthread/ |
| D | CONTRIBUTING.md | 28 …ew) and communicate your proposal so that the community can review and provide feedback. Getting e…
38 Setup your GitHub fork and continuous-integration services:
42 Setup your local development environment:
45 # Clone your fork
54 …your employer) retain the copyright to your contribution; this simply gives us permission to use a…
65 # Create a working branch for your new feature
82 This will open up a text editor where you can craft your commit message.
86 …your pull request, you might want to do a few things to clean up your branch and make it as simple…
88 If any commits have been made to the upstream main branch, you should rebase your development branc…
91 # Fetch upstream main and merge with your repo's main branch
[all …]
|
| /external/oss-fuzz/docs/clusterfuzzlite/ |
| D | build_integration.md | 27 Before you can start setting up your new project for fuzzing, you must do the following:
51 These must live in the `.clusterfuzzlite` directory in the root of your
62 Once the configuration files are generated, you should modify them to fit your
85 This integration file defines the Docker image for your project.
86 Your [build.sh](#buildsh) script will be executed in inside the container you
91 RUN apt-get update && apt-get install -y ... # install required packages to build your project
92 COPY . $SRC/<project_name> # checkout all sources needed to build your project
100 …ld binaries for [fuzz targets]({{ site.baseurl }}/reference/glossary/#fuzz-target) in your project.
101 The script is executed within the image built from your [Dockerfile](#Dockerfile).
105 - Build the project using your build system with OSS-Fuzz's compiler.
[all …]
|
| /external/auto/value/userguide/ |
| D | practices.md | 12 Avoid mutable types, including arrays, for your properties, especially if you
13 make your accessor methods `public`. The generated accessors don't copy the
14 field value on its way out, so you'd be exposing your internal state.
16 Note that this doesn't mean your factory method can't *accept* mutable types as
32 Your class can (and should) contain *simple* intrinsic behavior. But it
35 You should essentially *never* need an alternative implementation of your
37 framework. If your behavior has enough complexity (or dependencies) that it
46 reference from your source code: the call from your static factory method to the
54 Consider that other developers will try to read and understand your value class
55 while looking only at your hand-written class, not the actual (generated)
[all …]
|
| /external/tensorflow/tensorflow/lite/g3doc/examples/convert/ |
| D | index.md | 8 your TensorFlow models to the TensorFlow Lite model format.
18 depending on the content of your ML model. As the first step of that process,
19 you should evaluate your model to determine if it can be directly converted.
22 it uses. If your model uses operations outside of the supported set, you have
23 the option to refactor your model or use advanced conversion techniques.
54 Evaluating your model is an important step before attempting to convert it.
56 you want to determine if the contents of your model is compatible with the
57 TensorFlow Lite format. You should also determine if your model is a good fit
69 to determine if your model needs to be refactored for conversion.
83 You can convert your model using the [Python API](convert_models#python_api) or
[all …]
|
| /external/mesa3d/docs/ |
| D | repository.rst | 26 #. Install the Git software on your computer if needed.
33 #. Later, you can update your tree from the master repository with:
59 - Use `GitLab <https://gitlab.freedesktop.org/>`__ to create your
63 - You'll have to rely on another Mesa developer to push your initial
68 to give you access to merge your own code.
70 Pushing code to your GitLab account via HTTPS
77 to push over HTTPS if ssh will does not suit your needs. In this case,
82 … git remote set-url --push origin https://USER:TOKEN@gitlab.freedesktop.org/your~user~name/mesa.git
89 want to enable automatic CR/LF conversion in your local copy of the
133 would rebase your branch prior to merging with master. But for small
[all …]
|
| /external/markdown/docs/ |
| D | cli.md | 11 Generally, you will want to have the Markdown library fully installed on your
16 Therefore, assuming the python executable is on your system path, use the
51 your Python "Scripts" directory. Different systems require different methods to
52 ensure that any files in the Python "Scripts" directory are on your system
57 Assuming a default install of Python on Windows, your "Scripts" directory
59 of your "Scripts" directory and add it to you system path.
69 * Some systems will automatically install the script on your path. Try it
73 you need to add to your path. Find it (check with your distribution) and
74 either add it to your path or make a symbolic link to it from your path.
76 * If you are sure `markdown_py` is on your path, but it still is not being
[all …]
|