system_api: Add tethering DBus properties

BUG=b:225767403
TEST=cros-workon-${BOARD} start chromeos-base/system_api
TEST=FEATURES=test emerge-${BOARD} chromeos-base/system_api

Change-Id: I5bef18a23ca8d4e3e48d7add60c8eadc7e093add
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/3678067
Tested-by: Jintao Lin <jintaolin@chromium.org>
Reviewed-by: Hugo Benichi <hugobenichi@google.com>
Commit-Queue: Jintao Lin <jintaolin@chromium.org>
Reviewed-by: Matthew Wang <matthewmwang@chromium.org>
NOKEYCHECK=True
GitOrigin-RevId: b59da3208b4fb3261e451f2ff3d4ca4003724a5f
1 file changed
tree: 54817b26e115b03489b6da472729e755cb1aeeaa
  1. constants/
  2. dbus/
  3. mojo/
  4. src/
  5. switches/
  6. .gitignore
  7. BUILD.gn
  8. build.rs
  9. Cargo.toml
  10. LICENSE
  11. OWNERS
  12. README.md
  13. 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.