Commit 404970d6 authored by Craig Silverstein's avatar Craig Silverstein

Ready to release gflags 1.6!

* google-gflags: version 1.6
* BUGFIX: Fix a bug where we were leaving out a required $(top_srcdir)
* Fix definition of clstring (jyrki)
* Split up flag declares into its own file (jyrki)
* Add --version support (csilvers)
* Update teh README for gflags with static libs
* Update acx_pthread.m4 for nostdlib
* Change REparseCommandLineFlags to return void (csilvers)
* Some doc typofixes and example augmentation (various)

R=jperkins
DELTA=44  (41 added, 0 deleted, 3 changed)


Revision created by MOE tool push_codebase.
MOE_MIGRATION=2838


git-svn-id: https://gflags.googlecode.com/svn/trunk@56 6586e3c6-dcc4-952a-343f-ff74eb82781d
parent a923d333
Fri Jul 29 19:05:21 2011 Google Inc. <opensource@google.com>
* google-gflags: version 1.6
* BUGFIX: Fix a bug where we were leaving out a required $(top_srcdir)
* Fix definition of clstring (jyrki)
* Split up flag declares into its own file (jyrki)
* Add --version support (csilvers)
* Update the README for gflags with static libs
* Update acx_pthread.m4 for nostdlib
* Change ReparseCommandLineFlags to return void (csilvers)
* Some doc typofixes and example augmentation (various)
Mon Jan 24 16:11:35 2011 Google Inc. <opensource@google.com>
* google-gflags: version 1.5
......
== 24 January 2011 ==
== 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 value was always meaningless). Though I doubt anyone ever used
this (meaningless) return value, technically it's a change to the ABI
that requires a version bump. A bit sad.
There's also a procedural change with this release: I've changed the
internal tools used to integrate Google-supplied patches for gflags
into the opensource release. These new tools should result in more
frequent updates with better change descriptions. They will also
result in future `ChangeLog` entries being much more verbose (for better
or for worse).
See the
[http://code.google.com/p/google-gflags/source/browse/tags/gflags-1.6/ChangeLog ChangeLog]
for a full list of changes for this release.
=== 24 January 2011 ===
I've just released gflags 1.5. This release has only minor changes
from 1.4, including some slightly better reporting in --help, and
......
#! /bin/sh
# Guess values for system-dependent variables and create Makefiles.
# Generated by GNU Autoconf 2.62 for gflags 1.5.
# Generated by GNU Autoconf 2.62 for gflags 1.6.
#
# Report bugs to <opensource@google.com>.
#
......@@ -745,8 +745,8 @@ SHELL=${CONFIG_SHELL-/bin/sh}
# Identity of this package.
PACKAGE_NAME='gflags'
PACKAGE_TARNAME='gflags'
PACKAGE_VERSION='1.5'
PACKAGE_STRING='gflags 1.5'
PACKAGE_VERSION='1.6'
PACKAGE_STRING='gflags 1.6'
PACKAGE_BUGREPORT='opensource@google.com'
ac_unique_file="README"
......@@ -1496,7 +1496,7 @@ if test "$ac_init_help" = "long"; then
# Omit some internal or obsolete options to make the list less imposing.
# This message is too long to be a string in the A/UX 3.1 sh.
cat <<_ACEOF
\`configure' configures gflags 1.5 to adapt to many kinds of systems.
\`configure' configures gflags 1.6 to adapt to many kinds of systems.
Usage: $0 [OPTION]... [VAR=VALUE]...
......@@ -1566,7 +1566,7 @@ fi
if test -n "$ac_init_help"; then
case $ac_init_help in
short | recursive ) echo "Configuration of gflags 1.5:";;
short | recursive ) echo "Configuration of gflags 1.6:";;
esac
cat <<\_ACEOF
......@@ -1672,7 +1672,7 @@ fi
test -n "$ac_init_help" && exit $ac_status
if $ac_init_version; then
cat <<\_ACEOF
gflags configure 1.5
gflags configure 1.6
generated by GNU Autoconf 2.62
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001,
......@@ -1686,7 +1686,7 @@ cat >config.log <<_ACEOF
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by gflags $as_me 1.5, which was
It was created by gflags $as_me 1.6, which was
generated by GNU Autoconf 2.62. Invocation command line was
$ $0 $@
......@@ -2054,7 +2054,7 @@ ac_compiler_gnu=$ac_cv_c_compiler_gnu
# Update this value for every release! (A:B:C will map to foo.so.(A-C).C.B)
# http://www.gnu.org/software/libtool/manual/html_node/Updating-version-info.html
SO_VERSION=1:0:1
SO_VERSION=2:0:0
# The argument here is just something that should be in the current directory
# (for sanity checking)
......@@ -2408,7 +2408,7 @@ fi
# Define the identity of the package.
PACKAGE='gflags'
VERSION='1.5'
VERSION='1.6'
cat >>confdefs.h <<_ACEOF
......@@ -18469,7 +18469,7 @@ exec 6>&1
# report actual input values of CONFIG_FILES etc. instead of their
# values after options handling.
ac_log="
This file was extended by gflags $as_me 1.5, which was
This file was extended by gflags $as_me 1.6, which was
generated by GNU Autoconf 2.62. Invocation command line was
CONFIG_FILES = $CONFIG_FILES
......@@ -18522,7 +18522,7 @@ Report bugs to <bug-autoconf@gnu.org>."
_ACEOF
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
ac_cs_version="\\
gflags config.status 1.5
gflags config.status 1.6
configured by $0, generated by GNU Autoconf 2.62,
with options \\"`$as_echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`\\"
......
......@@ -4,10 +4,10 @@
# make sure we're interpreted by some minimal autoconf
AC_PREREQ(2.57)
AC_INIT(gflags, 1.5, opensource@google.com)
AC_INIT(gflags, 1.6, opensource@google.com)
# Update this value for every release! (A:B:C will map to foo.so.(A-C).C.B)
# http://www.gnu.org/software/libtool/manual/html_node/Updating-version-info.html
SO_VERSION=1:0:1
SO_VERSION=2:0:0
# The argument here is just something that should be in the current directory
# (for sanity checking)
......
gflags (1.6-1) unstable; urgency=low
* New upstream release.
-- Google Inc. <opensource@google.com> Fri, 29 Jul 2011 19:05:21 -0700
gflags (1.5-1) unstable; urgency=low
* New upstream release.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment