Searched refs:Chrome (Results 1 – 25 of 240) sorted by relevance
12345678910
/third_party/gn/docs/ |
D | standalone.md | 4 with GN but also be brought into the Chrome build. 8 and the Chrome build. However, GN is much more explicit in its naming 17 * A master build config file. Chrome's is `//build/config/BUILDCONFIG.gn` 20 complex reasons. Chrome's are in `//build/toolchain/<platform>/BUILD.gn`. 29 * See Chrome's `src/.gn` file. 30 * Unlike Chrome, you probably don't need to define a secondary root. 33 Adding a `.gn` file in a repository that is pulled into Chrome means 35 your subproject rather than for all of Chrome. This could be an 39 (e.g., to do the full Chrome build instead), you can use the command-line 42 If you want a completely standalone build that has nothing to do with Chrome [all …]
|
/third_party/skia/site/docs/dev/chrome/ |
D | _index.md | 3 title: "Skia in Chrome" 4 linkTitle: "Skia in Chrome" 14 If you have a Skia change that needs to be tested in Chrome, or which requires 30 Branching for Chrome 34 Chrome, eg. [refs/heads/chrome/m75](https://skia.googlesource.com/skia/+/chrome/m75). 37 housekeeping like updating the Chrome milestone number for the next release,
|
D | changes.md | 3 title: "Chrome changes" 4 linkTitle: "Chrome changes"
|
/third_party/skia/third_party/externals/angle2/doc/ |
D | BranchingAndRolling.md | 7 branch to correspond to a branched release of Chrome. 47 Sometimes, individual changes to ANGLE are needed for a release of Chrome which 49 created to correspond to the Chrome release version, so that Chrome may 51 the version on which Chrome depended at branch time. **Please note: Only ANGLE 53 Chrome release: 55 * Determine what the ANGLE dependency is for the Chrome release 58 * e.g., for [the Chrome 34 release at
|
D | DebuggingTips.md | 312 ## Testing with Chrome Canary 315 are available via JavaScript. For testing purposes, custom ANGLE builds may be injected in Chrome 322 1. Download and install [Google Chrome Canary](https://www.google.com/chrome/canary/). 329 1. Install Google Chrome Dev (via apt, or otherwise). Expected installation directory is 337 1. Download and install [Google Chrome Canary](https://www.google.com/chrome/canary/). 340 % xattr -cr /Applications/Google\ Chrome\ Canary.app 345 …bEGL.dylib,libGLESv2.dylib} /Applications/Google\ Chrome\ Canary.app/Contents/Frameworks/Google\ C… 349 % codesign --force --sign - --deep /Applications/Google\ Chrome\ Canary.app 354 Run Chrome: 356 - On Windows: `%LOCALAPPDATA%\Google\Chrome SxS\chrome.exe` [all …]
|
D | Orientation.md | 93 - Make sure you close all open instances of Chrome, they use a lot of background CPU and GPU. In 96 ### Profiling with Visual Studio + Chrome 98 - Install [Chrome Canary](https://www.google.com/chrome/browser/canary.html). 100 - Canary's install dir is usually `%APPDATA%/Local/Google/Chrome SxS/Application` 109 - Attach to the Chrome GPU process, then immediately pause profiling.
|
/third_party/skia/modules/canvaskit/future_apis/ |
D | ImageDecoder.md | 20 in Chrome Canary, works in version 85.0.4175.0. 24 1. Download and install [Chrome Canary](https://www.google.com/chrome/canary/). Verify that you 27 2. Run Chrome Canary with the `--enable-blink-features=WebCodecs` flag. 29 **MacOS**: Run `/applications/Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ Canary --en…
|
/third_party/skia/infra/wasm-common/docker/ |
D | README.md | 28 This image has Google Chrome and karma/jasmine installed on it, which can 39 Of note, some versions (generally before Chrome 60) run out of space on /dev/shm when 54 This image has Google Chrome and karma/jasmine installed on it, which can 66 Of note, some versions (generally before Chrome 60) run out of space on /dev/shm when 83 This image has Google Chrome and karma/jasmine installed on it, which can 95 Of note, some versions (generally before Chrome 60) run out of space on /dev/shm when
|
/third_party/skia/third_party/externals/icu/source/data/locales/ |
D | tg.txt | 8 * Chrome Note: This locale data is abridged to contain categories 9 * actually used by Chrome.
|
D | ku.txt | 8 * Chrome Note: This locale data is abridged to contain categories 9 * actually used by Chrome.
|
/third_party/skia/third_party/externals/icu/source/data/lang/ |
D | wa.txt | 8 * Chrome Note: This locale data is abridged to contain categories 9 * actually used by Chrome.
|
D | ku.txt | 8 * Chrome Note: This locale data is abridged to contain categories 9 * actually used by Chrome.
|
D | an.txt | 8 * Chrome Note: This locale data is abridged to contain categories 9 * actually used by Chrome.
|
D | tg.txt | 11 * Chrome Note: This locale data is abridged to contain categories 12 * actually used by Chrome.
|
/third_party/skia/site/docs/dev/internal/ |
D | _index.md | 29 ## Chrome related 31 - [Development on a Chrome branch](https://sites.google.com/a/google.com/skia/development-on-a-chro… 32 …ogle.com/skia/development-on-a-chrome-branch#TOC-How-to-cherrypick-a-Skia-fix-into-a-Chrome-branch)
|
/third_party/skia/third_party/externals/swiftshader/docs/ |
D | Subzero.md | 4 Subzero is a JIT compiler used as a back-end for [Reactor](Reactor.md). It originates from Chrome's… 9 … in your CMake command (or change LLVM to Subzero in the CMake GUI). For Chrome builds that use th… 16 * Install Chrome's [depot_tools](http://dev.chromium.org/developers/how-tos/install-depot-tools).
|
/third_party/skia/infra/lottiecap/docker/ |
D | README.md | 10 This image has Google Chrome, [puppeteer](https://github.com/GoogleChrome/puppeteer), 24 Of note, some versions (generally before Chrome 60) run out of space on /dev/shm when 40 This image has Google Chrome, [puppeteer](https://github.com/GoogleChrome/puppeteer), 56 Of note, some versions (generally before Chrome 60) run out of space on /dev/shm when
|
/third_party/node/deps/v8/tools/heap-stats/ |
D | README.md | 8 `--trace-gc-object-stats` or a trace captured using Chrome's tracing 9 infrastructure. Chrome trace files can either be processed as gzip or raw text
|
/third_party/node/deps/v8/third_party/inspector_protocol/ |
D | README.md | 15 See also [Contributing to Chrome Devtools Protocol](https://docs.google.com/document/d/1c-COD2kaK__… 18 [CRDTP - Chrome DevTools Protocol](crdtp/README.md).
|
/third_party/skia/tools/doxygen/mainpage/ |
D | mainpage.dox | 5 engine for Google Chrome and Chrome OS, Android, Mozilla Firefox and Firefox
|
/third_party/skia/third_party/externals/swiftshader/src/Reactor/ |
D | reactor.gni | 18 …# LLVM uses C++17 features which require macOS 10.12, while Chrome's minimum platform for x86 is 1… 20 # TODO(b/174843857): Remove check for !supports_subzero once Chrome supports macOS 10.12
|
/third_party/node/doc/api/ |
D | debugger.md | 229 V8 Inspector integration allows attaching Chrome DevTools to Node.js 231 [Chrome DevTools Protocol][]. 250 If the Chrome browser is older than 66.0.3345.0, 253 Chrome DevTools doesn't support debugging [worker threads][] yet. 256 [Chrome DevTools Protocol]: https://chromedevtools.github.io/devtools-protocol/
|
/third_party/skia/third_party/externals/angle2/ |
D | README.md | 7 Metal and MacOS, Chrome OS, and Fuchsia support. 26 | Chrome OS | | | | complete | planned | … 40 ANGLE is used as the default WebGL backend for both Google Chrome and Mozilla Firefox on Windows 41 platforms. Chrome uses ANGLE for all graphics rendering on Windows, including the accelerated
|
/third_party/skia/third_party/externals/libpng/contrib/oss-fuzz/ |
D | README.txt | 29 libpng_read_fuzzer.options original 2015, Chrome Devs Chromium 30 png.dict original 2015, Chrome Devs Chromium
|
/third_party/mesa3d/docs/ |
D | android.rst | 12 Chrome OS developers for building and testing Android drivers. 78 Replacing Android drivers on Chrome OS 81 Chrome OS's ARC++ is an Android container with hardware drivers inside 164 having to log in to Chrome again every time, you can just kill the
|
12345678910