Lines Matching full:files
22 (the resident kernel image) and modules (any module files).
46 any kernel Makefiles (or any other source files).
65 The kbuild files
72 The preferred name for the kbuild files are ``Makefile`` but ``Kbuild`` can
83 These lines define the files to be built, any special compilation
109 The kbuild Makefile specifies object files for vmlinux
113 Kbuild compiles all the $(obj-y) files. It then calls
114 ``$(AR) rcSTP`` to merge these files into one built-in.a file.
118 The order of files in $(obj-y) is significant. Duplicates in
132 # Each configuration option enables a list of files.
139 $(obj-m) specifies object files which are built as loadable
143 files. In the case of one source file, the kbuild makefile
153 If a kernel module is built from several source files, you specify
155 kbuild needs to know which object files you want to build your
167 ``$(LD) -r`` on the list of these files to generate isdn.o.
205 Note that the same kbuild makefile may list files to be built-in
226 directory. Files in subdirectories should be taken care of by
387 $(AFLAGS_$@) is a similar feature for source files in assembly
405 1) All prerequisite files (both ``*.c`` and ``*.h``)
406 2) ``CONFIG_`` options used in all prerequisite files
409 Thus, if you change an option to $(CC) all affected files will
417 header files generated during the build process.
424 path to prerequisite files and target files.
430 referring to files located in the src tree.
434 referring to generated files. Use $(obj) for pattern rules that need to work
435 for both generated files and real sources (VPATH will help to find the
447 The target file depends on two prerequisite files. References
450 generated files).
507 and its prerequisite files. GNU Make updates the target when any of the
560 assembler (``*.S``) files -- supports the given option. An optional
757 files. In the above example, checklist.c is compiled to checklist.o
760 Finally, the two .o files are linked to the executable, lxdialog.
779 If qconf is composed of a mixture of .c and .cc files, then an
804 consist of several source files (see ``samples/rust/hostprogs``).
919 files. In the above example, bpf-fancy.c is compiled to bpf-fancy.o
922 Finally, the two .o files are linked to the executable, bpf-fancy.
995 ``make clean`` deletes most generated files in the obj tree where the kernel
996 is compiled. This includes generated files such as host programs.
999 during ``make clean``. Files matching the patterns ``*.[oas]``, ``*.ko``, plus
1000 some additional files generated by kbuild are deleted all over the kernel
1003 Additional files or directories can be specified in kbuild makefiles by use of
1004 $(clean-files).
1009 clean-files := crc32table.h
1012 Kbuild will assume files to be in the same relative directory as the
1015 To exclude certain files or directories from make clean, use the
1016 $(no-clean-files) variable.
1065 5) All object files are then linked and the resulting file vmlinux is
1237 All object files for vmlinux. They are linked to vmlinux in the same
1244 All .a ``lib`` files for vmlinux. KBUILD_VMLINUX_OBJS and
1245 KBUILD_VMLINUX_LIBS together specify all the object files used to
1251 The archheaders: rule is used to generate header files that
1263 This is usually used for header files containing assembler constants.
1274 generating offset header files.
1312 it, wrap it in bootstrapping code, and copy the resulting files
1395 frees us from listing the setup.o and bootsect.o files.
1443 kbuild knows .lds files and includes a rule ``*lds.S`` -> ``*lds``.
1464 The kbuild infrastructure for ``*lds`` files is used in several
1465 architecture-specific files.
1467 Generic header files
1470 The directory include/asm-generic contains the header files
1512 arch/<arch>/include/asm/ to list asm files coming from asm-generic.
1556 If an architecture generates other header files alongside generic-y
1603 determine which files to compile.
1682 - Generating offset header files.