File: README.md

package info (click to toggle)
chromium 138.0.7204.183-1
  • links: PTS, VCS
  • area: main
  • in suites: trixie
  • size: 6,071,908 kB
  • sloc: cpp: 34,937,088; ansic: 7,176,967; javascript: 4,110,704; python: 1,419,953; asm: 946,768; xml: 739,971; pascal: 187,324; sh: 89,623; perl: 88,663; objc: 79,944; sql: 50,304; cs: 41,786; fortran: 24,137; makefile: 21,806; php: 13,980; tcl: 13,166; yacc: 8,925; 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 (18) 
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.