Searched refs:developers (Results 1 – 25 of 1186) sorted by relevance
12345678910>>...48
| /third_party/skia/third_party/externals/expat/expat/win32/ |
| D | MANIFEST.txt | 5 users, and some contain material of interest to developers who wish to
13 <top>\Doc\ API documentation for developers.
15 <top>\Bin\ Pre-compiled dynamic libraries for developers.
16 Pre-compiled static libraries for developers (*MT.lib).
19 <top>\Source\ Source code, which may interest some developers,
|
| /third_party/libinput/doc/user/ |
| D | development.rst | 4 Information for developers
7 Below is a list of topics of interest to developers, divided into
9 or other project. The :ref:`hacking_on_libinput` section applies to developers working on
13 libinput developers on the wayland-devel@lists.freedesktop.org
|
| /third_party/opencl-headers/tests/ |
| D | README.md | 6 to these expectations make use of these types practical for developers writing
11 carte. This provides developers a lifeline in the case that some unneeded part
21 extra warnings that it is expected developers are likely to use should be turned
|
| /third_party/skia/third_party/externals/oboe/ |
| D | CONTRIBUTORS | 6 # https://developers.google.com/open-source/cla/individual
7 # https://developers.google.com/open-source/cla/corporate
|
| /third_party/openGLES/extensions/QCOM/ |
| D | QCOM_driver_control.txt | 46 enabling developers to analyze driver overhead separate from GPU
48 rendering and thus should only be used by developers for debugging
53 of those controls to developers.
102 not change the name so that developers can key off this name for
|
| /third_party/skia/third_party/externals/opengl-registry/extensions/QCOM/ |
| D | QCOM_driver_control.txt | 46 enabling developers to analyze driver overhead separate from GPU
48 rendering and thus should only be used by developers for debugging
53 of those controls to developers.
102 not change the name so that developers can key off this name for
|
| /third_party/python/Doc/distributing/ |
| D | index.rst | 12 available for other Python developers to use under open source license terms.
39 developers and documentation authors responsible for the maintenance and
71 This means that other developers require explicit permission to copy, use,
75 relatively consistent way, allowing developers to share and collaborate
77 This leaves many developers free to spend more time focusing on the problems
81 reasonably straightforward for developers to make their own contributions
|
| /third_party/mesa3d/docs/ |
| D | developers.rst | 4 Both professional and volunteer developers contribute to Mesa.
7 developers including Brian Paul and Keith Whitwell.
|
| /third_party/node/deps/npm/docs/content/using-npm/ |
| D | orgs.md | 19 …uper admin will use the website to manage membership. Every org has a `developers` team that all u…
35 npm team ls <org>:developers
38 * Each org is automatically given a `developers` team, so you can see the whole list of team member…
|
| /third_party/node/deps/npm/docs/content/cli-commands/ |
| D | npm-completion.md | 41 * [npm developers](/using-npm/developers)
|
| /third_party/lwip/ |
| D | README_en.md | 12 and is now developed and maintained by a worldwide network of developers.
57 and developers using the stack often submit bug fixes, improvements,
63 mailing list. A core team of developers will commit changes to the
70 developers.
|
| D | README | 12 and is now developed and maintained by a worldwide network of developers.
57 and developers using the stack often submit bug fixes, improvements,
63 mailing list. A core team of developers will commit changes to the
70 developers.
|
| /third_party/node/doc/guides/ |
| D | technical-values.md | 27 We value ensuring that developers are productive and enjoy developing
40 keep the trust of developers and users, we value stability.
69 We value providing developers with modern APIs and technologies
|
| /third_party/vk-gl-cts/external/vulkan-docs/src/chapters/ |
| D | introduction.adoc | 30 and application developers seeking to make use of the API, forming a
36 developers).
56 background or suggestions to implementors or developers.
75 In text addressing application developers, their use expresses requirements
80 In text addressing application developers, the additional key words *can*
|
| D | introduction.txt | 30 and application developers seeking to make use of the API, forming a
36 developers).
56 background or suggestions to implementors or developers.
75 In text addressing application developers, their use expresses requirements
80 In text addressing application developers, the additional key words *can*
|
| /third_party/python/Doc/distutils/ |
| D | introduction.rst | 20 Using the Distutils is quite simple, both for module developers and for
35 Not all module developers have access to a multitude of platforms, so it's not
39 developers, build them on one or more platforms, and release the resulting built
109 First, both developers and installers have the same basic user interface, i.e.
111 :command:`sdist` command is almost exclusively for module developers, while
112 :command:`install` is more often for installers (although most developers will
|
| /third_party/libphonenumber/ |
| D | CONTRIBUTING.md | 65 See https://cla.developers.google.com/about to determine whether you need to
73 * [Corporate CLA](http://developers.google.com/open-source/cla/corporate?csw=1):
74 * See https://cla.developers.google.com/about and follow the instructions.
84 * [Individual CLA](http://cla.developers.google.com/about/google-individual?csw=1):
85 * See https://cla.developers.google.com/about to ensure that an Individual
125 GitHub username, go to https://cla.developers.google.com/clas and click
|
| /third_party/skia/third_party/externals/swiftshader/ |
| D | CONTRIBUTORS.txt | 6 # https://developers.google.com/open-source/cla/individual
7 # https://developers.google.com/open-source/cla/corporate
|
| D | CONTRIBUTING.txt | 6 (https://cla.developers.google.com/about/google-individual)
28 (https://cla.developers.google.com/about/google-corporate).
|
| /third_party/protobuf/python/docs/ |
| D | index.rst | 13 <https://developers.google.com/protocol-buffers/docs/pythontutorial>`_.
23 https://developers.google.com/protocol-buffers/
|
| /third_party/flutter/engine/flutter/ |
| D | README.md | 7 developers and organizations around the world, and is free and open source.
13 toolchain. Most developers will interact with Flutter via the [Flutter
|
| /third_party/skia/third_party/externals/brotli/ |
| D | CONTRIBUTING.md | 7 (https://cla.developers.google.com/about/google-individual)
27 (https://cla.developers.google.com/about/google-corporate).
|
| /third_party/libsnd/regtest/ |
| D | Readme.txt | 8 testing. From the point of view of the libsndfile developers, this
25 The user should then contact the libsndfile developers so that a copy
26 of the test file can be made available to the developers.
|
| /third_party/vk-gl-cts/external/vulkan-docs/src/appendices/ |
| D | VK_SEC_amigo_profiling.adoc | 25 Application developers should avoid using this extension.
26 It is documented solely for the benefit of tools and layer developers, who
|
| /third_party/libcoap/man/ |
| D | coap.txt.in | 74 libcoap-developers@lists.sourceforge.net or raise an issue on GitHub at
79 The libcoap project <libcoap-developers@lists.sourceforge.net>
|
12345678910>>...48