mkimage-profiles/image.in/vars.mk

# dump interesting variables' effective values;
# based on http://stackoverflow.com/questions/7117978

SPAM := $(.VARIABLES) DISTCFG_MK
-include distcfg.mk
HAM := $(.VARIABLES)

.PHONY: dump-vars

dump-vars:
	$(foreach v, \
	  $(filter-out $(SPAM) SPAM,$(sort $(HAM))), \
	    $(info $(v) = $($(v))))
	@:
image.in/vars.mk: dump distcfg variables nicely distcfg.mk is nice for tracing the variable values' build-up, but it's more useful to have a look at the final result sometimes. So here it is, logged for each build and callable by hand. 2011-09-02 00:01:52 +04:00			`# dump interesting variables' effective values;`
			`# based on http://stackoverflow.com/questions/7117978`

ensure that distcfg.mk gets included once at most This was done while debugging GLOBAL_CLEANUP_PACKAGES getting doubled... as it got no hard initial value but rather was always added to, it appeared that at least stage2/Makefile would obtain a once-initialized value from upstream and double it while including distcfg.mk itself. It's way less hassle to just proxy the value once. 2011-09-14 00:45:57 +04:00			`SPAM := $(.VARIABLES) DISTCFG_MK`
image.in/vars.mk: dump distcfg variables nicely distcfg.mk is nice for tracing the variable values' build-up, but it's more useful to have a look at the final result sometimes. So here it is, logged for each build and callable by hand. 2011-09-02 00:01:52 +04:00			`-include distcfg.mk`
			`HAM := $(.VARIABLES)`

			`.PHONY: dump-vars`

			`dump-vars:`
			`$(foreach v, \`
			`$(filter-out $(SPAM) SPAM,$(sort $(HAM))), \`
			`$(info $(v) = $($(v))))`
			`@:`