gecko-dev/media/webrtc/trunk/third_party/gflags
Dan Minor 6fa2ea51b7 Bug 1371485 - Fix gflags root; r=chmanchester
Summary:
I think the webrtc.org gtests are the only user of gflags in tree. We can switch
over to using gn to build this when we start building the tests using gn,
which is Bug 1430779.

Tags: #secure-revision

Bug #: 1371485

Differential Revision: https://phabricator.services.mozilla.com/D1802

--HG--
extra : rebase_source : ba496d6f262d3679031f0b933a80ce3e2a2236a5
2018-06-22 14:25:31 -04:00
..
gen
src
BUILD.gn
LICENSE
OWNERS
README.webrtc
codereview.settings
gflags.gyp Bug 1371485 - Fix gflags root; r=chmanchester 2018-06-22 14:25:31 -04:00

README.webrtc

URL: http://code.google.com/p/gflags/
Version: 2.0
License: New BSD
License File: LICENSE

Description:
The gflags package contains a library that implements commandline
flags processing. As such it's a replacement for getopt(). It has
increased flexibility, including built-in support for C++ types like
string, and the ability to define flags in the source file in which
they're used.

Local Modifications: None


How to update platform configuration files:
The gen/ directory contains pre-generated configuration header files.
Historically, all operating systems and architectures have generated
similar configurations except for Windows. This is why there's only
posix and win directories below gen/.
When rolling gflags to a newer version, it's a good idea to check if
new configuration files needs to be generated as well.
Do this by running ./configure in the newly checked out version of
gflags. Then diff the generated files with the ones below gen/.
If you notice a diff, update the files with the updated ones.
If you suspect platform dependend changes other than Windows, you'll
have to checkout gflags on the other platforms as well and run
./configure there too.