Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in / Register
Toggle navigation
G
gflags
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Packages
Packages
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
submodule
gflags
Commits
3d2a101c
Commit
3d2a101c
authored
Nov 11, 2018
by
Andreas Schuh
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
doc: Update README for release v2.2.2
parent
af502c81
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
15 additions
and
0 deletions
+15
-0
README.md
README.md
+15
-0
No files found.
README.md
View file @
3d2a101c
...
@@ -3,6 +3,21 @@
...
@@ -3,6 +3,21 @@
The documentation of the gflags library is available online at https://gflags.github.io/gflags/.
The documentation of the gflags library is available online at https://gflags.github.io/gflags/.
11 November 2018
----------------
I've just released gflags 2.2.2.
This maintenance release improves lives of Bazel users (no more "config.h" leaking into global include paths),
fixes build with recent MinGW versions, and silences a number of static code analyzer and compiler warnings.
The build targets exported by the CMake configuration of this library are now also prefixed by the package
name "gflags::" following a more recent (unwritten) CMake convention. The unprefixed target names are still
supported to avoid that dependent projects have to be modified due to this change in imported target names.
Please report any further issues with this release using the GitHub issue tracker.
11 July 2017
11 July 2017
------------
------------
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment