0
Files
src/chromeos
Nico Weber 918fe7f6e0 Reformat all gn files in /chromeos/components/multidevice.
`gn format` recently changed its formatting behavior
for deps, source, and a few other elements when they
are assigned (with =) single-element lists to be consistent
with the formatting of updates (with +=) with single-element.

Now that we've rolled in a GN binary with the change,
reformat all files so that people don't get presubmit
warnings due to this.

This CL was uploaded by git cl split.

R=khorimoto@chromium.org

Bug: 1041419
Change-Id: I3ac659a55e0fa6ab8a0068f8e4fd24616f7dee33
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1997812
Auto-Submit: Nico Weber <thakis@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#730811}
2020-01-13 20:59:28 +00:00
..
2020-01-13 02:48:15 +00:00
2019-10-12 04:14:45 +00:00

Chrome OS

This directory contains low-level support for Chrome running on Chrome OS. Many subdirectories contain Chrome-style C++ wrappers around operating system components.

For example, //chromeos/dbus contains wrappers around the D-Bus interfaces to system daemons like the network configuration manager (shill). Most other directories contain low-level utility code. For example, //chromeos/disks has utilities for mounting and unmounting disk volumes.

There are two exceptions:

  • //chromeos/services contains mojo services that were not considered sufficiently general to live in top-level //services. For example //chromeos/services/secure_channel bootstraps a secure communications channel to an Android phone over Bluetooth, enabling multi-device features like instant tethering.

  • //chromeos/components contains C++ components that were not considered sufficiently general to live in top-level //components. For example, //chromeos/components/account_manager manages the user's GAIA accounts, but is used as the backend for UI that only exists on Chrome OS devices.

Note, //chromeos does not contain any user-facing UI code, and hence it has "-ui" in its DEPS. The contents of //chromeos should also not depend on //chrome or //content.