This eases integration with other applications making use
of gflags without needing to install it in the system.
find_package looks in the registry for existing software.
* gflags: version 2.0
* Changed the 'official' gflags email in setup.py/etc
* Renamed google-gflags.sln to gflags.sln
* Changed copyright text to reflect Google's relinquished ownership
git-svn-id: https://gflags.googlecode.com/svn/trunk@74 6586e3c6-dcc4-952a-343f-ff74eb82781d
* 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: https://gflags.googlecode.com/svn/trunk@72 6586e3c6-dcc4-952a-343f-ff74eb82781d
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: https://gflags.googlecode.com/svn/trunk@70 6586e3c6-dcc4-952a-343f-ff74eb82781d
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: https://gflags.googlecode.com/svn/trunk@68 6586e3c6-dcc4-952a-343f-ff74eb82781d
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: https://gflags.googlecode.com/svn/trunk@66 6586e3c6-dcc4-952a-343f-ff74eb82781d
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: https://gflags.googlecode.com/svn/trunk@64 6586e3c6-dcc4-952a-343f-ff74eb82781d
