system_api: Add EIR property in bluetooth_device

This was added in crrev.com/c/1308457

BUG=chromium:887029,b:118334521
TEST=CQ

Change-Id: If80d8fc275e485f4f1db5d3c26e804b28aeaba5a
Reviewed-on: https://chromium-review.googlesource.com/1312382
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Tested-by: Qiyu Hu <qiyuh@google.com>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
(cherry picked from commit f7ec755ab30a72b8edb751703422f145b86549b0)
Reviewed-on: https://chromium-review.googlesource.com/c/1361651
Reviewed-by: Miao-chen Chou <mcchou@chromium.org>
Commit-Queue: Benjamin Gordon <bmgordon@chromium.org>
Tested-by: Benjamin Gordon <bmgordon@chromium.org>
1 file changed
tree: b3096e2c97d59aee662f5f8beee9383c86103450
  1. LICENSE
  2. MODULE_LICENSE_BSD
  3. OWNERS
  4. README.md
  5. constants/
  6. dbus/
  7. switches/
  8. system_api.gyp
  9. 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.