i'm just following the logic for the simple clean targets, and i'm
confused as to how "make clean" and "make dirclean" work. in a
fully-cleaned openwrt tree, running either of those dumps one into
"make menuconfig", which would seem to be a pointless exercise if the
tree is already clean.
in include/toplevel.mk, i can see the following:
...
.config: ./scripts/config/conf prepare-tmpinfo
@+if [ \! -f .config ]; then \
[ -e $(HOME)/.openwrt/defconfig ] && cp
$(HOME)/.openwrt/defconfig .config; \
$(NO_TRACE_MAKE) menuconfig $(PREP_MK); \
fi
...
clean dirclean: .config
@$(MAKE) $@
...
so i can see that either of those targets requires a rebuild of
.config if it isn't already there, which strikes me as weird.
i'm also puzzled by that second rule and its command:
@$(MAKE) $@
i'm sure i'm just missing something, but doesn't that just reinvoke
its own target? how *does* that work? thanks for any enlightenment.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
Home page: http://crashcourse.ca
Fedora Cookbook: http://crashcourse.ca/wiki/index.php/Fedora_Cookbook
========================================================================
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
