File: README.md

package info (click to toggle)
chromium 140.0.7339.185-1
  • links: PTS, VCS
  • area: main
  • in suites: forky
  • size: 6,193,740 kB
  • sloc: cpp: 35,093,945; ansic: 7,161,670; javascript: 4,199,694; python: 1,441,797; asm: 949,904; xml: 747,515; pascal: 187,748; perl: 88,691; sh: 88,248; objc: 79,953; sql: 52,714; cs: 44,599; fortran: 24,137; makefile: 22,114; tcl: 15,277; php: 13,980; yacc: 9,000; ruby: 7,485; awk: 3,720; lisp: 3,096; lex: 1,327; ada: 727; jsp: 228; sed: 36
file content (19 lines) | stat: -rw-r--r-- 1,083 bytes parent folder | download | duplicates (9) 
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.