[go: nahoru, domu]
Google Git
Sign in
chromium / chromium / src / 71a22ffe9496acdc71c6d5afd08ce5d7d8385cc8 / . / chromeos
tree: 3c21eb1e59d01f9f3ca1fe8f13773aed01f9ae2e [path history] [tgz]
  1. assistant/
  2. chromeos_strings_grd/
  3. components/
  4. constants/
  5. crosapi/
  6. dbus/
  7. hugepage_text/
  8. ime/
  9. lacros/
  10. language/
  11. login/
  12. memory/
  13. metrics/
  14. network/
  15. printing/
  16. process_proxy/
  17. profiles/
  18. resources/
  19. scanning/
  20. services/
  21. startup/
  22. strings/
  23. system/
  24. test/
  25. third_party/
  26. tools/
  27. tpm/
  28. ui/
  29. utils/
  30. BUILD.gn
  31. chromeos_export.h
  32. CHROMEOS_LKGM
  33. chromeos_strings.grd
  34. DEPS
  35. DIR_METADATA
  36. LACROS_OWNERS
  37. OWNERS
  38. README.md
  39. SECURITY_OWNERS
  40. 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.

There are two exceptions:

  • //chromeos/services contains mojo services that were not considered sufficiently general to live in top-level //services and that, at the same time, are shared between ash-chrome and lacros-chrome. In case of an ash-chrome only mojo service, please use //ash/services instead.

  • //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.