• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..30-Mar-2022-

gen/H30-Mar-2022-2,193776

src/H30-Mar-2022-8,2145,041

BUILD.gnH A D30-Mar-20221.9 KiB6554

LICENSEH A D30-Mar-20221.4 KiB2925

OWNERSH A D30-Mar-2022226 85

README.webrtcH A D30-Mar-20221.1 KiB2924

codereview.settingsH A D30-Mar-2022153 53

gflags.gypH A D30-Mar-20223 KiB9391

README.webrtc

1URL: http://code.google.com/p/gflags/
2Version: 2.0
3License: New BSD
4License File: LICENSE
5
6Description:
7The gflags package contains a library that implements commandline
8flags processing. As such it's a replacement for getopt(). It has
9increased flexibility, including built-in support for C++ types like
10string, and the ability to define flags in the source file in which
11they're used.
12
13Local Modifications: None
14
15
16How to update platform configuration files:
17The gen/ directory contains pre-generated configuration header files.
18Historically, all operating systems and architectures have generated
19similar configurations except for Windows. This is why there's only
20posix and win directories below gen/.
21When rolling gflags to a newer version, it's a good idea to check if
22new configuration files needs to be generated as well.
23Do this by running ./configure in the newly checked out version of
24gflags. Then diff the generated files with the ones below gen/.
25If you notice a diff, update the files with the updated ones.
26If you suspect platform dependend changes other than Windows, you'll
27have to checkout gflags on the other platforms as well and run
28./configure there too.
29