25b39ab1a6
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 |
||
---|---|---|
.. | ||
gen | ||
gflags.gyp | ||
LICENSE | ||
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.