system_api: generate Plugin VM service Go proto binding

Generates Go proto bindings for Plugin VM service to be used in Tast
tests.

BUG=chromium:1107876
TEST=build

Change-Id: I25711be5411a56c84796c5bf28363656c9c412ee
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/2310169
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: Olya Kalitova <okalitova@chromium.org>
Commit-Queue: Olya Kalitova <okalitova@chromium.org>
Cr-Mirrored-From: https://chromium.googlesource.com/chromiumos/platform2
Cr-Mirrored-Commit: adb92062928102bd5f5c61641a7b426fff8c8304
2 files changed
tree: bd91b0b1c3885b9c3d866efe43bfcd87cb679ba0
  1. .gitignore
  2. BUILD.gn
  3. Cargo.toml
  4. LICENSE
  5. OWNERS
  6. README.md
  7. build.rs
  8. constants/
  9. dbus/
  10. src/
  11. switches/
  12. system_api.pc
README.md

This directory (platform2/system_api) contains constants and definitions like D-Bus service names that are shared between Chromium and Chromium OS.

This directory is only for things like headers and .proto files. No implementation should be added.

When writting a .proto file make sure to use:

option optimize_for = LITE_RUNTIME;

This will force usage of a lite protobuf instead of a full/heavy weight protobuf. The browser only links against the light version, so you will get cryptic link errors about missing parts of Message if you define a protobuf here and then try to use it in Chrome. Currently CrOS links against the full protobuffer library, but that might change in the future.

When declaring a protobuf, avoid use of required unless it is exactly what you mean. “Required is Forever” and very rarely should actually be used. Consult Protocol Buffer Basics: C++ for a detailed of this issue.