crosvm/system_api
Dennis Kempin ee15178af7 Fix compilation with vtpm enabled
This snuck through because it's only compiled for chromeos. The feature
will be split out and enabled on upstream builds in https://crrev.com/c/3924741
to prevent failures like this in the future.

BUG=None
TEST=emerge-amd64-generic implicit-system crosvm

Change-Id: Id74c59a5a5a765bfbe5864ee9588ab9863b18bc7
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3929079
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
Auto-Submit: Dennis Kempin <denniskempin@google.com>
Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
2022-09-29 17:17:21 +00:00
..
src Fix compilation with vtpm enabled 2022-09-29 17:17:21 +00:00
Cargo.toml system_api: Add copy of ChromeOS's system_api 2022-09-28 18:13:00 +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.