Documentation/kbuild/modules.rst

50 easily accomplished, and a complete example will be presented in
60 using a distribution kernel, there will be a package for the kernel you
63 An alternative is to use the "make" target "modules_prepare." This will
68 NOTE: "modules_prepare" will not build Module.symvers even if
100 		"make" will actually change to the specified directory
101 		when executing and will change back when finished.
117 	The default will build the module(s) located in the current
119 	output files will also be generated in this directory. No
160 build file is required. Contained in this file will be the name of
166 The kbuild system will build <module_name>.o from <module_name>.c,
167 and, after linking, will result in the kernel module <module_name>.ko.
217 	of the makefile. In the example, kbuild will only see the two
218 	assignments, whereas "make" will see everything except these
227 	In newer versions of the kernel, kbuild will first look for a
228 	file named "Kbuild," and only if that is not found, will it
301 	files and the binary file, kbuild will pick up different rules
345 	kbuild will add options to "gcc" so the relevant directories
467 	During a kernel build, a file named Module.symvers will be
496 	tree. During the MODPOST step, a new Module.symvers file will be
529 		will then do the expected and compile both modules with
536 		These files will be loaded by modpost during the