I frequently (but not frequently enough) compile kernels on one machine
that are to be used on another machine. If It needs modules, I will need a
way to collect all modules that need to be transfered into a directory.
Usurally I'll want INSTALL_MOD_PATH=somedir make modules_install, but I
keep forgetting the name of the variable. I suppose I'm not the only one.
Therefore I suggest a modules_collect target, which will collect all
modules into a single directory ready for being tared and transfered:
--- a/Makefile 2005-11-15 01:41:32.000000000 +0100
+++ b/Makefile 2005-11-23 19:22:33.000000000 +0100
@@ -1065,6 +1065,7 @@ help:
@echo '* vmlinux - Build the bare kernel'
@echo '* modules - Build all modules'
@echo ' modules_install - Install all modules'
+ @echo ' modules_collect - Install all modules into ./modules.d'
@echo ' dir/ - Build all files in dir and below'
@echo ' dir/file.[ois] - Build specified target only'
@echo ' dir/file.ko - Build module including final link'
@@ -1316,4 +1317,10 @@ clean := -f $(if $(KBUILD_SRC),$(srctree
endif # skip-makefile
+.PHONY: modules_collect
+modules_collect:
+ rm -rf modules.d
+ mkdir modules.d
+ INSTALL_MOD_PATH=modules.d make modules_install
+
FORCE:
--
Top 100 things you don't want the sysadmin to say:
98. What the hell!?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
