webrtc

History

fischman@webrtc.org 2c89b5cb27 Make everyone an OWNER for .gyp/.gypi add/delete purposes, non-talk/ edition. This CL brought to you by: $ for d in $(for f in $(git ls-files 'gyp' 'gypi'); do dirname $f; done\|sort\|uniq\|grep -v '^\.$'); do echo -e "\n# These are for the common case of adding or renaming files. If you're doing\n# structural changes, please get a review from a reviewer in this file.\nper-file .gyp=\nper-file .gypi=" >> $d/OWNERS; done $ for d in $(for f in $(git ls-files 'gyp' 'gypi'); do dirname $f; done\|sort\|uniq\|grep -v '^\.$'); do git add $d/OWNERS; done (and then removed the talk/ impact) R=niklas.enbom@webrtc.org Review URL: https://webrtc-codereview.appspot.com/11969004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@5903 4adac7df-926f-26a2-2b94-8c16560cd09d		2014-04-14 20:08:03 +00:00
..
gen	Document updating gflags and remove code duplication.	2013-08-20 16:17:10 +00:00
gflags.gyp	Document updating gflags and remove code duplication.	2013-08-20 16:17:10 +00:00
LICENSE	Roll chromium_revision 214260:217707 and gflags 45:84	2013-08-15 23:31:30 +00:00
OWNERS	Make everyone an OWNER for .gyp/.gypi add/delete purposes, non-talk/ edition.	2014-04-14 20:08:03 +00:00
README.webrtc	Document updating gflags and remove code duplication.	2013-08-20 16:17:10 +00: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.