Lines Matching full:files
11 === 3 The kbuild files
51 --- 7.10 Generic header files
80 (the resident kernel image) and modules (any module files).
104 any kernel Makefiles (or any other source files).
123 3 The kbuild files
129 The preferred name for the kbuild files are 'Makefile' but 'Kbuild' can
140 These lines define the files to be built, any special compilation
166 The kbuild Makefile specifies object files for vmlinux
170 Kbuild compiles all the $(obj-y) files. It then calls
171 "$(AR) rcSTP" to merge these files into one built-in.a file.
175 The order of files in $(obj-y) is significant. Duplicates in
189 # Each configuration option enables a list of files.
196 $(obj-m) specifies object files which are built as loadable
200 files. In the case of one source file, the kbuild makefile
210 If a kernel module is built from several source files, you specify
212 kbuild needs to know which object files you want to build your
224 "$(LD) -r" on the list of these files to generate isdn.o.
268 Note that the same kbuild makefile may list files to be built-in
289 directory. Files in subdirectories should be taken care of by
399 $(AFLAGS_$@) is a similar feature for source files in assembly
418 1) All prerequisite files (both `*.c` and `*.h`)
419 2) `CONFIG_` options used in all prerequisite files
422 Thus, if you change an option to $(CC) all affected files will
430 header files generated during the build process.
437 path to prerequisite files and target files.
444 referring to files located in the src tree.
449 referring to generated files.
460 The target file depends on two prerequisite files. References
463 generated files).
491 assembler (`*.S`) files -- supports the given option. An optional
676 files. In the above example, checklist.c is compiled to checklist.o
679 Finally, the two .o files are linked to the executable, lxdialog.
698 If qconf is composed of a mixture of .c and .cc files, then an
819 files. In the above example, bpf-fancy.c is compiled to bpf-fancy.o
822 Finally, the two .o files are linked to the executable, bpf-fancy.
888 "make clean" deletes most generated files in the obj tree where the kernel
889 is compiled. This includes generated files such as host programs.
892 during "make clean". Files matching the patterns "*.[oas]", "*.ko", plus
893 some additional files generated by kbuild are deleted all over the kernel
896 Additional files or directories can be specified in kbuild makefiles by use of
897 $(clean-files).
902 clean-files := crc32table.h
905 Kbuild will assume files to be in the same relative directory as the
908 To exclude certain files or directories from make clean, use the
909 $(no-clean-files) variable.
963 5) All object files are then linked and the resulting file vmlinux is
1111 All object files for vmlinux. They are linked to vmlinux in the same
1116 All .a "lib" files for vmlinux. KBUILD_VMLINUX_OBJS and
1117 KBUILD_VMLINUX_LIBS together specify all the object files used to
1123 The archheaders: rule is used to generate header files that
1135 This is usually used for header files containing assembler constants.
1145 generating offset header files.
1187 it, wrap it in bootstrapping code, and copy the resulting files
1251 2) kbuild knows what files to delete during "make clean"
1258 In this example, extra-y is used to list object files that
1275 When the rule is evaluated, it is checked to see if any files
1326 frees us from listing the setup.o and bootsect.o files.
1401 kbuild knows .lds files and includes a rule `*lds.S` -> `*lds`.
1424 The kbuild infrastructure for `*lds` files is used in several
1425 architecture-specific files.
1427 7.10 Generic header files
1430 The directory include/asm-generic contains the header files
1469 arch/<arch>/include/asm/ to list asm files coming from asm-generic.
1512 If an architecture generates other header files alongside generic-y
1559 determine which files to compile.
1622 - Describe how kbuild supports shipped files with _shipped.
1623 - Generating offset header files.