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
30 --- 6.2 Symbols and External Modules
31 --- 6.3 Symbols From Another External Module
48 in building out-of-tree (or "external") modules. The author of an
49 external module should supply a makefile that hides most of the
55 2. How to Build External Modules
58 To build external modules, you must have a prebuilt kernel available
67 building external modules.
76 The command to build an external module is::
80 The kbuild system knows that an external module is being built
105 Informs kbuild that an external module is being built.
107 directory where the external module (kbuild file) is
113 When building an external module, only a subset of the "make"
126 The default target for external modules. It has the
131 Install the external module(s). The default location is
143 List the available targets for external modules.
150 external modules.
160 3. Creating a Kbuild File for an External Module
193 An external module always includes a wrapper makefile that
254 each file; however, some external modules use makefiles
292 Some external modules need to include an object file as a blob.
356 External modules tend to place header files in a separate
417 External modules may export headers to userspace in a similar
434 And external modules are installed in:
456 External modules are by default installed to a directory under
505 6.2 Symbols and External Modules
508 When building an external module, the build system needs access
509 to the symbols from the kernel to check if all external symbols
513 written containing all exported symbols from that external module.
515 6.3 Symbols From Another External Module
518 Sometimes, an external module uses exported symbols from
519 another external module. Kbuild needs to have full knowledge of
573 External modules have traditionally used "grep" to check for
575 broken. As introduced before, external modules should use