From cfdfa6d04e16b001e45054dafbf5df3cfc98ef03 Mon Sep 17 00:00:00 2001 From: Alexandru Ardelean Date: Wed, 24 Jan 2018 12:56:39 +0200 Subject: [PATCH] rules.mk: drop `include_mk` build rule The only users of this were the python packages from the `packages` feed. The 2 python interpreters would export some mk files (e.g. python-package.mk) and then other python packages would include it via this rule. But there's a few things wrong with this approach, most of them drawing from the fact that python host needs to be built first, to export these mk files. By now all uses of include_mk have been corrected in the feeds and this can be removed. Signed-off-by: Alexandru Ardelean --- rules.mk | 4 ---- 1 file changed, 4 deletions(-) diff --git a/rules.mk b/rules.mk index 9d8b9f8f90..84e0aaadc6 100644 --- a/rules.mk +++ b/rules.mk @@ -355,10 +355,6 @@ define shexport export $(call shvar,$(1))=$$(call $(1)) endef -define include_mk -$(eval -include $(if $(DUMP),,$(STAGING_DIR)/mk/$(strip $(1)))) -endef - # Execute commands under flock # $(1) => The shell expression. # $(2) => The lock name. If not given, the global lock will be used.