Lines Matching +full:some +full:- +full:project +full:- +full:name
1 [](https://travis-ci.org/gfla…
2 …status/4ctod566ysraus74/branch/master?svg=true)](https://ci.appveyor.com/project/schuhschuh/gflags…
8 ----------------
15 name "gflags::" following a more recent (unwritten) CMake convention. The unprefixed target names a…
22 ------------
33 ----------------
39 or [pkg-config](https://www.freedesktop.org/wiki/Software/pkg-config/).
42 This is to allow those used to separate words of the flag name by dashes
52 -------------
67 This release also marks the complete move of the gflags project
76 -------------
88 -------------
103 hosting of this project remains at Google Code. Thanks to the distributed
110 [Git branching model](http://nvie.com/posts/a-successful-git-branching-model/)
118 ---------------
122 executed on non-Unix platforms and splitting them up into separate CTest tests.
125 [cmake-migration](https://github.com/schuhschuh/gflags/tree/cmake-migration) branch.
129 -------------
134 development of the library, I moved the project source code today to
136 I believe that the strengths of [Git](http://git-scm.com/) will allow for better community collabor…
146 Google Code project to Git, but in this case the SVN repository would be
151 Please continue to report any issues with gflags on Google Code. The GitHub project will
154 One major change of the project structure I have in mind for the next weeks
157 [cmake-migration](https://github.com/schuhschuh/gflags/tree/cmake-migration)
162 ---------------
166 The `google-gflags` project has been renamed to `gflags`. I
169 around gflags and the ideas you have for the project going forward,
173 ownership of the project. All the [changes](ChangeLog.txt)
178 synonym of `/usr/local/include/gflags/`, though the former name has
179 been obsolete for some time now.
183 ---------------
185 The `google-gflags` Google Code page has been renamed to
186 `gflags`, in preparation for the project being renamed to
188 maintainer for the gflags project, and as part of that Google is
189 relinquishing ownership of the project; it will now be entirely
190 community run. The name change reflects that shift.
194 ----------------
199 very long --help strings, and some other minor [changes](ChangeLog.txt).
202 ------------
205 is support for setting version info, so that --version does something
215 internal tools used to integrate Google-supplied patches for gflags
224 ---------------
227 from 1.4, including some slightly better reporting in --help, and
228 an new memory-cleanup function that can help when running gflags-using
237 ---------------
240 from 1.3, including some documentation tweaks and some work to make
245 --------------
248 all tests pass. I **really** never thought non-unix-y Windows folks
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).
257 -----------------
261 never thought Windows folks would want unix-style command-line flags,
265 The other changes are minor, such as support for --htmlxml in the
269 -------------
278 libgflags.so, but the deb file created libgoogle-gflags.so. I have
280 in debian packaging, but I believe this has caused the package name to
282 [[mailto:google-[email protected]](mailto:google-[email protected])
283 google-[email protected]]) if this causes problems for you --
285 packages to add symlinks from the old library name to the new
286 (libgoogle-gflags.so -> libgflags.so), but that is beyond my knowledge
290 let me know. I'm excited to finally have 64-bit package files, but
291 there may still be some wrinkles in the new system to iron out.
294 --------------
299 `/usr/include/gflags`. While I have backwards-compatibility
311 --help` to see the flags). If you have feedback as to whether the
313 non-backwards-compatible change, send mail to
314 `google-[email protected]`!
316 Version 1.0 also has some neat new features, like support for bash
317 commandline-completion of help flags. See the [ChangeLog](ChangeLog.txt)
320 If I don't hear any bad news for a few weeks, I'll release 1.0-final.