Lines Matching full:external

2 Building External Modules
10 	=== 2 How to Build External Modules
15 	=== 3. Creating a Kbuild File for an External Module
29 	   --- 6.2 Symbols and External Modules
30 	   --- 6.3 Symbols From Another External Module
47 in building out-of-tree (or "external") modules. The author of an
48 external module should supply a makefile that hides most of the
54 2. How to Build External Modules
57 To build external modules, you must have a prebuilt kernel available
66 building external modules.
75 	The command to build an external module is::
79 	The kbuild system knows that an external module is being built
104 		Informs kbuild that an external module is being built.
106 		directory where the external module (kbuild file) is
112 	When building an external module, only a subset of the "make"
125 		The default target for external modules. It has the
130 		Install the external module(s). The default location is
138 		List the available targets for external modules.
145 	external modules.
155 3. Creating a Kbuild File for an External Module
188 	An external module always includes a wrapper makefile that
249 	each file; however, some external modules use makefiles
287 	Some external modules need to include an object file as a blob.
351 	External modules tend to place header files in a separate
418 And external modules are installed in:
440 	External modules are by default installed to a directory under
489 6.2 Symbols and External Modules
492 	When building an external module, the build system needs access
493 	to the symbols from the kernel to check if all external symbols
497 	written containing all exported symbols from that external module.
499 6.3 Symbols From Another External Module
502 	Sometimes, an external module uses exported symbols from
503 	another external module. Kbuild needs to have full knowledge of
557 	External modules have traditionally used "grep" to check for
559 	broken. As introduced before, external modules should use