Lines Matching full:make
50 complexity, so one only has to type "make" to build the module. This is
64 An alternative is to use the "make" target "modules_prepare." This will
65 make sure the kernel contains the information required. The target
71 executed to make module versioning work.
78 $ make -C <path_to_kernel_src> M=$PWD
85 $ make -C /lib/modules/`uname -r`/build M=$PWD
90 $ make -C /lib/modules/`uname -r`/build M=$PWD modules_install
97 make -C $KDIR M=$PWD
101 "make" will actually change to the specified directory
113 When building an external module, only a subset of the "make"
116 make -C $KDIR M=$PWD [target]
122 precondition that a successful "make" has been executed for the
154 make -C $KDIR M=$PWD bar.lst
155 make -C $KDIR M=$PWD baz.o
156 make -C $KDIR M=$PWD foo.ko
157 make -C $KDIR M=$PWD ./
194 supports building the module using "make" with no arguments.
213 $(MAKE) -C $(KDIR) M=$$PWD
223 assignments, whereas "make" will see everything except these
225 the first pass is by the "make" instance run on the command
227 initiated by the parameterized "make" in the default target.
247 $(MAKE) -C $(KDIR) M=$$PWD
276 $(MAKE) -C $(KDIR) M=$$PWD
286 makefiles, to be used when the "make" and kbuild parts are
445 $ make INSTALL_MOD_PATH=/frodo modules_install
450 calling "make." This has effect when installing both in-tree
462 $ make INSTALL_MOD_DIR=gandalf -C $KDIR \
543 $ make -C $KDIR M=$PWD
548 Use "make" variable KBUILD_EXTRA_SYMBOLS