office-gobmx/config_host/config_clang.h.in
Tor Lillqvist c5b1441ede Use separate config_*.h files for BUILD and HOST when cross-compiling
We have only been lucky so far that there hasn't been any compilation errors
caused by using the HOST platform config_*.h files also for the BUILD
platform. But as more and more information found out during configury is
stored in config_*.h files, sooner or later it will be a problem.

Move config/* to config_host/*. When not cross-compiling, the config_*.h files
in config_host expanded from config_*.h.in are all there is. When
cross-compiling, the generated config_*.h files for the BUILD platform are
put into a config_build folder.

Then use config_build when building the cross_toolset and config_host
otherwise.

Change-Id: I3c28cc83866bffd696b45d00dfb68e00bc2ae538
2013-01-31 21:43:59 +02:00

19 lines
351 B
C

/*
Settings related to Clang compiler plugins.
*/
#ifndef CONFIG_CLANG_H
#define CONFIG_CLANG_H
#undef BUILDDIR
#undef OUTDIR
#undef SRCDIR
#undef WORKDIR
/* This is actually unused, but it should change whenever Clang changes,
thus causing update of this .h file and triggerring rebuild of our Clang plugin. */
#undef CLANG_FULL_VERSION
#endif