crosvm/system_api
Daniel Verkamp a360baa819 Cargo.toml: upgrade protobuf 2.x -> 3.x
system_api bindings have been regenerated with protobuf 3.2; this should
be okay to land before the full ChromeOS system_api migration, since
crosvm always uses its own copy of the bindings rather than the ones
provided by the dev-rust/system_api package.

The protoc-rust crate is replaced with protobuf_codegen in 3.x.

BUG=b:277243607
BUG=b:279834784
TEST=tools/dev_container tools/presubmit

Change-Id: I6aad45ded2639d7506a7238800584bebab196455
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4405309
Reviewed-by: Dennis Kempin <denniskempin@google.com>
Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
Reviewed-by: Noah Gold <nkgold@google.com>
2023-04-28 19:32:01 +00:00
..
src Cargo.toml: upgrade protobuf 2.x -> 3.x 2023-04-28 19:32:01 +00:00
Cargo.toml Cargo.toml: upgrade protobuf 2.x -> 3.x 2023-04-28 19:32:01 +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.