system_api: add method name for SetCrostiniVmType dbus method platform2 owns method name constants for all dbus methods, including ones implemeted in chromium. Add the method name here for subsequent chromium implementation. BUG=b:476119187 TEST=None Change-Id: I0d4fab2faf3f0671a9e75550ca7c4cbd24941a41 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/7486735 Auto-Submit: maciek swiech <drmasquatch@google.com> Commit-Queue: Eric Caruso <ejcaruso@chromium.org> Commit-Queue: ChromeOS Auto Runner <chromeos-auto-runner@chromeos-bot.iam.gserviceaccount.com> Tested-by: maciek swiech <drmasquatch@google.com> Reviewed-by: Eric Caruso <ejcaruso@chromium.org> NOKEYCHECK=True GitOrigin-RevId: b16c7a5212ead3cb5a3e05adda4cbfb8e4fbc384
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.