gflags-v2.2.0.tar.gz

[](https://travis-ci.org/gflags/gflags) [](https://ci.appveyor.com/project/schuhschuh/gflags/branch/master) 25 November 2016 ---------------- I've finally released gflags 2.2.0. This release adds support for use of the gflags library as external dependency not only in projects using CMake, but also [Bazel](https://bazel.build/), or [pkg-config](https://www.freedesktop.org/wiki/Software/pkg-config/). One new minor feature is added in this release: when a command flag argument contains dashes, these are implicitly converted to underscores. This is to allow those used to separate words of the flag name by dashes to do so, while the flag variable names are required to use underscores. Memory leaks reported by valgrind should be resolved by this release. This release fixes build errors with MS Visual Studio 2015. Please report any further issues with this release using the GitHub issue tracker. 24 March 2015 ------------- I've just released gflags 2.1.2. This release completes the namespace change fixes. In particular, it restores binary ABI compatibility with release version 2.0. The deprecated "google" namespace is by default still kept as primary namespace while symbols are imported into the new "gflags" namespace. This can be overridden using the CMake variable GFLAGS_NAMESPACE. Other fixes of the build configuration are related to the (patched) CMake modules FindThreads.cmake and CheckTypeSize.cmake. These have been removed and instead the C language is enabled again even though gflags is written in C++ only. This release also marks the complete move of the gflags project from Google Code to GitHub. Email addresses of original issue reporters got lost in the process. Given the age of most issue reports, this should be negligable. Please report any further issues using the GitHub issue tracker. 30 March 2014 ------------- I've just released gflags 2.1.1. This release fixes a few bugs in the configuration of gflags\_declare.h and adds a separate GFLAGS\_INCLUDE\_DIR CMake variable to the build configuration. Setting GFLAGS\_NAMESPACE to "google" no longer changes also the include path of the public header files. This allows the use of the library with other Google projects such as glog which still use the deprecated "google" namespace for the gflags library, but include it as "gflags/gflags.h". 20 March 2014 ------------- I've just released gflags 2.1. The major changes are the use of CMake for the build configuration instead of the autotools and packaging support through CPack. The default namespace of all C++ symbols is now "gflags" instead of "google". This can be configured via the GFLAGS\_NAMESPACE variable. This release compiles with all major compilers without warnings and passed the unit tests on Ubuntu 12.04, Windows 7 (Visual Studio 2008 and 2010, Cygwin, MinGW), and Mac OS X (Xcode 5.1). The SVN repository on Google Code is now frozen and replaced by a Git repository such that it can be used as Git submodule by projects. The main hosting of this project remains at Google Code. Thanks to the distributed character of Git, I can push (and pull) changes from both GitHub and Google Code in order to keep the two public repositories in sync. When fixing an issue for a pull request through either of these hosting platforms, please reference the issue number as [described here](https://code.google.com/p/support/wiki/IssueTracker#Integration_with_version_control). For the further development, I am following the [Git branching model](http://nvie.com/posts/a-successful-git-branching-model/) with feature branch names prefixed by "feature/" and bugfix branch names prefixed by "bugfix/", respectively. Binary and source [packages](https://github.com/schuhschuh/gflags/releases) are available on GitHub. 14 January 2014 --------------- The migration of the build system to CMake is almost complete. What remains to be done is rewriting the tests in Python such they can be executed on non-Unix platforms and splitting them up into separate CTest tests. Though merging these changes into the master branch yet remains to be done, it is recommended to already start using the [cmake-migration](https://github.com/schuhschuh/gflags/tree/cmake-migration) branch. 20 April 2013 ------------- More than a year has past since I (Andreas) took over the maintenance for `gflags`. Only few minor changes have been made since then, much to my regret. To get more involved and stimulate participation in the further development of the library, I moved the project source code today to [GitHub](https://github.com/schuhschuh/gflags). I believe that the strengths of [Git](http://git-scm.com/) will allow for better community collaboration as well as ease the integration of changes made by others. I encourage everyone who would like to contribute to send me pull requests. Git's lightweight feature branches will also provide the right tool for more radical changes which should only be merged back into the master branch after these are complete and implement the desired behavior. The SVN repository remains accessible at Google Code and I will keep the master branch of the Git repository hosted at GitHub and the trunk of the Subversion repository synchronized. Initially, I was going to simply switch the Google Code project to Git, but in this case the SVN repository would be frozen and force everyone who would like the latest development changes to use Git as well. Therefore I decided to host the public Git repository at GitHub instead. Please continue to report any issues with gflags on Google Code. The GitHub project will only be used to host the Git repository. One major change of the project structure I have in mind for the next weeks is the migration from autotools to [CMake](http://www.cmake.org/). Check out the (unstable!) [cmake-migration](https://github.com/schuhschuh/gflags/tree/cmake-migration) branch on GitHub for details. 25 January 2012 --------------- I've just released gflags 2.0. The `google-gflags` project has been renamed to `gflags`. I (csilvers) am stepping down as maintainer, to be replaced by Andreas Schuh. Welcome to the team, Andreas! I've seen the energy you have around gflags and the ideas you have for the project going forward, and look forward to having you on the team. I bumped the major version number up to 2 to reflect the new community ownership of the project. All the [changes](ChangeLog.txt) are related to the renaming. There are no functional changes from gflags 1.7. In particular, I've kept the code in the namespace `google`, though in a future version it should be renamed to `gflags`. I've also kept the `/usr/local/include/google/` subdirectory as synonym of `/usr/local/include/gflags/`, though the former name has been obsolete for some time now. 18 January 2011 --------------- The `google-gflags` Google Code page has been renamed to `gflags`, in preparation for the project being renamed to `gflags`. In the coming weeks, I'll be stepping down as maintainer for the gflags project, and as part of that Google is relinquishing ownership of the project; it will now be entirely community run. The name change reflects that shift. 20 December 2011 ---------------- I've just released gflags 1.7. This is a minor release; the major change is that `CommandLineFlagInfo` now exports the address in memory where the flag is located. There has also been a bugfix involving very long --help strings, and some other minor [changes](ChangeLog.txt). 29 July 2011 ------------ I've just released gflags 1.6. The major new feature in this release is support for setting version info, so that --version does something useful. One minor change has required bumping the library number: `ReparseCommandlineFlags` now returns `void` instead of `int` (the int return val