Searched refs:Chromium (Results 1 – 25 of 2812) sorted by relevance
12345678910>>...113
/external/skqp/site/dev/chrome/ |
D | changes.md | 4 If your change modifies the Skia API, you may also need to land a change in Chromium. 6 The strategy you use to synchronize changes in the Skia and Chromium 11 Method 1 \(preferred\) \- Make the old code path opt\-in for Chromium 16 * Synchronize the above changes in Skia with a Chromium commit to 21 * Test the new or updated Skia API within Chromium. 24 Method 2 \- Make the new code path opt\-in for Chromium 28 * Set the flag in Chromium's 'skia/skia_common.gypi' or 30 * Test the new or updated Skia API within Chromium. 35 how to synchronize the changes between Skia, Blink, and Chromium [here](./blink).
|
D | multi_repo_trybots.md | 1 Multiple repo Chromium trybots 4 When a proposed Skia change will require a change in Chromium or Blink it is 5 often helpful to locally create the Chromium and Blink changes and test with the 8 to do so on the Chromium trybots. 12 If the Skia patch is already in Gerrit and there are no associated Chromium 13 changes, then it is possible to just run the Chromium trybots. This will apply 16 Skia and Chromium changes 18 If the Skia patch is already in Gerrit and there are associated Chromium 19 changes, then in the Chromium CL add the following to 70 directory structure used by Chromium. When `gclient runhooks` is run, the files
|
D | repo.md | 1 Working in a Chromium repo 4 To work on Skia inside a Chromium checkout, run the following: 14 We no longer recommend the .gclient file manipulation to have Chromium DEPS also 16 Chromium doesn't need any of them, and it can be confusing and problematic if 17 they somehow get mixed into the Chromium build.
|
D | blink.md | 32 Updating the version of Skia in Chromium is called a 'roll'. 42 Chromium's 'skia/chromium\_skia\_defines\.gypi' 45 1. Add code suppression to Chromium's 'skia/chromium\_skia\_defines\.gypi' before making code 50 5. Wait for Skia roll into Chromium. 53 1. Remove code suppression from header file in Chromium and add code suppression to 54 Chromium's 'skia/chromium\_skia\_defines\.gypi'. 57 the Chromium build. 63 Chromium\.WebKit tree very red for an extended period, and the gardener needs to 65 2. Create a CL removing the code suppression from Chromium's 85 3. Wait for Skia roll into Chromium.
|
/external/skia/site/dev/chrome/ |
D | changes.md | 4 If your change modifies the Skia API, you may also need to land a change in Chromium. 6 The strategy you use to synchronize changes in the Skia and Chromium 11 Method 1 \(preferred\) \- Make the old code path opt\-in for Chromium 16 * Synchronize the above changes in Skia with a Chromium commit to 21 * Test the new or updated Skia API within Chromium. 24 Method 2 \- Make the new code path opt\-in for Chromium 28 * Set the flag in Chromium's 'skia/skia_common.gypi' or 30 * Test the new or updated Skia API within Chromium. 35 how to synchronize the changes between Skia, Blink, and Chromium [here](./blink).
|
D | multi_repo_trybots.md | 1 Multiple repo Chromium trybots 4 When a proposed Skia change will require a change in Chromium or Blink it is 5 often helpful to locally create the Chromium and Blink changes and test with the 8 to do so on the Chromium trybots. 12 If the Skia patch is already in Gerrit and there are no associated Chromium 13 changes, then it is possible to just run the Chromium trybots. This will apply 16 Skia and Chromium changes 18 If the Skia patch is already in Gerrit and there are associated Chromium 19 changes, then in the Chromium CL add the following to 70 directory structure used by Chromium. When `gclient runhooks` is run, the files
|
D | repo.md | 1 Working in a Chromium repo 4 To work on Skia inside a Chromium checkout, run the following: 14 We no longer recommend the .gclient file manipulation to have Chromium DEPS also 16 Chromium doesn't need any of them, and it can be confusing and problematic if 17 they somehow get mixed into the Chromium build.
|
D | blink.md | 32 Updating the version of Skia in Chromium is called a 'roll'. 42 Chromium's 'skia/chromium\_skia\_defines\.gypi' 45 1. Add code suppression to Chromium's 'skia/chromium\_skia\_defines\.gypi' before making code 50 5. Wait for Skia roll into Chromium. 53 1. Remove code suppression from header file in Chromium and add code suppression to 54 Chromium's 'skia/chromium\_skia\_defines\.gypi'. 57 the Chromium build. 63 Chromium\.WebKit tree very red for an extended period, and the gardener needs to 65 2. Create a CL removing the code suppression from Chromium's 85 3. Wait for Skia roll into Chromium.
|
/external/libyuv/files/build_overrides/ |
D | build.gni | 12 # 10.11 min SDK but those targets are only used in non-Chromium builds. We can 13 # remove this when Chromium drops 10.6 support and also requires 10.7. 17 # Some non-Chromium builds don't use Chromium's third_party/binutils. 21 # Chromium specific targets in a client project's GN file etc. 24 # Some non-Chromium builds don't support building java targets. 39 # For Chromium, Android 32-bit non-component, non-clang builds hit a 4GiB size 44 # Use system Xcode installation instead of the Chromium bundled Mac toolchain,
|
/external/chromium-webview/ |
D | README | 1 Building the Chromium-based WebView in AOSP is no longer supported. WebView can 2 now be built entirely from the Chromium source code. 4 General instructions for building WebView from Chromium: 9 The prebuilt libwebviewchromium.so included in these APKs is built from Chromium 27 Due to WebView API changes in the O-MR1 release, the Java code in the Chromium 29 the O-MR1 specific Java changes to Chromium once the final O-MR1 SDK is released.
|
/external/pdfium/build_overrides/ |
D | build.gni | 1 # Copyright 2016 The Chromium Authors. All rights reserved. 7 # and a 10.11 min SDK, but those targets are only used in non-Chromium 8 # builds. We can remove this when Chromium drops 10.6 support and also 14 # Chromium specific targets in a client project's GN file etc. 17 # Support different NDK locations in non-Chromium builds. 30 # PDFium builds don't use Chromium's third_party/binutils. 33 # PDFium just uses the Chromium suppression files for now.
|
/external/v8/build_overrides/ |
D | build.gni | 9 # Chromium specific targets in a client project's GN file etc. 13 # non-Chromium builds. 17 # Some non-Chromium builds don't support building java targets. 20 # Some non-Chromium builds don't use Chromium's third_party/binutils.
|
/external/webrtc/webrtc/ |
D | supplement.gypi | 5 # Override the default (10.6) in Chromium's build/common.gypi. 8 # Disable use of sysroot for Linux. It's enabled by default in Chromium, 23 # Chromium iOS toolchain relies on target_subarch being set. 40 # Replace Chromium's LSan suppressions with our own for WebRTC. 49 # Replace Chromium's TSan v2 suppressions with our own for WebRTC.
|
/external/v8/ |
D | ChangeLog | 442 Remove SIMD.js from V8 (issue 4124, Chromium issue 5948). 3497 [build] Use MSVS 2015 by default (Chromium issue 603131). 6026 [wasm] Master CL for Binary 0xC changes (Chromium issue 575167). 6193 [wasm] Master CL for Binary 0xC changes (Chromium issue 575167). 10194 [wasm] Fix receiver conversion for WASM->JS calls (Chromium issue 10736 [ic] LoadICState cleanup (Chromium issue 576312). 10748 [ic] Remove --new-load-global-ic switch (Chromium issue 576312). 10795 [ic] Enable new LoadGlobalIC machinery (Chromium issue 576312). 10798 vector (Chromium issue 576312). 10831 properties backing store is enlarged (Chromium issue 601420). [all …]
|
D | CODE_OF_CONDUCT.md | 3 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
|
/external/toolchain-utils/ |
D | README.chromium | 10 include tools for downloading and building Chromium OS; building 11 custom versions of the toolchain inside Chromium OS; launching 16 NOTE: These tools are strictly for Chromium developers; none of them 17 ship on the final product (devices that run Chromium OS).
|
/external/webrtc/build_overrides/ |
D | webrtc.gni | 10 # standalone build (i.e. not in Chromium). 13 # build_overrides/ of Chromium. 17 # Excluded in Chromium since its prerequisites don't require Pulse Audio. 20 # Chromium uses its own IO handling, so the internal ADM is only built for
|
/external/webrtc/webrtc/build/ |
D | common.gypi | 62 # The Chromium common.gypi we use treats all gyp files without 66 # We can set this here to have WebRTC code treated as Chromium code. Our 140 # Exclude pulse audio on Chromium since its prerequisites don't require 144 # Exclude internal ADM since Chromium uses its own IO handling. 147 # Remove tests for Chromium to avoid slowing down GYP generation. 150 }, { # Settings for the standalone (not-in-Chromium) build. 203 # Chromium's build/common.gypi defines _DEBUG for all posix 221 # Changes settings for Chromium build. 230 # mechanism for selecting the override headers in Chromium. 244 # -Wextra is currently disabled in Chromium's common.gypi. Enable [all …]
|
/external/libpng/contrib/oss-fuzz/ |
D | README.txt | 12 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
|
/external/webrtc/ |
D | DEPS | 1 # This file contains dependencies for WebRTC that are not shared with Chromium. 2 # If you wish to add a dependency that is present in Chromium's src/DEPS or a 3 # directory from the Chromium checkout, you should add it to setup_links.py 68 # Create links to shared dependencies in Chromium. 75 # an early hook but it will need to be run after syncing Chromium and 91 # but then we would need to run all the Chromium hooks each time,
|
/external/autotest/client/site_tests/security_RendererSandbox/ |
D | control | 1 AUTHOR = "Chromium OS Team" 3 PURPOSE = "Basic check to ensure renderer is sandboxed/jailed in Chromium OS." 16 environment inside Chromium OS.
|
/external/libmojo/base/android/linker/ |
D | config.gni | 1 # Copyright 2014 The Chromium Authors. All rights reserved. 9 # Chromium linker doesn't reliably support loading multiple libraries; 11 # Chromium linker causes instrumentation to return incorrect results.
|
/external/libyuv/files/tools_libyuv/autoroller/unittests/testdata/ |
D | DEPS | 9 # Entry that is a directory in Chromium, so we're using a Git subtree mirror for it. 13 # Entry that's also a DEPS entry in the Chromium DEPS file. 17 # Entry only present in libyuv, not Chromium.
|
/external/autotest/client/site_tests/desktopui_SpeechSynthesisSemiAuto/ |
D | control | 1 # Copyright (c) 2010 The Chromium OS Authors. All rights reserved. 5 AUTHOR = "Chromium OS Team" 18 Please confirm manually that the text "Welcome to Chromium O S" is heard.
|
/external/autotest/client/site_tests/platform_CryptohomeStress/ |
D | control | 1 AUTHOR = "Chromium OS Team" 3 PURPOSE = "Stress test the encrypted file system in Chromium OS." 10 This is a stress test of the file system in Chromium OS. While performing the
|
12345678910>>...113