crosvm/system_api
Daniel Verkamp ac0fc378a3 Fix remaining Chrome/Chromium OS instances
These should be written as ChromeOS and ChromiumOS (without the space)
to match the updated branding. The copyright headers were already
migrated to the new style (https://crrev.com/c/3894243), but there were
some more instances left over.

BUG=None
TEST=tools/cargo-doc

Change-Id: I8c76aea2eb33b2e370ab71ee9b5cc0a4cfd00585
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4129934
Reviewed-by: Dennis Kempin <denniskempin@google.com>
Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
2023-01-03 22:14:30 +00:00
..
src Fix compilation with vtpm enabled 2022-09-29 17:17:21 +00:00
Cargo.toml Fix remaining Chrome/Chromium OS instances 2023-01-03 22:14:30 +00:00
README.md system_api: Add copy of ChromeOS's system_api 2022-09-28 18:13:00 +00:00
update_bindings.sh system_api: Add copy of ChromeOS's system_api 2022-09-28 18:13:00 +00:00

Crosvm version of ChromeOS's system_api

system_api is used by ChromeOS to interact with other system services and mainly contains automatically generated bindings for dbus services and proto types.

The ground truth for this crate is in the ChromeOS codebase at platform2/system_api.

To allow us to build ChromeOS features in upstream crosvm, we need to copy a subset of the generated files into this repository. The update_bindings.sh script can be used to update them.

Note: Originally, the ChromeOS build would replace this crate with the ChromeOS platform2/system_api crate. This is no longer the case and crosvm will always be built against the version in this directory.