Lines Matching +full:ci +full:- +full:cmake
1 [](https://travis-ci.org/gfla…
2 [![Build status](https://ci.appveyor.com/api/projects/status/4ctod566ysraus74/branch/master?svg=tru…
8 ----------------
14 The build targets exported by the CMake configuration of this library are now also prefixed by the …
15 name "gflags::" following a more recent (unwritten) CMake convention. The unprefixed target names a…
22 ------------
33 ----------------
38 not only in projects using CMake, but also [Bazel](https://bazel.build/),
39 or [pkg-config](https://www.freedesktop.org/wiki/Software/pkg-config/).
52 -------------
60 This can be overridden using the CMake variable GFLAGS_NAMESPACE.
63 CMake modules FindThreads.cmake and CheckTypeSize.cmake. These have
76 -------------
81 and adds a separate GFLAGS\_INCLUDE\_DIR CMake variable to the build configuration.
88 -------------
92 The major changes are the use of CMake for the build configuration instead
110 [Git branching model](http://nvie.com/posts/a-successful-git-branching-model/)
118 ---------------
120 The migration of the build system to CMake is almost complete.
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 -------------
136 I believe that the strengths of [Git](http://git-scm.com/) will allow for better community collabor…
155 is the migration from autotools to [CMake](http://www.cmake.org/).
157 [cmake-migration](https://github.com/schuhschuh/gflags/tree/cmake-migration)
162 ---------------
166 The `google-gflags` project has been renamed to `gflags`. I
183 ---------------
185 The `google-gflags` Google Code page has been renamed to
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 ---------------
245 --------------
248 all tests pass. I **really** never thought non-unix-y Windows folks
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
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
290 let me know. I'm excited to finally have 64-bit package files, but
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-gflags@googlegroups.com`!
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.