Lines Matching refs:gflags
1 [![Build Status](https://travis-ci.org/gflags/gflags.svg?branch=master)](https://travis-ci.org/gfla…
2 …6ysraus74/branch/master?svg=true)](https://ci.appveyor.com/project/schuhschuh/gflags/branch/master)
4 The documentation of the gflags library is available online at https://gflags.github.io/gflags/.
10 I've just released gflags 2.2.2.
15 name "gflags::" following a more recent (unwritten) CMake convention. The unprefixed target names a…
24 I've just released gflags 2.2.1.
35 I've finally released gflags 2.2.0.
37 This release adds support for use of the gflags library as external dependency
54 I've just released gflags 2.1.2.
59 primary namespace while symbols are imported into the new "gflags" namespace.
65 gflags is written in C++ only.
67 This release also marks the complete move of the gflags project
78 I've just released gflags 2.1.1.
80 This release fixes a few bugs in the configuration of gflags\_declare.h
85 namespace for the gflags library, but include it as "gflags/gflags.h".
90 I've just released gflags 2.1.
94 of all C++ symbols is now "gflags" instead of "google". This can be
114 Binary and source [packages](https://github.com/schuhschuh/gflags/releases) are available on GitHub.
125 [cmake-migration](https://github.com/schuhschuh/gflags/tree/cmake-migration) branch.
132 `gflags`. Only few minor changes have been made since then, much to my regret.
135 [GitHub](https://github.com/schuhschuh/gflags).
151 Please continue to report any issues with gflags on Google Code. The GitHub project will
157 [cmake-migration](https://github.com/schuhschuh/gflags/tree/cmake-migration)
164 I've just released gflags 2.0.
166 The `google-gflags` project has been renamed to `gflags`. I
169 around gflags and the ideas you have for the project going forward,
175 gflags 1.7. In particular, I've kept the code in the namespace
176 `google`, though in a future version it should be renamed to `gflags`.
178 synonym of `/usr/local/include/gflags/`, though the former name has
185 The `google-gflags` Google Code page has been renamed to
186 `gflags`, in preparation for the project being renamed to
187 `gflags`. In the coming weeks, I'll be stepping down as
188 maintainer for the gflags project, and as part of that Google is
196 I've just released gflags 1.7. This is a minor release; the major
204 I've just released gflags 1.6. The major new feature in this release
215 internal tools used to integrate Google-supplied patches for gflags
226 I've just released gflags 1.5. This release has only minor changes
228 an new memory-cleanup function that can help when running gflags-using
239 I've just released gflags 1.4. This release has only minor changes
247 I've just released gflags 1.3. gflags now compiles under MSVC, and
249 would want gflags, but at least some of them do.
252 into its own library, [python-gflags](http://code.google.com/p/python-gflags).
253 If you're interested in the Python version of gflags, that's the place to
259 I've just released gflags 1.2. The major change from gflags 1.1 is it
266 python version of gflags.
271 I've just released gflags 1.1. It has only minor changes fdrom gflags
278 libgflags.so, but the deb file created libgoogle-gflags.so. I have
282 [[mailto:google-gflags@googlegroups.com](mailto:google-gflags@googlegroups.com)
283 google-gflags@googlegroups.com]) if this causes problems for you --
286 (libgoogle-gflags.so -> libgflags.so), but that is beyond my knowledge
296 gflags 1.0rc2 was out for a few weeks without any issues, so gflags
297 1.0 is now released. This is much like gflags 0.9. The major change
299 `/usr/include/gflags`. While I have backwards-compatibility
302 #include <gflags/gflags.h>
306 #include <google/gflags.h>
312 default namespace should change to gflags, which would be a
314 `google-gflags@googlegroups.com`!