system_api: add explicit error code for license issues for Plugin VM

It is beneficial to know whether certain operations failed because of
invalid license or other reasons.

BUG=b:133521686
TEST=Build

Change-Id: I763706e9fefd0a476d7d82808f556911937b7335
Reviewed-on: https://chromium-review.googlesource.com/1660886
Tested-by: Dmitry Torokhov <dtor@chromium.org>
Commit-Ready: Dmitry Torokhov <dtor@chromium.org>
Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org>
Reviewed-by: Timothy Loh <timloh@chromium.org>
Cr-Mirrored-From: https://chromium.googlesource.com/chromiumos/platform2
Cr-Mirrored-Commit: b1c3be8c490ea9a3a84569282f43238e284b6d71
1 file changed
tree: 1352f18571afc96d14ac98abac6a5e27ef8c975a
  1. BUILD.gn
  2. LICENSE
  3. OWNERS
  4. README.md
  5. constants/
  6. dbus/
  7. switches/
  8. 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.