File: README.md

package info (click to toggle)
chromium 146.0.7680.153-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 6,057,156 kB
  • sloc: cpp: 36,426,539; ansic: 7,626,206; javascript: 3,599,825; python: 1,658,592; xml: 842,302; asm: 722,011; pascal: 186,153; sh: 88,976; perl: 88,684; objc: 79,984; sql: 60,492; cs: 42,470; fortran: 24,101; makefile: 21,141; tcl: 15,277; php: 14,022; yacc: 9,154; ruby: 7,553; awk: 3,720; lisp: 3,233; lex: 1,328; ada: 727; jsp: 228; sed: 36
file content (19 lines) | stat: -rw-r--r-- 1,083 bytes parent folder | download | duplicates (11) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
 
This directory contains an implementation of the
[Open Screen](../../third_party/openscreen) platform API along with utility
functions, using the `//base` and `//net` directories in Chromium.

Any Chromium target that (indirectly) depends on
`//third_party/openscreen/src/platform:api` must also (indirectly) depend on one
of two components provided by this component. In nearly all cases, the dependency
should be in the same `deps` as `//third_party/openscreen/src/platform:api`.
Most external targets should depend on `//components/openscreen_platform`.
Targets that cannot use the Network Service should instead depend on
`//components/openscreen_platform:openscreen_platform_using_net_sockets`, which
uses a `//net`-based implementation of `UdpSocket`. These two targets are
incompatible with each other.

A very small set of intermediary targets that are used by both types of targets
above depend directly on
`//components/openscreen_platform:openscreen_platform_without_sockets` and
push the requirement to depend on one of the two public targets up to the
dependency chain.