Documentation/kbuild/modules.rst

20 complexity, so one only has to type "make" to build the module. This is
34 An alternative is to use the "make" target "modules_prepare." This will
35 make sure the kernel contains the information required. The target
41 executed to make module versioning work.
48 		$ make -C <path_to_kernel_dir> M=$PWD
55 		$ make -C /lib/modules/`uname -r`/build M=$PWD
60 		$ make -C /lib/modules/`uname -r`/build M=$PWD modules_install
69 	make -C $KDIR M=$PWD
74 		"make" will actually change to the specified directory
86 	When building an external module, only a subset of the "make"
89 	make -C $KDIR M=$PWD [target]
95 	precondition that a successful "make" has been executed for the
124 		make -C $KDIR M=$PWD bar.lst
125 		make -C $KDIR M=$PWD baz.o
126 		make -C $KDIR M=$PWD foo.ko
127 		make -C $KDIR M=$PWD ./
163 	supports building the module using "make" with no arguments.
182 			$(MAKE) -C $(KDIR) M=$$PWD
188 	assignments, whereas "make" will see everything except these
190 	the first pass is by the "make" instance run on the command
192 	initiated by the parameterized "make" in the default target.
211 			$(MAKE) -C $(KDIR) M=$$PWD
339 		$ make INSTALL_MOD_PATH=/frodo modules_install
344 	calling "make." This has effect when installing both in-tree
356 		$ make INSTALL_MOD_DIR=gandalf -C $KDIR \
437 			$ make -C $KDIR M=$PWD
442 	Use "make" variable KBUILD_EXTRA_SYMBOLS