From 62532ad485698b70924c54a222890ebcb714dc39 Mon Sep 17 00:00:00 2001 From: Luboš Luňák Date: Sun, 6 Jan 2013 18:09:04 +0100 Subject: do not set our clang timestamp to the timestamp of the clang binary If the clang binary comes from a package which had been built before any of our clang related sources were changed the last time, the timestamp would be older and so there would be no rebuild. So do the stamp handling the usual way, clang upgrades will work fine, downgrades will not, but that's the same problem like with downgrading a library and its headers. To somewhat mitigate the problem (Clang plugin doesn't get cleaned by 'make clean'), include the full Clang version (which includes SVN revision) in config_clang.h and make all Clang plugin code include that, so at least configure re-run will trigger a rebuild if necessary. Change-Id: I993197f79e92e36105092c92c33b2e1db343e975 --- configure.ac | 1 + 1 file changed, 1 insertion(+) (limited to 'configure.ac') diff --git a/configure.ac b/configure.ac index bd5b0749240e..29cc3929b1ac 100644 --- a/configure.ac +++ b/configure.ac @@ -2906,6 +2906,7 @@ if test "$GCC" = "yes"; then CLANG_FULL_VERSION=`echo __clang_version__ | $CC -E -P -` CLANGVER=`echo $clang_version | $AWK -F. '{ print \$1*10000+\$2*100+\$3 }'` AC_MSG_RESULT([Clang $CLANG_FULL_VERSION, $CLANGVER]) + AC_DEFINE_UNQUOTED(CLANG_FULL_VERSION,$CLANG_FULL_VERSION) fi fi AC_SUBST(COM_GCC_IS_CLANG) -- cgit