KumiSystems/openwrtv4
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

rules.mk: drop include_mk build rule

Browse source 
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 <ardeleanalex@gmail.com>
This commit is contained in:
Alexandru Ardelean 2018-01-24 12:56:39 +02:00 committed by Matthias Schiffer
parent 2c50af0cea
commit cfdfa6d04e
No known key found for this signature in database
GPG key ID: 16EF3F64CB201D9C
1 changed files with 0 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
rules.mk
View file

@ -355,10 +355,6 @@ define shexport
export $(call shvar,$(1))=$$(call $(1)) export $(call shvar,$(1))=$$(call $(1))
endef endef
define include_mk
$(eval -include $(if $(DUMP),,$(STAGING_DIR)/mk/$(strip $(1))))
endef
# Execute commands under flock # Execute commands under flock
# $(1) => The shell expression. # $(1) => The shell expression.
# $(2) => The lock name. If not given, the global lock will be used. # $(2) => The lock name. If not given, the global lock will be used.