* ctemplate: version 2.0 release
* Changed the 'official' ctemplate email in setup.py/etc
* Rewrote docs to refer to Ctemplate, not Google Template
* Renamed google-ctemplate.sln to ctemplate.sln
* Changed copyright text to reflect Google's relinquished ownership
* ctemplate: version 1.1 release
* Make reloads always prefer files earlier on the search patch (ssas)
* PORTING: Add a default BSWAP32, needed for AIX (csilvers)
* Die at configure-time when g++ isn't installed
util.h. We need to override that version with a 'real' (but
simplistic) version in template.cc. The other option would be
to have a 'real' definition everywhere, but that's not
necessary at this juncture.
R=jad
DELTA=2 (1 added, 0 deleted, 1 changed)
Revision created by MOE tool push_codebase.
MOE_MIGRATION=3980
using the default constructor of T.
Tested:
blaze test //base/...
blaze test --compiler=gcc-4.6.x-cxx0x //base/...
R=csilvers
DELTA=3 (3 added, 0 deleted, 0 changed)
Revision created by MOE tool push_codebase.
MOE_MIGRATION=3961
another template has been added with the same name earlier in the search path,
even if the original file is NOT updated(touched, updated, deleted etc).
Tested:
blaze test template:all
R=panicker,csilvers
DELTA=45 (6 added, 24 deleted, 15 changed)
Revision created by MOE tool push_codebase.
MOE_MIGRATION=3885
See http://wiki/Main/LogFatalVsCheckFalse for details. While I'm here,
fix a couple of cases of CHECK("message" != NULL) and remove some dead
code that our compilers are now smart enough to not need.
R=falmeida
DELTA=5 (0 added, 2 deleted, 3 changed)
Revision created by MOE tool push_codebase.
MOE_MIGRATION=3617
the opensource shims to be able to compile that. This is a
bit of a hack.
R=chandlerc
DELTA=5 (5 added, 0 deleted, 0 changed)
Revision created by MOE tool push_codebase.
MOE_MIGRATION=3313
which properly indicates a no-return point in the CFG. This should have no
functional change.
R=csilvers
DELTA=16 (0 added, 0 deleted, 16 changed)
Revision created by MOE tool push_codebase.
MOE_MIGRATION=3300
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=3221
* ctemplate: version 1.0rc2 release
* BUGFIX: removed #includes of non-installed headers from installed ones
* BUGFIX: Make compile-test test against an install
R=jad
DELTA=30 (26 added, 0 deleted, 4 changed)
Revision created by MOE tool push_codebase.
MOE_MIGRATION=2822
