generic-library/webrtc
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
c3c9015bc6
webrtc/third_party/gflags/README.webrtc

29 lines
1.1 KiB
Plaintext
Raw Normal View History

Roll chromium_revision 214260:217707 and gflags 45:84 gflags roll is needed mostly to pick up fixes for warnings triggered by newer compiler/settings pulled in by the chromium roll. Had to switch from the old google-gflags project the current gflags project to pick up this fix (see https://code.google.com/p/gflags/source/detail?r=74 for details). Update android build.xml file to reflect tools moves in new SDK pulled in by the chromium_revision roll. R=niklas.enbom@webrtc.org, wu@webrtc.org Review URL: https://webrtc-codereview.appspot.com/2043004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@4555 4adac7df-926f-26a2-2b94-8c16560cd09d
2013-08-16 01:31:30 +02:00
URL: http://code.google.com/p/gflags/
Version: 2.0
google-gflags is an open source command line parsing library for C++ that is useful for our test programs. The GYP file and the platform specific configurations in this CL is copied from the Page Speed project (http://code.google.com/p/page-speed) that also uses this library. Review URL: http://webrtc-codereview.appspot.com/140009 git-svn-id: http://webrtc.googlecode.com/svn/trunk@569 4adac7df-926f-26a2-2b94-8c16560cd09d
2011-09-09 15:00:24 +02:00
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
Roll chromium_revision 214260:217707 and gflags 45:84 gflags roll is needed mostly to pick up fixes for warnings triggered by newer compiler/settings pulled in by the chromium roll. Had to switch from the old google-gflags project the current gflags project to pick up this fix (see https://code.google.com/p/gflags/source/detail?r=74 for details). Update android build.xml file to reflect tools moves in new SDK pulled in by the chromium_revision roll. R=niklas.enbom@webrtc.org, wu@webrtc.org Review URL: https://webrtc-codereview.appspot.com/2043004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@4555 4adac7df-926f-26a2-2b94-8c16560cd09d
2013-08-16 01:31:30 +02:00
Document updating gflags and remove code duplication. When rolling the google-gflags dependency, there might be a need of updating the generated configuration files. I added a instructions to the README.webrtc file for doing that. This CL also removes duplicated configuration headers so we only separete the ones that differs (Windows and everything else). BUG=2251 TEST=none R=fischman@webrtc.org, niklas.enbom@webrtc.org Review URL: https://webrtc-codereview.appspot.com/2046004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@4574 4adac7df-926f-26a2-2b94-8c16560cd09d
2013-08-20 18:17:10 +02:00
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.
Reference in New Issue Copy Permalink