From c5b1441ede3c58f1fe92372cbb48864f9d4df6ec Mon Sep 17 00:00:00 2001 From: Tor Lillqvist Date: Thu, 31 Jan 2013 20:44:25 +0200 Subject: 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 --- cross_tail_build/Makefile | 2 ++ 1 file changed, 2 insertions(+) (limited to 'cross_tail_build') diff --git a/cross_tail_build/Makefile b/cross_tail_build/Makefile index 89d362745b41..e632a08bf563 100644 --- a/cross_tail_build/Makefile +++ b/cross_tail_build/Makefile @@ -30,6 +30,8 @@ ifeq ($(strip $(SOLARENV)),) include $(dir $(realpath $(firstword $(MAKEFILE_LIST))))/../config_build.mk endif +export gb_Side=build + include $(SOLARENV)/gbuild/gbuild.mk $(eval $(call gb_Module_make_global_targets,$(SRCDIR)/Module_cross_tail_build.mk)) -- cgit