system_api: Add healthd mojo services

Add name of services related to cros_healthd. This is for the new
chromeos mojo service manager so create a new file under mojo/
directory.

BUG=b:230064284
TEST=CQ

Change-Id: Ia867fea3b1d65962ae1839f20775b6f8a23de9f3
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/3717708
Tested-by: Chung-Sheng Wu <chungsheng@google.com>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Queue: Chung-Sheng Wu <chungsheng@google.com>
NOKEYCHECK=True
GitOrigin-RevId: 66f039ef6f702efc6ad107bffff404939a44ca94
1 file changed
tree: abe9153f2e25e72f27cbebc7ed03cbbbecea67ce
  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.