Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
branch: master
Commits on Dec 21, 2011
  1. Tue Dec 20 19:48:57 2011 Google Inc. <opensource@google.com>

    csilvers authored
    	* google-gflags: version 1.7
    	* Add CommandLineFlagInfo::flag_ptr pointing to current storage (musji)
    	* PORTING: flush after writing to stderr, needed on cygwin
    	* PORTING: Clean up the GFLAGS_DLL_DECL stuff better
    	* Fix a bug in StringPrintf() that affected large strings (csilvers)
    	* Die at configure-time when g++ isn't installed
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@72 990008b9-e524-0410-ae84-45f8ed876473
Commits on Dec 1, 2011
  1. Clarify thread-safety comment for FlagSaver.

    csilvers+gflags@google.com authored
    Tested:
    blaze test base:commandlineflags_unittest
    
    R=csilvers
    DELTA=4  (3 added, 0 deleted, 1 changed)
    
    
    Revision created by MOE tool push_codebase.
    MOE_MIGRATION=3791
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@71 990008b9-e524-0410-ae84-45f8ed876473
Commits on Nov 3, 2011
  1. The last bit of rolling back commandlineflag categories:

    csilvers+gflags@google.com authored
    remove the 'categories' field from CommandLineFlagInfo.  (Note
    the code to fill this field was removed from
    FillComandLineFlagInfo previously, so it's been an empty
    string for some time now.)
    
    R=ncalvin
    DELTA=1  (0 added, 1 deleted, 0 changed)
    
    
    Revision created by MOE tool push_codebase.
    MOE_MIGRATION=3616
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@70 990008b9-e524-0410-ae84-45f8ed876473
  2. Get rid of the old FlagRegisterer constructor.

    csilvers+gflags@google.com authored
    R=jkline,georgevdd
    DELTA=27  (0 added, 27 deleted, 0 changed)
    
    
    Revision created by MOE tool push_codebase.
    MOE_MIGRATION=3609
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@69 990008b9-e524-0410-ae84-45f8ed876473
  3. Starting the rollback of flag categories.

    csilvers+gflags@google.com authored
    I left in the old FlagRegisterer constructor.
    I also left in 'categories' in CommandLineFlagInfo for now,
    though I never use it.  I doubt anyone else does either, but I
    want to minimize the number of ways this rollback can break
    the build.  I will remove it in a subsequent CL.
    
    R=ncalvin
    DELTA=121  (28 added, 55 deleted, 38 changed)
    
    
    Revision created by MOE tool push_codebase.
    MOE_MIGRATION=3574
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@68 990008b9-e524-0410-ae84-45f8ed876473
  4. Add a 'flag_ptr' field to CommandLineFlagInfo that points to the curr…

    csilvers+gflags@google.com authored
    …ent storage of the flag (i.e. &FLAGS_foo).
    
    R=csilvers
    DELTA=15  (15 added, 0 deleted, 0 changed)
    
    
    Revision created by MOE tool push_codebase.
    MOE_MIGRATION=3301
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@67 990008b9-e524-0410-ae84-45f8ed876473
  5. A user reported a bug that configure should die when g++ isn't

    csilvers+gflags@google.com authored
    installed, but wasn't:
    http://code.google.com/p/google-perftools/issues/detail?id=217
    
    This turned out to be a bug in autoconf:
    http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=357378
    
    The workaround is simple: check for CXX before checking for
    CC.  This means that if g++ is installed but gcc isn't, we
    won't die (at cc-checking time), but I tested, and the
    configure script dies later.  In any case, it seems unlikely
    someone would have a c++ compiler installed but not a c
    compiler.
    
    This fixes the 4 opensource projects I work on that are
    susceptible to this.
    
    R=iant
    DELTA=1437  (694 added, 694 deleted, 49 changed)
    
    
    Revision created by MOE tool push_codebase.
    MOE_MIGRATION=3222
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@66 990008b9-e524-0410-ae84-45f8ed876473
  6. Now I can get rid of the old constructor!

    csilvers+gflags@google.com authored
    R=jkline,ncalvin
    DELTA=28  (0 added, 27 deleted, 1 changed)
    
    
    Revision created by MOE tool push_codebase.
    MOE_MIGRATION=3169
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@65 990008b9-e524-0410-ae84-45f8ed876473
  7. http://code.google.com/p/google-gflags/issues/detail?id=45

    csilvers+gflags@google.com authored
    reports that the error isn't always getting flushed on
    cygwin.  So do that explicitly.
    
    R=desovski
    DELTA=1  (1 added, 0 deleted, 0 changed)
    
    
    Revision created by MOE tool push_codebase.
    MOE_MIGRATION=3140
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@64 990008b9-e524-0410-ae84-45f8ed876473
  8. Report category names via the xml help output (but not, yet,

    csilvers+gflags@google.com authored
    during 'normal' help output).
    
    R=ncalvin
    DELTA=3  (3 added, 0 deleted, 0 changed)
    
    
    Revision created by MOE tool push_codebase.
    MOE_MIGRATION=3066
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@63 990008b9-e524-0410-ae84-45f8ed876473
  9. Add back in a backwards-compatible constructor for

    csilvers+gflags@google.com authored
    FlagRegisterer.
    
    Because this backwards-compatible API is intended to be
    short-lived, I did it in the simplest, least invasive way
    possible, which involved cutting-and-pasting.
    
    R=ncalvin,jkline
    DELTA=27  (27 added, 0 deleted, 0 changed)
    
    
    Revision created by MOE tool push_codebase.
    MOE_MIGRATION=3065
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@62 990008b9-e524-0410-ae84-45f8ed876473
  10. NOTE: I'm checking this in just to have a record in source control of…

    csilvers+gflags@google.com authored
    … the idea. We've decided for now it doesn't make sense to go forward with flag categories -- and the __VA_ARGS__ for macros has caused lots of problems with uncaught accidental commas, already -- so a future commit will back this out. (Actually, it's all a series of commits, for annoying technical reasons.)
    
    Add support for flag categories.
    
    In this CL, all you can do is set categories in the DEFINE_*
    macros and then retrieve them via GetCommandLineFlagInfo and
    similar.
    
    In future CLs, we will start to give some semantic meaning to
    particular flag values, as described in the designdoc.  In
    particular, we will start to use flag categories to revamp
    --help output.
    
    Implementation-wise: to keep categories an optional macro
    argument, I had to use __VA_ARGS__, which means future gflags
    releases will no longer work with MSVC 7.1.  We're at MSVC 10
    now, so I'm pretty much ok with that.
    
    The downside of __VA_ARGS__ is there is no error if you
    specify more args after the ones we expect.  To get around
    that, I only use __VA_ARGS_ in this idiom:
    static const OptionalDefineArgs var = { __VA_ARGS__ };
    The new OptionalDefineArgs struct defines all the args that
    may be optionally specified in the DEFINE_* macros.  For now,
    that's only the 'categories' arg, though in theory more could be
    added later.
    
    R=titus,ncalvin
    DELTA=92  (54 added, 3 deleted, 35 changed)
    
    
    Revision created by MOE tool push_codebase.
    MOE_MIGRATION=3057
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@61 990008b9-e524-0410-ae84-45f8ed876473
Commits on Aug 18, 2011
  1. Clean up the 'GFLAGS_DLL_DECL' stuff better: reduce use outside of wi…

    csilvers+gflags@google.com authored
    …ndows/ directory.
    
    R=jyrki
    DELTA=33  (0 added, 27 deleted, 6 changed)
    
    
    Revision created by MOE tool push_codebase.
    MOE_MIGRATION=3016
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@60 990008b9-e524-0410-ae84-45f8ed876473
Commits on Aug 4, 2011
  1. Fix a bug in StringPrintf() that caused it to not print large strings…

    csilvers+gflags@google.com authored
    … properly.
    
    R=nilton
    DELTA=1  (0 added, 0 deleted, 1 changed)
    
    
    Revision created by MOE tool push_codebase.
    MOE_MIGRATION=2886
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@59 990008b9-e524-0410-ae84-45f8ed876473
  2. Add a new unittest case, that tests the --help output for a

    csilvers+gflags@google.com authored
    really long helpstring.  Opensource gflags had a bug where we
    were cutting off the output too soon; this test should protect
    against such a thing.
    
    R=nilton
    DELTA=16  (16 added, 0 deleted, 0 changed)
    
    
    Revision created by MOE tool push_codebase.
    MOE_MIGRATION=2885
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@58 990008b9-e524-0410-ae84-45f8ed876473
Commits on Jul 30, 2011
  1. Ready to release gflags 1.6!

    csilvers+gflags@google.com authored
    * 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: http://google-gflags.googlecode.com/svn/trunk@56 990008b9-e524-0410-ae84-45f8ed876473
  2. It turns out we don't want all this dll-decl stuff for mingw.

    csilvers+gflags@google.com authored
    So make the #ifdef correct for mscv-but-not-mingw.
    
    I think the right fix would be to take all this logic out and
    insert it via a MOE directive, just for the windows versions
    of these files.  This is what ctemplate does.  But it's a
    more-major change, and I'm looking to get this release out
    today, so I'm submitting this (TBR), since it's a much more
    minor change.
    
    
    Revision created by MOE tool push_codebase.
    MOE_MIGRATION=2837
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@55 990008b9-e524-0410-ae84-45f8ed876473
Commits on Jul 29, 2011
  1. mingw fixes:

    csilvers+gflags@google.com authored
    1) mingw needs an #include to have access to mkdir.
    
    2) It needs to always #include port.h (this is an identical
    bit of code, in configure.ac, that I have in other opensource
    projects for mingw support.)
    
    3) I moved some code from port.cc to port.h, so I didn't have
    to add logic to link in port.cc for mingw.
    
    Last change before new release!  (*knock on wood*)  Submitting
    TBR so I can get the release out today.  This isn't exactly a
    trivial change, so I'm chary to submit TBR, but it's pretty
    isolated to windows and mingw, and I've tested on those
    platforms to make sure they compile and all tests pass.
    
    DELTA=70  (37 added, 30 deleted, 3 changed)
    
    
    Revision created by MOE tool push_codebase.
    MOE_MIGRATION=2823
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@54 990008b9-e524-0410-ae84-45f8ed876473
  2. A few autotools files that it loosk like aren't needed by the latest

    csilvers authored
    version of autotools (taht we're using now).  Get rid of them to clean
    up the svn tree.  Also get rid of the 'python' file -- I don't know
    what that is, but it's been a long time since the python version of
    gflags has moved to its own project.
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@53 990008b9-e524-0410-ae84-45f8ed876473
  3. Some reorganization that results from a new method I'm moving to to

    csilvers authored
    maintaining this opensource tree.  Some of this reorganization is
    entirely a result of reorganization: blank lines in a few different
    places, etc.  Here are the others:
    
    1) I've added a new file, util.h, with lots of new, helpful routines,
    most notably StringPrintf (printf returning a string).  I've also
    moved some routines from the .cc and unittest.cc file here, such as
    the CHECK macros, testing framework, and #ifdefs for 16-bit ints.
    Quite a bit of code was rewritten to use these new routines.
    
    2) I noticed that the special-case setenv() code was only needed for
    windows systems, so I moved it to port.h/cc.
    
    3) I also had to add a new vsnprintf wrapper in port.h/cc, to support
    StringPrintf.
    
    4) A few places I used an old name, commandlineflags, instead of
    gflags.  Most or all of these should be fixed now.
    
    5) Some of my copyright dates weren't quite right.  Fixed them up.
    
    6) In some .cc files, I added using directives to not have to use
    std:: so much.
    
    7) I've added a minor new test, adding 10000 or so flags to see how
    the system scales.
    
    8) Some compile-warning fixes, such as int -> size_t when appropriate,
    and better protected #defines in mutex.h
    
    9) The .h files gained some logic defining GFLAGS_DLL_DECL.  This is
    true even for .h files outside the windows directory, which will never
    have these dll issues.  But one big advantage of my new organization
    is auto-generating the windows versions of these files from the unix
    versions, so there's some unnecessary (but harmless) duplication as a
    result.
    
    10) Fixed a bug in rpm.sh which would cause an unnecessary crash when
    dpkg was missing.
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@52 990008b9-e524-0410-ae84-45f8ed876473
  4. Update to automake 1.10.1 (from 1.9), and downdate to autoconf 2.62

    csilvers authored
    (from 2.65).  I'm moving to a new system for maintaining the
    opensource version, which involves using a 'hermetic' version of
    autotools, and those are the versions installed in the hermetic
    system.  There shouldn't be a user-noticeable change here.
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@51 990008b9-e524-0410-ae84-45f8ed876473
Commits on Jul 28, 2011
  1. * Minor correction for doc of shorthelp (soerenme, mecarson)

    csilvers authored
    	* Fix a bug where we were leaving out a required $(top_srcdir)
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@50 990008b9-e524-0410-ae84-45f8ed876473
Commits on May 19, 2011
  1. Update the windows version of the .h's to match the unix version.

    csilvers authored
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@49 990008b9-e524-0410-ae84-45f8ed876473
Commits on Apr 21, 2011
  1. * Split up flag declares into its own file (jyrki)

    csilvers authored
    	* Add --version support (csilvers)
    	* Fix doc typo (sudit)
    	* Update the README instructions for gflags with static libs (csilvers)
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@48 990008b9-e524-0410-ae84-45f8ed876473
Commits on Mar 3, 2011
  1. Add support for specifying a version number (SetVersionString()),

    csilvers authored
    which is then displayed in --version.
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@47 990008b9-e524-0410-ae84-45f8ed876473
Commits on Mar 2, 2011
  1. * Update acx_pthread.m4 for nostdlib (liujisi)

    csilvers authored
            * Typo fix in docs (bogdand)
            * Change ReparseCommandLineFlags to return void (csilvers)
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@46 990008b9-e524-0410-ae84-45f8ed876473
Commits on Jan 25, 2011
  1. Mon Jan 24 16:11:35 2011 Google Inc. <opensource@google.com>

    csilvers authored
    	* google-gflags: version 1.5
    	* Better reporting of current vs default value (handler)
    	* Add API for cleaning up of memory at program-exit (jmarantz)
    	* Fix macros to work inside namespaces (csilvers)
    	* Use our own string typedef in case string is redefined (csilvers)
    	* Updated to autoconf 2.65
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@44 990008b9-e524-0410-ae84-45f8ed876473
Commits on Jan 14, 2011
  1. * Remove reference to InitGoogle (csilvers)

    csilvers authored
    	* Remove superfluous friend declaration (mec)
    	* Better reporting of current vs default value (handler)
    	* Allow cleaning up of memory at program-exit (jmarantz)
    	* Put CompileAssert in correct namespace (csilvers)
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@43 990008b9-e524-0410-ae84-45f8ed876473
Commits on Nov 16, 2010
  1. * Use our own string typedef so macro is never confused (csilvers)

    csilvers authored
    	* Set up configure.ac to give proper library version numbers (csilvers)
    	* Update from autoconf 2.64 to 2.65.  Also hermeticize libtool a bit
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@42 990008b9-e524-0410-ae84-45f8ed876473
Commits on Oct 14, 2010
  1. Wed Oct 13 17:40:12 2010 Google Inc. <opensource@google.com>

    csilvers authored
    	* google-gflags: version 1.4
    	* Add a check to prevent passing 0 to DEFINE_string (jorg)
    	* Reduce compile (.o) size (jyrki)
    	* Some small changes to quiet debug compiles (alexk)
    	* PORTING: better support static linking on windows (csilvers)
    	* DOCUMENTATION: change default values, use validators, etc.
    	* Update the NEWS file to be non-empty
    	* Add pkg-config (.pc) files for libgflags and libgflags_nothreads
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@40 990008b9-e524-0410-ae84-45f8ed876473
Commits on Sep 16, 2010
  1. * Reduce .o size by decomposing switches (jyrki)

    csilvers authored
    	* Document how to change the default flag value (csilvers)
    	* Add a windows-specific README (csilvers)
    	* A few comment updates (wojtekm)
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@39 990008b9-e524-0410-ae84-45f8ed876473
Commits on May 7, 2010
  1. * Added a contentful NEWS file (csilvers)

    csilvers authored
    	* Fixed email address in maintainers to actually work (csilvers)
    	* Update docs with info on validators (wojtekm)
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@38 990008b9-e524-0410-ae84-45f8ed876473
Commits on Mar 10, 2010
  1. * Get rid of unnecessary c++ aliasing violation (csilvers)

    csilvers authored
    	* Better error message on parse failure (tstromberg)
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@37 990008b9-e524-0410-ae84-45f8ed876473
Commits on Jan 5, 2010
  1. Mon Jan 4 18:09:30 2010 Google Inc. <opensource@google.com>

    csilvers authored
    	* google-gflags: version 1.3
    	* PORTABILITY: can now build and run tests under MSVC (csilvers)
    	* Remove the python gflags code, which is now its own package (tansell)
    	* Clarify that "last flag wins" in the docs (csilvers)
    	* Comment danger of using GetAllFlags in validators (wojtekm)
    	* PORTABILITY: Some fixes necessary for c++0x (mboerger)
    	* Makefile fix: $(srcdir) -> $(top_srcdir) in one place (csilvres)
    	* INSTALL: autotools to autoconf v2.64 + automake v1.11 (csilvers)
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@35 990008b9-e524-0410-ae84-45f8ed876473
Commits on Nov 10, 2009
  1. * PORTING: Add windows (MSVC) support (csilvers)

    csilvers authored
    	* Comment danger of using GetAllFlags in validators (wojtekm)
    	* Add python support for gnu_getopt (hobe)
    	* DEFINE_list now accepts a list as a default (dsturtevant)
    	* TMPDIR -> TEST_TMPDIR in Makefile, fixing objcopy behavior (csilvers)
    	* Fix the 'cp' command to use $(top_srcdir) in the Makefile (csilvers)
    
    
    
    git-svn-id: http://google-gflags.googlecode.com/svn/trunk@34 990008b9-e524-0410-ae84-45f8ed876473
Something went wrong with that request. Please try again.