Home
last modified time | relevance | path

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

12345678910>>...86

/external/skia/site/dev/chrome/
Dchanges.md4 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).
Dblink.md37 * Skia roll into Chromium. See
40 * Blink roll into Chromium. See
50 Chromium's 'skia/skia\_common\.gypi'
52 6. Wait for Blink roll into Chromium.
53 7. Remove code suppression from Chromium's 'skia/skia\_common\.gypi'.
60 4. Wait for Blink roll into Chromium.
62 6. Wait for Skia roll into Chromium.
65 1. Remove code suppression from header file in Chromium and add code suppression to
66 Chromium's 'skia/skia\_common\.gypi'.
69 the Chromium build.
[all …]
Drepo.md1 Working in a Chromium repo
4 To work on Skia inside a Chromium checkout, run the following:
16 We no longer recommend the .gclient file manipulation to have Chromium DEPS also
18 Chromium doesn't need any of them, and it can be confusing and problematic if
19 they somehow get mixed into the Chromium build.
/external/chromium-webview/
DREADME1 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 N release, the Java code in the Chromium 2743_91
29 Java changes to Chromium once the final N SDK is released.
/external/v8/
DChangeLog440 [ic] LoadICState cleanup (Chromium issue 576312).
452 [ic] Remove --new-load-global-ic switch (Chromium issue 576312).
499 [ic] Enable new LoadGlobalIC machinery (Chromium issue 576312).
502 vector (Chromium issue 576312).
535 properties backing store is enlarged (Chromium issue 601420).
542 [ic] Split LoadIC into LoadGlobalIC and LoadIC (Chromium issue 576312).
707 [ic] [stubs] Remove InlineCacheState field from the code flags (Chromium
730 [build] Use icu data file by default (Chromium issue 616033).
777 [build] Use sysroot for linux compilation with clang (Chromium issues
805 [icu] Support loading data file from default location (Chromium issue
[all …]
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
/external/webrtc/webrtc/
Dsupplement.gypi5 # 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/build/android/docs/
Dlint.md4 analysis tool that Chromium uses to catch possible issues in Java code.
8 ## How Chromium uses lint
10 Chromium runs lint on a per-target basis for all targets using any of the
11 following templates if they are marked as Chromium code (i.e.,
19 Chromium also runs lint on a per-target basis for all targets using any of the
20 following templates if they are marked as Chromium code and they support
45 in Chromium is typically limited to the first three.
76 should be ignored. Chromium's lint suppression XML file can be found in
/external/webrtc/build_overrides/
Dwebrtc.gni10 # 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/chromium-trace/catapult/telemetry/third_party/chromite/
DREADME.chromium13 This contains scripts used to build Chromium for Chromium OS
14 ('cros chrome-sdk'), as well as interact with the Chromium OS
/external/webrtc/webrtc/build/
Dcommon.gypi62 # 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/autotest/client/site_tests/security_RendererSandbox/
Dcontrol1 AUTHOR = "Chromium OS Team"
3 PURPOSE = "Basic check to ensure renderer is sandboxed/jailed in Chromium OS."
17 environment inside Chromium OS.
/external/autotest/client/site_tests/desktopui_SpeechSynthesisSemiAuto/
Dcontrol1 # 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/
Dcontrol.surfing1 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
Dcontrol1 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
/external/webrtc/
DDEPS1 # 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_DbusMap/
Dcontrol1 # Copyright (c) 2011 The Chromium OS Authors. All rights reserved.
6 AUTHOR = "The Chromium OS Authors"
9 in Chromium OS.
/external/v8/build/secondary/third_party/crashpad/crashpad/handler/
DBUILD.gn1 # Copyright 2015 The Chromium Authors. All rights reserved.
51 # The handler is in Chromium.app/Contents/Versions/X/Chromium Framework.framework/Helpers/
/external/autotest/client/site_tests/security_ChromiumOSLSM/
Dcontrol1 # Copyright (c) 2011 The Chromium OS Authors. All rights reserved.
6 PURPOSE = "Verify that the Chromium Security Module is working as expected"
20 Verify that the Chromium Security Module is working as expected.
/external/v8/build/
Dchrome_settings.gypi1 # Copyright 2013 The Chromium Authors. All rights reserved.
23 'mac_bundle_id': 'org.chromium.Chromium',
26 'grit_defines': ['-D', 'mac_bundle_id=org.chromium.Chromium'],
/external/autotest/client/site_tests/video_VEAPerf/
Dcontrol.vp8.bvt1 # Copyright 2015 The Chromium Authors. All rights reserved.
7 PURPOSE = "Monitor the performance of the Chromium VEA."
25 performance of the Chromium Video Encode Accelerator.
Dcontrol.h264.bvt1 # Copyright 2015 The Chromium Authors. All rights reserved.
7 PURPOSE = "Monitor the performance of the Chromium VEA."
25 performance of the Chromium Video Encode Accelerator.
/external/autotest/client/site_tests/video_VDAPerf/
Dcontrol.h264.4k1 # Copyright (c) 2013 The Chromium Authors. All rights reserved.
7 PURPOSE = "Monitor the performance of the Chromium hardware VDA."
22 performance of the Chromium hardware Video Decode Accelerator.
Dcontrol.vp8.4k1 # Copyright (c) 2013 The Chromium Authors. All rights reserved.
7 PURPOSE = "Monitor the performance of the Chromium hardware VDA."
22 performance of the Chromium hardware Video Decode Accelerator.
/external/chromium-trace/catapult/dashboard/docs/
Dglossary.md48 ## Chromium continuous integration infrastructure
51 Chromium Perf waterfall is also known as chromium.perf or ChromiumPerf.
56 *Reference (ref) build*: On the Chromium Perf waterfall, tests are run
57 on both ToT Chromium and on an older build of Chromium. This is useful

12345678910>>...86