Name |
Date |
Size |
#Lines |
LOC |
||
---|---|---|---|---|---|---|
.. | - | - | ||||
constants/ | 03-May-2024 | - | 18 | 7 | ||
dbus/ | 03-May-2024 | - | 6,673 | 5,180 | ||
switches/ | 03-May-2024 | - | 46 | 20 | ||
LICENSE | D | 03-May-2024 | 1.5 KiB | 28 | 27 | |
METADATA | D | 03-May-2024 | 39 | 4 | 3 | |
MODULE_LICENSE_BSD | D | 03-May-2024 | 0 | |||
OWNERS | D | 03-May-2024 | 75 | 5 | 4 | |
README | D | 03-May-2024 | 942 | 19 | 15 | |
system_api.gyp | D | 03-May-2024 | 12.2 KiB | 383 | 382 | |
system_api.pc | D | 03-May-2024 | 506 | 5 | 4 |
README
1This repository (system_api.git) contains constants and definitions like 2D-Bus service names that are shared between Chromium and Chromium OS. 3 4This repository is only for things like headers and .proto files. 5No implementation should be added. 6 7When writting a .proto file make sure to use: 8"option optimize_for = LITE_RUNTIME;" 9 10This will force usage of a lite protobuf instead of a full/heavy weight 11protobuf. The browser only links against the light version, so you will get 12cryptic link errors about missing parts of Message if you define a protobuf here 13and then try to use it in Chrome. Currently CrOS links against the full 14protobuffer library, but that might change in the future. 15 16When declaring a protobuf, avoid use of required unless it is exactly what you 17mean. "Required is Forever" and very rarely should actually be used. Consult 18http://code.google.com/apis/protocolbuffers/docs/cpptutorial.html for a detailed 19of this issue.