File: README.md

package info (click to toggle)
chromium 139.0.7258.127-1
  • links: PTS, VCS
  • area: main
  • in suites:
  • size: 6,122,068 kB
  • sloc: cpp: 35,100,771; ansic: 7,163,530; javascript: 4,103,002; python: 1,436,920; asm: 946,517; xml: 746,709; pascal: 187,653; perl: 88,691; sh: 88,436; objc: 79,953; sql: 51,488; cs: 44,583; fortran: 24,137; makefile: 22,147; tcl: 15,277; php: 13,980; yacc: 8,984; ruby: 7,485; awk: 3,720; lisp: 3,096; lex: 1,327; ada: 727; jsp: 228; sed: 36
file content (22 lines) | stat: -rw-r--r-- 987 bytes parent folder | download | duplicates (20) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
 
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++](http://code.google.com/apis/protocolbuffers/docs/cpptutorial.html)
for a detailed of this issue.