i can see that, after i run "make modules_prepare", i have a new
directory in the kernel source tree "include/config" full of empty
header files. what is the function of this directory? is it just
keeping track of which header files have been processed for exporting
to userspace or what?
i also notice that, if i start with a fresh tree and run "make
derconfig", that directory is created but is empty, suggesting that
it's not really needed for a *config target, but running "make
modules_prepare" *does* fill it in. i'm guessing that, just for
convenience, the top-level Makefile creates that directory even
before it actually needs it:
config: scripts_basic outputmakefile FORCE
$(Q)mkdir -p include/linux include/config
$(Q)$(MAKE) $(build)=scripts/kconfig $@
%config: scripts_basic outputmakefile FORCE
$(Q)mkdir -p include/linux include/config
$(Q)$(MAKE) $(build)=scripts/kconfig $@
and is it just me, but could those two rules be collapsed into one
since they're pretty much identical?
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
"Kernel Newbie Corner" column @ linux.com: http://cli.gs/WG6WYX
========================================================================
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ
