[go: nahoru, domu]
Google Git
Sign in
chromium / chromium / src / 89da162498dab17e3a49bc467d4d200dab5c7a9f / . / chromeos
tree: 052118d7f8d5ba9894b5e7c894edec223224193f [path history] [tgz]
  1. assistant/
  2. attestation/
  3. chromeos_strings_grd/
  4. components/
  5. crosapi/
  6. cryptohome/
  7. dbus/
  8. disks/
  9. geolocation/
  10. hugepage_text/
  11. ime/
  12. lacros/
  13. language/
  14. login/
  15. memory/
  16. metrics/
  17. network/
  18. policy/
  19. printing/
  20. process_proxy/
  21. profiles/
  22. resources/
  23. scanning/
  24. services/
  25. settings/
  26. startup/
  27. strings/
  28. system/
  29. test/
  30. third_party/
  31. timezone/
  32. tools/
  33. tpm/
  34. ui/
  35. utils/
  36. BUILD.gn
  37. chromeos_export.h
  38. CHROMEOS_LKGM
  39. chromeos_strings.grd
  40. DEPS
  41. DIR_METADATA
  42. LACROS_OWNERS
  43. OWNERS
  44. README.md
  45. SECURITY_OWNERS
  46. tast_control.gni
chromeos/README.md

Chrome OS

This directory contains low-level support for Chrome running on Chrome OS.

The Lacros project is in the process of extracting the browser-functionality into a separate binary. This introduces the following terminology and rules:

  • ash-chrome: The new name of the legacy “chrome” binary. It contains system UI and the current/legacy web browser. Code that is only used by ash-chrome should eventually be moved to //ash, have an _ash suffix in the filename, or have a (grand-)parent directory named /ash/.
  • lacros-chrome: The name of the new, standalone web-browser binary. Code that is only used by lacros-chrome should have a _lacros suffix in the filename, or have a (grand-)parent directory named /lacros/.
  • crosapi: The term “crosapi” is short for ChromeOS API. Ash-chrome implements the API, and lacros-chrome is the only consumer.
  • chromeos: The term “chromeos” refers to code that is shared by binaries targeting the chromeos platform or using the chromeos toolchain. Code that is shared by ash-chrome and lacros-chrome should have a _chromeos suffix in the filename, or have a (grand-)parent directory named /chromeos/.
  • Exception: The exception to the rule is //chrome/browser/chromeos. Following existing conventions in //chrome, the directory should refer to lacros-chrome. However, this would involve a massive and otherwise unnecessary refactor. //chrome/browser/chromeos will continue to contain code that is only used by ash-chrome. //chrome/browser/lacros will contain code used only by lacros-chrome. See this document for more details.

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.

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.