Home
last modified time | relevance | path

Searched refs:Chromium (Results 1 – 25 of 344) sorted by relevance

12345678910>>...14

/third_party/skia/third_party/externals/angle2/doc/
DChoosingANGLEBranch.md12 Chromium. These branches are named `chromium/####`, where the number is the
13 matching Chromium branch. These branches will be created from the revision which
14 that Chromium branch points to as its dependency. So, for example, the
15 `chromium/2013` branch point is at r28bcf4ff, because [Chromium's dependency
20 It isn't necessary to be familiar with how Chromium's dependency management
23 stable Chromium release channel build, as those branches will be deployed with
24 Chromium, and receive updates if bugs are found and fixed during release
28 **We recommend choosing a branch corresponding to a Beta or Stable Chromium
31 ## Matching a Chromium release to an ANGLE branch
33 In order to determine which branches are used by Chromium releases, please use
[all …]
DBuildingAngleForChromiumDevelopment.md1 # How to build ANGLE in Chromium for dev
5 …ell as the graphics API translator. These parts can be built and tested inside a Chromium checkout.
7 … few other targets that don't build on Chromium. These steps describe how to build such targets wi…
11 * Checkout and build [Chromium](http://dev.chromium.org/Home).
14 ## Standalone ANGLE inside Chromium
40 * To go back to the Chromium-managed version, remove `third_party/angle/.gclient`.
42 ## Working with ANGLE in Chromium
44 …th a local version of ANGLE instead of the version that is pulled in by Chromium's [DEPS](https://…
65 …* Se the ANGLE workspace to the version specified in Chromium's DEPS. Ensure there are no modified…
66 * `gclient sync` your Chromium workspace.
DBranchingAndRolling.md1 # How to Branch and Roll Chromium's ANGLE Dependency
3 ANGLE provides an implementation of OpenGL ES on Windows, which Chromium relies
4 upon for hardware accelerated rendering and WebGL support. Chromium specifies
10 the Chromium repository. To reduce the chance of a Chromium-side
11 change breaking ANGLE's CQ, the version of Chromium against which
17 At present, autorollers manage both the ANGLE roll into Chromium, and
18 the Chromium roll into ANGLE. All of the ANGLE-related autorollers are
24 Chromium's dependency on third-party projects is tracked in [the Chromium
32 on which Chromium should depend. Please use the full SHA-1, not a
DContributingCode.md35 2. ANGLE's BUILD.gn script is used by [Chromium's gn build][gn-build-config]. If you change build
36 files other than to add or remove source files be aware you could break the Chromium build.
37 ANGLE's commit queue (CQ) will detect such breakage. Ask a project member for help with Chromium
38 issues if you don't have a Chromium checkout.
73 * If you are a Chromium developer, see
74 [Building ANGLE for Chromium Development][build-ANGLE-for-chromium] for instructions on
75 building ANGLE within Chromium.
88 * The [Chromium GPU FYI bot waterfall][Chromium-waterfall] provides continuous integration for
94 [build-ANGLE-for-Chromium]: BuildingAngleForChromiumDevelopment.md
97 [Chromium-waterfall]: https://ci.chromium.org/p/chromium/g/chromium.gpu.fyi/console
[all …]
/third_party/skia/site/docs/dev/chrome/
Dchanges.md9 If your change modifies the Skia API, you may also need to land a change in Chromium.
11 The strategy you use to synchronize changes in the Skia and Chromium
16 Method 1 \(preferred\) \- Make the old code path opt\-in for Chromium
21 * Synchronize the above changes in Skia with a Chromium commit to
26 * Test the new or updated Skia API within Chromium.
29 Method 2 \- Make the new code path opt\-in for Chromium
33 * Set the flag in Chromium's 'skia/skia_common.gypi' or
35 * Test the new or updated Skia API within Chromium.
40 how to synchronize the changes between Skia, Blink, and Chromium [here](../blink).
Drepo.md3 title: "Working in a Chromium repo"
4 linkTitle: "Working in a Chromium repo"
9 To work on Skia inside a Chromium checkout, run the following:
19 We no longer recommend the .gclient file manipulation to have Chromium DEPS also
21 Chromium doesn't need any of them, and it can be confusing and problematic if
22 they somehow get mixed into the Chromium build.
Dmulti_repo_trybots.md3 title: "Multiple repo Chromium trybots"
4 linkTitle: "Multiple repo Chromium trybots"
9 When a proposed Skia change will require a change in Chromium or Blink it is
10 often helpful to locally create the Chromium and Blink changes and test with the
13 to do so on the Chromium trybots.
17 If the Skia patch is already in Gerrit and there are no associated Chromium
18 changes, then it is possible to just run the Chromium trybots. This will apply
21 Skia and Chromium changes
23 If the Skia patch is already in Gerrit and there are associated Chromium
24 changes, then in the Chromium CL add the following to
[all …]
Dblink.md38 Updating the version of Skia in Chromium is called a 'roll'.
48 Chromium's 'skia/chromium\_skia\_defines\.gypi'
51 1. Add code suppression to Chromium's 'skia/chromium\_skia\_defines\.gypi' before making code
56 5. Wait for Skia roll into Chromium.
59 1. Remove code suppression from header file in Chromium and add code suppression to
60 Chromium's 'skia/chromium\_skia\_defines\.gypi'.
63 the Chromium build.
69 Chromium\.WebKit tree very red for an extended period, and the gardener needs to
71 2. Create a CL removing the code suppression from Chromium's
91 3. Wait for Skia roll into Chromium.
Dcommandbuffer.md3 title: "Chromium Command Buffer"
4 linkTitle: "Chromium Command Buffer"
10 nanobench, on top of the GL ES interface provided by Chromium's command
17 The command buffer standalone shared library is built in a Chromium checkout
/third_party/skia/third_party/externals/angle2/src/common/third_party/base/
DREADME.angle1 Name: Chromium base:: helper Classes
5 SOURCE CODE: Copy the Chromium folder manually into this folder and run git cl format.
7 Revision: 28b5bbb227d331c01e6ff9b2f8729732135aadc7 (Chromium)
9 License: Chromium
10 License File: LICENSE in Chromium/src
17 To update the checkout, simply overwrite the folder with Chromium's latest, apply
26 violations when ANGLE code is mixed with Chromium code.
/third_party/skia/third_party/externals/angle2/infra/
DANGLEWrangling.md8 [Chromium GPU FYI Waterfall](https://ci.chromium.org/p/chromium/g/chromium.gpu.fyi/console)
21 **Note**: It's highly recommend that all wranglers install the [Chromium Flake Linker][Flaker]
47 unrelated to ANGLE [file a Chromium bug](http://crbug.com/new) and set the Label
48 `Hotlist-PixelWrangler` on the bug (see [Filing Chromium Bug Reports](#filing-chromium-bug-reports)…
57 ## Task 2: Monitor Chromium FYI Testers and Respond to Bugs
63 The [Chromium GPU FYI Waterfall][ChromiumFYI]
65 persistent breakage that could be related to ANGLE. Also follow [Chromium bugs in the `Internals>G…
74 ### Filing Chromium Bug Reports
76 The GPU Pixel Wrangler is responsible for the *Chromium* bugs. Please file issues with
79 *IMPORTANT* info to include in Chromium bug reports:
[all …]
/third_party/skia/third_party/externals/libpng/contrib/oss-fuzz/
DREADME.txt12 They were licensed by Google Inc, using the BSD-like Chromium license,
19 had no licensing information; we assumed that these were under the Chromium
28 libpng_read_fuzzer.cc derived 2017, Glenn R-P Chromium
29 libpng_read_fuzzer.options original 2015, Chrome Devs Chromium
30 png.dict original 2015, Chrome Devs Chromium
/third_party/node/tools/inspector_protocol/
DREADME.md1 # Chromium inspector (devtools) protocol
3 This package contains code generators and templates for the Chromium
9 In the Chromium tree, it's rolled into
20 [Chromium's development process](https://www.chromium.org/developers/contributing-code)
/third_party/skia/third_party/externals/abseil-cpp/
Dabsl.gni1 # Copyright 2020 The Chromium Authors. All rights reserved.
8 # to correctly compile abseil in Chromium.
46 # Within Chromium builds, restrict direct visibility of Abseil sources, so
68 # used by Chromium only when is_component_build=false.
72 # Not used by Chromium directly.
/third_party/node/deps/v8/
DCODE_OF_CONDUCT.md3 As part of the Chromium team, the V8 team is committed to preserving and
4 fostering a diverse, welcoming community. To this end, the [Chromium Code of
7 other Chromium-supported communication group, as well as any private
/third_party/skia/site/docs/dev/tools/
Dcodesearch.md13 [Chromium code search](https://code.google.com/p/chromium/codesearch) restricted
14 to the Skia portion of the Chromium tree. You can add a query after the slash;
16 Skia tree. Chromium code search provides cross-references.
43 [1]: http://cs.skia.org/ "Chromium code search"
54 search the repos of Skia clients, e.g. Chromium, Android, and Mozilla. If you
/third_party/skia/third_party/externals/dawn/docs/
Dinfra.md3 …Chromium's continuous integration (CI) infrastructure to continually run tests on changes to Dawn …
9 For additional information on GPU testing in Chromium, please see [[chromium/src]//docs/gpu/gpu_tes…
38 ## Dawn Chromium-Based CI Waterfall Bots
39 …ee Dawn, whereas bots named "DEPS Builder" are responsible for building Chromium's DEPS version of…
50 ## Dawn Chromium-Based Tryjobs
51 …which are defined in the Chromium workspace. The reason for this separation is that jobs sent to t…
58 And for Chromium CLs:
90 …erless configurations which means they use builderless GCEs shared with Chromium bots and don't ne…
/third_party/node/deps/v8/third_party/inspector_protocol/
DREADME.md1 # Chromium inspector (devtools) protocol
3 This package contains code generators and templates for the Chromium
9 In the Chromium tree, it's rolled into
/third_party/node/deps/v8/third_party/zlib/google/
DBUILD.gn1 # Copyright 2017 The Chromium Authors. All rights reserved.
40 # This allows other users of Chromium's zlib library, but don't use Chromium's
/third_party/skia/third_party/externals/zlib/google/
DBUILD.gn1 # Copyright 2017 The Chromium Authors. All rights reserved.
38 # This allows other users of Chromium's zlib library, but don't use Chromium's
/third_party/node/deps/zlib/google/
DBUILD.gn1 # Copyright 2017 The Chromium Authors
51 # This allows other users of Chromium's zlib library, but don't use Chromium's
/third_party/node/deps/v8/testing/gmock/
DBUILD.gn1 # Copyright 2014 The Chromium Authors. All rights reserved.
6 # it stabilizes, Chromium code MUST use this target instead of reaching directly
22 # it stabilizes, Chromium code MUST use this target instead of reaching directly
/third_party/libphonenumber/
DLICENSE.Chromium2 This project contains a small number of files derived from the Chromium
5 // Copyright (c) 2010 The Chromium Authors. All rights reserved.
9 Here is the full text of the LICENSE file from the Chromium project:
11 // Copyright 2014 The Chromium Authors. All rights reserved.
/third_party/skia/third_party/externals/dawn/src/tests/
DBUILD.gn31 # Gtest Gmock - Handle building inside and outside of Chromium.
34 # When building outside of Chromium we need to define our own targets for GTest
35 # and GMock. However when compiling inside of Chromium we need to reuse the
36 # existing targets, both because Chromium has a special harness for swarming
40 # When we aren't in Chromium we define out own targets based on the location
79 # When we are in Chromium we reuse its targets, and also add some deps that
93 # Wrapping of Chromium targets
96 # These targets are separated because they are Chromium sources files that
98 # applied while compiling a bunch of Chromium's //base (via header inclusion)
303 # When building inside Chromium, use their gtest main function because it is
[all …]
/third_party/skia/third_party/externals/dawn/src/fuzzers/
DBUILD.gn18 # We only have libfuzzer in Chromium builds but if we build fuzzer targets only
21 # as well with a dawn_fuzzer_test target that acts like Chromium's fuzzer_test.
25 # whole Chromium checkout.
30 # In Chromium build we just proxy everything to the real fuzzer_test

12345678910>>...14