system_api: Add dbus constants for FjordOobeService

BUG=b:470421245
TEST=none

Change-Id: I54604620d499c65a6552d1ecf80d90b92d3b1f1b
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/7281346
Tested-by: Courtney Wong <[email protected]>
Reviewed-by: Eric Caruso <[email protected]>
Commit-Queue: Courtney Wong <[email protected]>
NOKEYCHECK=True
GitOrigin-RevId: 14e9d2a2a0556344f2092fd8bb74bfa76facfb77
1 file changed
tree: a4b419c1fd88551b8d5d50af2ea5eca8a43697c7
  1. constants/
  2. dbus/
  3. mojo/
  4. non_standard_ipc/
  5. proto/
  6. src/
  7. switches/
  8. .gitignore
  9. BUILD.gn
  10. build.rs
  11. Cargo.toml
  12. DIR_METADATA
  13. LICENSE
  14. OWNERS
  15. README.md
  16. 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.