]>
Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | Linux Kernel Makefiles |
2 | ||
3 | This document describes the Linux kernel Makefiles. | |
4 | ||
5 | === Table of Contents | |
6 | ||
7 | === 1 Overview | |
8 | === 2 Who does what | |
9 | === 3 The kbuild files | |
10 | --- 3.1 Goal definitions | |
11 | --- 3.2 Built-in object goals - obj-y | |
12 | --- 3.3 Loadable module goals - obj-m | |
13 | --- 3.4 Objects which export symbols | |
14 | --- 3.5 Library file goals - lib-y | |
15 | --- 3.6 Descending down in directories | |
16 | --- 3.7 Compilation flags | |
17 | --- 3.8 Command line dependency | |
18 | --- 3.9 Dependency tracking | |
19 | --- 3.10 Special Rules | |
20a468b5 | 20 | --- 3.11 $(CC) support functions |
691ef3e7 | 21 | --- 3.12 $(LD) support functions |
1da177e4 LT |
22 | |
23 | === 4 Host Program support | |
24 | --- 4.1 Simple Host Program | |
25 | --- 4.2 Composite Host Programs | |
62e22107 MY |
26 | --- 4.3 Using C++ for host programs |
27 | --- 4.4 Controlling compiler options for host programs | |
28 | --- 4.5 When host programs are actually built | |
29 | --- 4.6 Using hostprogs-$(CONFIG_FOO) | |
1da177e4 LT |
30 | |
31 | === 5 Kbuild clean infrastructure | |
32 | ||
33 | === 6 Architecture Makefiles | |
34 | --- 6.1 Set variables to tweak the build to the architecture | |
052ad274 PA |
35 | --- 6.2 Add prerequisites to archheaders: |
36 | --- 6.3 Add prerequisites to archprepare: | |
37 | --- 6.4 List directories to visit when descending | |
38 | --- 6.5 Architecture-specific boot images | |
39 | --- 6.6 Building non-kbuild targets | |
40 | --- 6.7 Commands useful for building a boot image | |
41 | --- 6.8 Custom kbuild commands | |
42 | --- 6.9 Preprocessing linker scripts | |
43 | --- 6.10 Generic header files | |
fbe6e37d | 44 | --- 6.11 Post-link pass |
1da177e4 | 45 | |
c7bb349e | 46 | === 7 Kbuild syntax for exported headers |
fcc8487d | 47 | --- 7.1 no-export-headers |
ae3f4151 MY |
48 | --- 7.2 generic-y |
49 | --- 7.3 generated-y | |
50 | --- 7.4 mandatory-y | |
c7bb349e SR |
51 | |
52 | === 8 Kbuild Variables | |
53 | === 9 Makefile language | |
54 | === 10 Credits | |
55 | === 11 TODO | |
1da177e4 LT |
56 | |
57 | === 1 Overview | |
58 | ||
59 | The Makefiles have five parts: | |
60 | ||
61 | Makefile the top Makefile. | |
62 | .config the kernel configuration file. | |
63 | arch/$(ARCH)/Makefile the arch Makefile. | |
64 | scripts/Makefile.* common rules etc. for all kbuild Makefiles. | |
65 | kbuild Makefiles there are about 500 of these. | |
66 | ||
67 | The top Makefile reads the .config file, which comes from the kernel | |
68 | configuration process. | |
69 | ||
70 | The top Makefile is responsible for building two major products: vmlinux | |
71 | (the resident kernel image) and modules (any module files). | |
72 | It builds these goals by recursively descending into the subdirectories of | |
73 | the kernel source tree. | |
74 | The list of subdirectories which are visited depends upon the kernel | |
75 | configuration. The top Makefile textually includes an arch Makefile | |
76 | with the name arch/$(ARCH)/Makefile. The arch Makefile supplies | |
77 | architecture-specific information to the top Makefile. | |
78 | ||
79 | Each subdirectory has a kbuild Makefile which carries out the commands | |
80 | passed down from above. The kbuild Makefile uses information from the | |
39e6e9cf | 81 | .config file to construct various file lists used by kbuild to build |
1da177e4 LT |
82 | any built-in or modular targets. |
83 | ||
84 | scripts/Makefile.* contains all the definitions/rules etc. that | |
85 | are used to build the kernel based on the kbuild makefiles. | |
86 | ||
87 | ||
88 | === 2 Who does what | |
89 | ||
90 | People have four different relationships with the kernel Makefiles. | |
91 | ||
92 | *Users* are people who build kernels. These people type commands such as | |
93 | "make menuconfig" or "make". They usually do not read or edit | |
94 | any kernel Makefiles (or any other source files). | |
95 | ||
96 | *Normal developers* are people who work on features such as device | |
97 | drivers, file systems, and network protocols. These people need to | |
a07f6033 | 98 | maintain the kbuild Makefiles for the subsystem they are |
1da177e4 LT |
99 | working on. In order to do this effectively, they need some overall |
100 | knowledge about the kernel Makefiles, plus detailed knowledge about the | |
101 | public interface for kbuild. | |
102 | ||
103 | *Arch developers* are people who work on an entire architecture, such | |
104 | as sparc or ia64. Arch developers need to know about the arch Makefile | |
105 | as well as kbuild Makefiles. | |
106 | ||
107 | *Kbuild developers* are people who work on the kernel build system itself. | |
108 | These people need to know about all aspects of the kernel Makefiles. | |
109 | ||
110 | This document is aimed towards normal developers and arch developers. | |
111 | ||
112 | ||
113 | === 3 The kbuild files | |
114 | ||
115 | Most Makefiles within the kernel are kbuild Makefiles that use the | |
a07f6033 | 116 | kbuild infrastructure. This chapter introduces the syntax used in the |
1da177e4 | 117 | kbuild makefiles. |
172c3ae3 | 118 | The preferred name for the kbuild files are 'Makefile' but 'Kbuild' can |
a07f6033 | 119 | be used and if both a 'Makefile' and a 'Kbuild' file exists, then the 'Kbuild' |
172c3ae3 | 120 | file will be used. |
1da177e4 LT |
121 | |
122 | Section 3.1 "Goal definitions" is a quick intro, further chapters provide | |
123 | more details, with real examples. | |
124 | ||
125 | --- 3.1 Goal definitions | |
126 | ||
127 | Goal definitions are the main part (heart) of the kbuild Makefile. | |
128 | These lines define the files to be built, any special compilation | |
129 | options, and any subdirectories to be entered recursively. | |
130 | ||
131 | The most simple kbuild makefile contains one line: | |
132 | ||
133 | Example: | |
134 | obj-y += foo.o | |
135 | ||
5c811e59 | 136 | This tells kbuild that there is one object in that directory, named |
1da177e4 LT |
137 | foo.o. foo.o will be built from foo.c or foo.S. |
138 | ||
139 | If foo.o shall be built as a module, the variable obj-m is used. | |
140 | Therefore the following pattern is often used: | |
141 | ||
142 | Example: | |
143 | obj-$(CONFIG_FOO) += foo.o | |
144 | ||
145 | $(CONFIG_FOO) evaluates to either y (for built-in) or m (for module). | |
146 | If CONFIG_FOO is neither y nor m, then the file will not be compiled | |
147 | nor linked. | |
148 | ||
149 | --- 3.2 Built-in object goals - obj-y | |
150 | ||
151 | The kbuild Makefile specifies object files for vmlinux | |
a07f6033 | 152 | in the $(obj-y) lists. These lists depend on the kernel |
1da177e4 LT |
153 | configuration. |
154 | ||
155 | Kbuild compiles all the $(obj-y) files. It then calls | |
156 | "$(LD) -r" to merge these files into one built-in.o file. | |
157 | built-in.o is later linked into vmlinux by the parent Makefile. | |
158 | ||
159 | The order of files in $(obj-y) is significant. Duplicates in | |
160 | the lists are allowed: the first instance will be linked into | |
161 | built-in.o and succeeding instances will be ignored. | |
162 | ||
163 | Link order is significant, because certain functions | |
164 | (module_init() / __initcall) will be called during boot in the | |
165 | order they appear. So keep in mind that changing the link | |
a07f6033 JE |
166 | order may e.g. change the order in which your SCSI |
167 | controllers are detected, and thus your disks are renumbered. | |
1da177e4 LT |
168 | |
169 | Example: | |
170 | #drivers/isdn/i4l/Makefile | |
171 | # Makefile for the kernel ISDN subsystem and device drivers. | |
172 | # Each configuration option enables a list of files. | |
2f5a2f81 | 173 | obj-$(CONFIG_ISDN_I4L) += isdn.o |
1da177e4 LT |
174 | obj-$(CONFIG_ISDN_PPP_BSDCOMP) += isdn_bsdcomp.o |
175 | ||
176 | --- 3.3 Loadable module goals - obj-m | |
177 | ||
39fed701 | 178 | $(obj-m) specifies object files which are built as loadable |
1da177e4 LT |
179 | kernel modules. |
180 | ||
181 | A module may be built from one source file or several source | |
182 | files. In the case of one source file, the kbuild makefile | |
183 | simply adds the file to $(obj-m). | |
184 | ||
185 | Example: | |
186 | #drivers/isdn/i4l/Makefile | |
187 | obj-$(CONFIG_ISDN_PPP_BSDCOMP) += isdn_bsdcomp.o | |
188 | ||
189 | Note: In this example $(CONFIG_ISDN_PPP_BSDCOMP) evaluates to 'm' | |
190 | ||
191 | If a kernel module is built from several source files, you specify | |
4f827280 MM |
192 | that you want to build a module in the same way as above; however, |
193 | kbuild needs to know which object files you want to build your | |
194 | module from, so you have to tell it by setting a $(<module_name>-y) | |
195 | variable. | |
1da177e4 LT |
196 | |
197 | Example: | |
198 | #drivers/isdn/i4l/Makefile | |
4f827280 MM |
199 | obj-$(CONFIG_ISDN_I4L) += isdn.o |
200 | isdn-y := isdn_net_lib.o isdn_v110.o isdn_common.o | |
1da177e4 LT |
201 | |
202 | In this example, the module name will be isdn.o. Kbuild will | |
4f827280 | 203 | compile the objects listed in $(isdn-y) and then run |
1da177e4 LT |
204 | "$(LD) -r" on the list of these files to generate isdn.o. |
205 | ||
4f827280 MM |
206 | Due to kbuild recognizing $(<module_name>-y) for composite objects, |
207 | you can use the value of a CONFIG_ symbol to optionally include an | |
208 | object file as part of a composite object. | |
1da177e4 LT |
209 | |
210 | Example: | |
211 | #fs/ext2/Makefile | |
4f827280 MM |
212 | obj-$(CONFIG_EXT2_FS) += ext2.o |
213 | ext2-y := balloc.o dir.o file.o ialloc.o inode.o ioctl.o \ | |
214 | namei.o super.o symlink.o | |
215 | ext2-$(CONFIG_EXT2_FS_XATTR) += xattr.o xattr_user.o \ | |
216 | xattr_trusted.o | |
217 | ||
218 | In this example, xattr.o, xattr_user.o and xattr_trusted.o are only | |
219 | part of the composite object ext2.o if $(CONFIG_EXT2_FS_XATTR) | |
220 | evaluates to 'y'. | |
1da177e4 LT |
221 | |
222 | Note: Of course, when you are building objects into the kernel, | |
223 | the syntax above will also work. So, if you have CONFIG_EXT2_FS=y, | |
224 | kbuild will build an ext2.o file for you out of the individual | |
225 | parts and then link this into built-in.o, as you would expect. | |
226 | ||
227 | --- 3.4 Objects which export symbols | |
228 | ||
229 | No special notation is required in the makefiles for | |
230 | modules exporting symbols. | |
231 | ||
232 | --- 3.5 Library file goals - lib-y | |
233 | ||
a07f6033 | 234 | Objects listed with obj-* are used for modules, or |
1da177e4 LT |
235 | combined in a built-in.o for that specific directory. |
236 | There is also the possibility to list objects that will | |
237 | be included in a library, lib.a. | |
238 | All objects listed with lib-y are combined in a single | |
239 | library for that directory. | |
5d3f083d ML |
240 | Objects that are listed in obj-y and additionally listed in |
241 | lib-y will not be included in the library, since they will | |
242 | be accessible anyway. | |
a07f6033 | 243 | For consistency, objects listed in lib-m will be included in lib.a. |
1da177e4 LT |
244 | |
245 | Note that the same kbuild makefile may list files to be built-in | |
246 | and to be part of a library. Therefore the same directory | |
247 | may contain both a built-in.o and a lib.a file. | |
248 | ||
249 | Example: | |
2f5a2f81 MM |
250 | #arch/x86/lib/Makefile |
251 | lib-y := delay.o | |
1da177e4 | 252 | |
2f5a2f81 MM |
253 | This will create a library lib.a based on delay.o. For kbuild to |
254 | actually recognize that there is a lib.a being built, the directory | |
255 | shall be listed in libs-y. | |
052ad274 | 256 | See also "6.4 List directories to visit when descending". |
39e6e9cf | 257 | |
a07f6033 | 258 | Use of lib-y is normally restricted to lib/ and arch/*/lib. |
1da177e4 LT |
259 | |
260 | --- 3.6 Descending down in directories | |
261 | ||
262 | A Makefile is only responsible for building objects in its own | |
263 | directory. Files in subdirectories should be taken care of by | |
264 | Makefiles in these subdirs. The build system will automatically | |
265 | invoke make recursively in subdirectories, provided you let it know of | |
266 | them. | |
267 | ||
a07f6033 | 268 | To do so, obj-y and obj-m are used. |
1da177e4 LT |
269 | ext2 lives in a separate directory, and the Makefile present in fs/ |
270 | tells kbuild to descend down using the following assignment. | |
271 | ||
272 | Example: | |
273 | #fs/Makefile | |
274 | obj-$(CONFIG_EXT2_FS) += ext2/ | |
275 | ||
276 | If CONFIG_EXT2_FS is set to either 'y' (built-in) or 'm' (modular) | |
277 | the corresponding obj- variable will be set, and kbuild will descend | |
278 | down in the ext2 directory. | |
279 | Kbuild only uses this information to decide that it needs to visit | |
280 | the directory, it is the Makefile in the subdirectory that | |
39fed701 | 281 | specifies what is modular and what is built-in. |
1da177e4 LT |
282 | |
283 | It is good practice to use a CONFIG_ variable when assigning directory | |
284 | names. This allows kbuild to totally skip the directory if the | |
285 | corresponding CONFIG_ option is neither 'y' nor 'm'. | |
286 | ||
287 | --- 3.7 Compilation flags | |
288 | ||
f77bf014 | 289 | ccflags-y, asflags-y and ldflags-y |
c95940f2 NK |
290 | These three flags apply only to the kbuild makefile in which they |
291 | are assigned. They are used for all the normal cc, as and ld | |
292 | invocations happening during a recursive build. | |
f77bf014 | 293 | Note: Flags with the same behaviour were previously named: |
c95940f2 NK |
294 | EXTRA_CFLAGS, EXTRA_AFLAGS and EXTRA_LDFLAGS. |
295 | They are still supported but their usage is deprecated. | |
1da177e4 | 296 | |
eb07e1b4 | 297 | ccflags-y specifies options for compiling with $(CC). |
1da177e4 LT |
298 | |
299 | Example: | |
3d91a353 SD |
300 | # drivers/acpi/acpica/Makefile |
301 | ccflags-y := -Os -D_LINUX -DBUILDING_ACPICA | |
302 | ccflags-$(CONFIG_ACPI_DEBUG) += -DACPI_DEBUG_OUTPUT | |
1da177e4 LT |
303 | |
304 | This variable is necessary because the top Makefile owns the | |
a0f97e06 | 305 | variable $(KBUILD_CFLAGS) and uses it for compilation flags for the |
1da177e4 LT |
306 | entire tree. |
307 | ||
eb07e1b4 | 308 | asflags-y specifies options for assembling with $(AS). |
1da177e4 LT |
309 | |
310 | Example: | |
eb07e1b4 MM |
311 | #arch/sparc/kernel/Makefile |
312 | asflags-y := -ansi | |
1da177e4 | 313 | |
eb07e1b4 | 314 | ldflags-y specifies options for linking with $(LD). |
1da177e4 LT |
315 | |
316 | Example: | |
eb07e1b4 MM |
317 | #arch/cris/boot/compressed/Makefile |
318 | ldflags-y += -T $(srctree)/$(src)/decompress_$(arch-y).lds | |
1da177e4 | 319 | |
720097d8 | 320 | subdir-ccflags-y, subdir-asflags-y |
eb07e1b4 | 321 | The two flags listed above are similar to ccflags-y and asflags-y. |
c95940f2 NK |
322 | The difference is that the subdir- variants have effect for the kbuild |
323 | file where they are present and all subdirectories. | |
324 | Options specified using subdir-* are added to the commandline before | |
325 | the options specified using the non-subdir variants. | |
720097d8 SR |
326 | |
327 | Example: | |
328 | subdir-ccflags-y := -Werror | |
329 | ||
1da177e4 LT |
330 | CFLAGS_$@, AFLAGS_$@ |
331 | ||
332 | CFLAGS_$@ and AFLAGS_$@ only apply to commands in current | |
333 | kbuild makefile. | |
334 | ||
335 | $(CFLAGS_$@) specifies per-file options for $(CC). The $@ | |
336 | part has a literal value which specifies the file that it is for. | |
337 | ||
338 | Example: | |
339 | # drivers/scsi/Makefile | |
340 | CFLAGS_aha152x.o = -DAHA152X_STAT -DAUTOCONF | |
341 | CFLAGS_gdth.o = # -DDEBUG_GDTH=2 -D__SERIAL__ -D__COM2__ \ | |
342 | -DGDTH_STATISTICS | |
1da177e4 | 343 | |
eb07e1b4 | 344 | These two lines specify compilation flags for aha152x.o and gdth.o. |
1da177e4 LT |
345 | |
346 | $(AFLAGS_$@) is a similar feature for source files in assembly | |
347 | languages. | |
348 | ||
349 | Example: | |
350 | # arch/arm/kernel/Makefile | |
eb07e1b4 MM |
351 | AFLAGS_head.o := -DTEXT_OFFSET=$(TEXT_OFFSET) |
352 | AFLAGS_crunch-bits.o := -Wa,-mcpu=ep9312 | |
353 | AFLAGS_iwmmxt.o := -Wa,-mcpu=iwmmxt | |
354 | ||
1da177e4 LT |
355 | |
356 | --- 3.9 Dependency tracking | |
357 | ||
358 | Kbuild tracks dependencies on the following: | |
359 | 1) All prerequisite files (both *.c and *.h) | |
360 | 2) CONFIG_ options used in all prerequisite files | |
361 | 3) Command-line used to compile target | |
362 | ||
363 | Thus, if you change an option to $(CC) all affected files will | |
364 | be re-compiled. | |
365 | ||
366 | --- 3.10 Special Rules | |
367 | ||
368 | Special rules are used when the kbuild infrastructure does | |
369 | not provide the required support. A typical example is | |
370 | header files generated during the build process. | |
5c811e59 | 371 | Another example are the architecture-specific Makefiles which |
a07f6033 | 372 | need special rules to prepare boot images etc. |
1da177e4 LT |
373 | |
374 | Special rules are written as normal Make rules. | |
375 | Kbuild is not executing in the directory where the Makefile is | |
376 | located, so all special rules shall provide a relative | |
377 | path to prerequisite files and target files. | |
378 | ||
379 | Two variables are used when defining special rules: | |
380 | ||
381 | $(src) | |
382 | $(src) is a relative path which points to the directory | |
383 | where the Makefile is located. Always use $(src) when | |
384 | referring to files located in the src tree. | |
385 | ||
386 | $(obj) | |
387 | $(obj) is a relative path which points to the directory | |
388 | where the target is saved. Always use $(obj) when | |
389 | referring to generated files. | |
390 | ||
391 | Example: | |
392 | #drivers/scsi/Makefile | |
393 | $(obj)/53c8xx_d.h: $(src)/53c7,8xx.scr $(src)/script_asm.pl | |
394 | $(CPP) -DCHIP=810 - < $< | ... $(src)/script_asm.pl | |
395 | ||
396 | This is a special rule, following the normal syntax | |
397 | required by make. | |
398 | The target file depends on two prerequisite files. References | |
399 | to the target file are prefixed with $(obj), references | |
400 | to prerequisites are referenced with $(src) (because they are not | |
401 | generated files). | |
402 | ||
5410ecc0 MF |
403 | $(kecho) |
404 | echoing information to user in a rule is often a good practice | |
405 | but when execution "make -s" one does not expect to see any output | |
406 | except for warnings/errors. | |
39fed701 | 407 | To support this kbuild defines $(kecho) which will echo out the |
5410ecc0 MF |
408 | text following $(kecho) to stdout except if "make -s" is used. |
409 | ||
410 | Example: | |
411 | #arch/blackfin/boot/Makefile | |
412 | $(obj)/vmImage: $(obj)/vmlinux.gz | |
413 | $(call if_changed,uimage) | |
414 | @$(kecho) 'Kernel: $@ is ready' | |
415 | ||
416 | ||
20a468b5 SR |
417 | --- 3.11 $(CC) support functions |
418 | ||
a07f6033 | 419 | The kernel may be built with several different versions of |
20a468b5 | 420 | $(CC), each supporting a unique set of features and options. |
39fed701 | 421 | kbuild provides basic support to check for valid options for $(CC). |
e95be9a5 | 422 | $(CC) is usually the gcc compiler, but other alternatives are |
20a468b5 SR |
423 | available. |
424 | ||
425 | as-option | |
a07f6033 JE |
426 | as-option is used to check if $(CC) -- when used to compile |
427 | assembler (*.S) files -- supports the given option. An optional | |
428 | second option may be specified if the first option is not supported. | |
20a468b5 SR |
429 | |
430 | Example: | |
431 | #arch/sh/Makefile | |
432 | cflags-y += $(call as-option,-Wa$(comma)-isa=$(isa-y),) | |
433 | ||
a07f6033 | 434 | In the above example, cflags-y will be assigned the option |
20a468b5 SR |
435 | -Wa$(comma)-isa=$(isa-y) if it is supported by $(CC). |
436 | The second argument is optional, and if supplied will be used | |
437 | if first argument is not supported. | |
438 | ||
f86fd306 SR |
439 | cc-ldoption |
440 | cc-ldoption is used to check if $(CC) when used to link object files | |
0b0bf7a3 RM |
441 | supports the given option. An optional second option may be |
442 | specified if first option are not supported. | |
443 | ||
444 | Example: | |
25eb650a | 445 | #arch/x86/kernel/Makefile |
f86fd306 | 446 | vsyscall-flags += $(call cc-ldoption, -Wl$(comma)--hash-style=sysv) |
0b0bf7a3 | 447 | |
5c811e59 | 448 | In the above example, vsyscall-flags will be assigned the option |
0b0bf7a3 RM |
449 | -Wl$(comma)--hash-style=sysv if it is supported by $(CC). |
450 | The second argument is optional, and if supplied will be used | |
451 | if first argument is not supported. | |
452 | ||
e2414910 AK |
453 | as-instr |
454 | as-instr checks if the assembler reports a specific instruction | |
455 | and then outputs either option1 or option2 | |
456 | C escapes are supported in the test instruction | |
222d394d | 457 | Note: as-instr-option uses KBUILD_AFLAGS for $(AS) options |
e2414910 | 458 | |
20a468b5 | 459 | cc-option |
39fed701 GU |
460 | cc-option is used to check if $(CC) supports a given option, and if |
461 | not supported to use an optional second option. | |
20a468b5 SR |
462 | |
463 | Example: | |
25eb650a | 464 | #arch/x86/Makefile |
20a468b5 SR |
465 | cflags-y += $(call cc-option,-march=pentium-mmx,-march=i586) |
466 | ||
5c811e59 | 467 | In the above example, cflags-y will be assigned the option |
a07f6033 JE |
468 | -march=pentium-mmx if supported by $(CC), otherwise -march=i586. |
469 | The second argument to cc-option is optional, and if omitted, | |
20a468b5 | 470 | cflags-y will be assigned no value if first option is not supported. |
a0f97e06 | 471 | Note: cc-option uses KBUILD_CFLAGS for $(CC) options |
20a468b5 SR |
472 | |
473 | cc-option-yn | |
39e6e9cf | 474 | cc-option-yn is used to check if gcc supports a given option |
20a468b5 SR |
475 | and return 'y' if supported, otherwise 'n'. |
476 | ||
477 | Example: | |
478 | #arch/ppc/Makefile | |
479 | biarch := $(call cc-option-yn, -m32) | |
480 | aflags-$(biarch) += -a32 | |
481 | cflags-$(biarch) += -m32 | |
39e6e9cf | 482 | |
a07f6033 JE |
483 | In the above example, $(biarch) is set to y if $(CC) supports the -m32 |
484 | option. When $(biarch) equals 'y', the expanded variables $(aflags-y) | |
485 | and $(cflags-y) will be assigned the values -a32 and -m32, | |
486 | respectively. | |
a0f97e06 | 487 | Note: cc-option-yn uses KBUILD_CFLAGS for $(CC) options |
20a468b5 | 488 | |
8417da6f MM |
489 | cc-disable-warning |
490 | cc-disable-warning checks if gcc supports a given warning and returns | |
491 | the commandline switch to disable it. This special function is needed, | |
492 | because gcc 4.4 and later accept any unknown -Wno-* option and only | |
493 | warn about it if there is another warning in the source file. | |
494 | ||
495 | Example: | |
496 | KBUILD_CFLAGS += $(call cc-disable-warning, unused-but-set-variable) | |
497 | ||
498 | In the above example, -Wno-unused-but-set-variable will be added to | |
499 | KBUILD_CFLAGS only if gcc really accepts it. | |
500 | ||
20a468b5 | 501 | cc-version |
a07f6033 | 502 | cc-version returns a numerical version of the $(CC) compiler version. |
20a468b5 SR |
503 | The format is <major><minor> where both are two digits. So for example |
504 | gcc 3.41 would return 0341. | |
505 | cc-version is useful when a specific $(CC) version is faulty in one | |
a07f6033 | 506 | area, for example -mregparm=3 was broken in some gcc versions |
20a468b5 SR |
507 | even though the option was accepted by gcc. |
508 | ||
509 | Example: | |
25eb650a | 510 | #arch/x86/Makefile |
20a468b5 | 511 | cflags-y += $(shell \ |
665d92e3 | 512 | if [ $(cc-version) -ge 0300 ] ; then \ |
20a468b5 SR |
513 | echo "-mregparm=3"; fi ;) |
514 | ||
a07f6033 | 515 | In the above example, -mregparm=3 is only used for gcc version greater |
20a468b5 SR |
516 | than or equal to gcc 3.0. |
517 | ||
518 | cc-ifversion | |
6dcb4e5e MY |
519 | cc-ifversion tests the version of $(CC) and equals the fourth parameter |
520 | if version expression is true, or the fifth (if given) if the version | |
521 | expression is false. | |
20a468b5 SR |
522 | |
523 | Example: | |
524 | #fs/reiserfs/Makefile | |
f77bf014 | 525 | ccflags-y := $(call cc-ifversion, -lt, 0402, -O1) |
20a468b5 | 526 | |
f77bf014 | 527 | In this example, ccflags-y will be assigned the value -O1 if the |
20a468b5 | 528 | $(CC) version is less than 4.2. |
39e6e9cf | 529 | cc-ifversion takes all the shell operators: |
20a468b5 SR |
530 | -eq, -ne, -lt, -le, -gt, and -ge |
531 | The third parameter may be a text as in this example, but it may also | |
532 | be an expanded variable or a macro. | |
533 | ||
7015030f SR |
534 | cc-fullversion |
535 | cc-fullversion is useful when the exact version of gcc is needed. | |
536 | One typical use-case is when a specific GCC version is broken. | |
537 | cc-fullversion points out a more specific version than cc-version does. | |
538 | ||
539 | Example: | |
540 | #arch/powerpc/Makefile | |
665d92e3 | 541 | $(Q)if test "$(cc-fullversion)" = "040200" ; then \ |
7015030f SR |
542 | echo -n '*** GCC-4.2.0 cannot compile the 64-bit powerpc ' ; \ |
543 | false ; \ | |
544 | fi | |
545 | ||
39fed701 GU |
546 | In this example for a specific GCC version the build will error out |
547 | explaining to the user why it stops. | |
1da177e4 | 548 | |
910b4046 | 549 | cc-cross-prefix |
631bcfbb | 550 | cc-cross-prefix is used to check if there exists a $(CC) in path with |
910b4046 SR |
551 | one of the listed prefixes. The first prefix where there exist a |
552 | prefix$(CC) in the PATH is returned - and if no prefix$(CC) is found | |
553 | then nothing is returned. | |
554 | Additional prefixes are separated by a single space in the | |
555 | call of cc-cross-prefix. | |
631bcfbb GU |
556 | This functionality is useful for architecture Makefiles that try |
557 | to set CROSS_COMPILE to well-known values but may have several | |
910b4046 | 558 | values to select between. |
631bcfbb GU |
559 | It is recommended only to try to set CROSS_COMPILE if it is a cross |
560 | build (host arch is different from target arch). And if CROSS_COMPILE | |
910b4046 SR |
561 | is already set then leave it with the old value. |
562 | ||
563 | Example: | |
564 | #arch/m68k/Makefile | |
565 | ifneq ($(SUBARCH),$(ARCH)) | |
566 | ifeq ($(CROSS_COMPILE),) | |
567 | CROSS_COMPILE := $(call cc-cross-prefix, m68k-linux-gnu-) | |
568 | endif | |
569 | endif | |
570 | ||
691ef3e7 SR |
571 | --- 3.12 $(LD) support functions |
572 | ||
573 | ld-option | |
574 | ld-option is used to check if $(LD) supports the supplied option. | |
575 | ld-option takes two options as arguments. | |
576 | The second argument is an optional option that can be used if the | |
577 | first option is not supported by $(LD). | |
578 | ||
579 | Example: | |
580 | #Makefile | |
5b83df2b | 581 | LDFLAGS_vmlinux += $(call ld-option, -X) |
691ef3e7 SR |
582 | |
583 | ||
1da177e4 LT |
584 | === 4 Host Program support |
585 | ||
586 | Kbuild supports building executables on the host for use during the | |
587 | compilation stage. | |
588 | Two steps are required in order to use a host executable. | |
589 | ||
590 | The first step is to tell kbuild that a host program exists. This is | |
591 | done utilising the variable hostprogs-y. | |
592 | ||
593 | The second step is to add an explicit dependency to the executable. | |
39e6e9cf | 594 | This can be done in two ways. Either add the dependency in a rule, |
1da177e4 LT |
595 | or utilise the variable $(always). |
596 | Both possibilities are described in the following. | |
597 | ||
598 | --- 4.1 Simple Host Program | |
599 | ||
600 | In some cases there is a need to compile and run a program on the | |
601 | computer where the build is running. | |
602 | The following line tells kbuild that the program bin2hex shall be | |
603 | built on the build host. | |
604 | ||
605 | Example: | |
606 | hostprogs-y := bin2hex | |
607 | ||
608 | Kbuild assumes in the above example that bin2hex is made from a single | |
609 | c-source file named bin2hex.c located in the same directory as | |
610 | the Makefile. | |
39e6e9cf | 611 | |
1da177e4 LT |
612 | --- 4.2 Composite Host Programs |
613 | ||
614 | Host programs can be made up based on composite objects. | |
615 | The syntax used to define composite objects for host programs is | |
616 | similar to the syntax used for kernel objects. | |
5d3f083d | 617 | $(<executable>-objs) lists all objects used to link the final |
1da177e4 LT |
618 | executable. |
619 | ||
620 | Example: | |
621 | #scripts/lxdialog/Makefile | |
39e6e9cf | 622 | hostprogs-y := lxdialog |
1da177e4 LT |
623 | lxdialog-objs := checklist.o lxdialog.o |
624 | ||
625 | Objects with extension .o are compiled from the corresponding .c | |
a07f6033 | 626 | files. In the above example, checklist.c is compiled to checklist.o |
1da177e4 | 627 | and lxdialog.c is compiled to lxdialog.o. |
a07f6033 | 628 | Finally, the two .o files are linked to the executable, lxdialog. |
1da177e4 LT |
629 | Note: The syntax <executable>-y is not permitted for host-programs. |
630 | ||
62e22107 | 631 | --- 4.3 Using C++ for host programs |
1da177e4 LT |
632 | |
633 | kbuild offers support for host programs written in C++. This was | |
634 | introduced solely to support kconfig, and is not recommended | |
635 | for general use. | |
636 | ||
637 | Example: | |
638 | #scripts/kconfig/Makefile | |
639 | hostprogs-y := qconf | |
640 | qconf-cxxobjs := qconf.o | |
641 | ||
642 | In the example above the executable is composed of the C++ file | |
643 | qconf.cc - identified by $(qconf-cxxobjs). | |
39e6e9cf | 644 | |
39fed701 | 645 | If qconf is composed of a mixture of .c and .cc files, then an |
1da177e4 LT |
646 | additional line can be used to identify this. |
647 | ||
648 | Example: | |
649 | #scripts/kconfig/Makefile | |
650 | hostprogs-y := qconf | |
651 | qconf-cxxobjs := qconf.o | |
652 | qconf-objs := check.o | |
39e6e9cf | 653 | |
62e22107 | 654 | --- 4.4 Controlling compiler options for host programs |
1da177e4 LT |
655 | |
656 | When compiling host programs, it is possible to set specific flags. | |
657 | The programs will always be compiled utilising $(HOSTCC) passed | |
658 | the options specified in $(HOSTCFLAGS). | |
659 | To set flags that will take effect for all host programs created | |
a07f6033 | 660 | in that Makefile, use the variable HOST_EXTRACFLAGS. |
1da177e4 LT |
661 | |
662 | Example: | |
663 | #scripts/lxdialog/Makefile | |
664 | HOST_EXTRACFLAGS += -I/usr/include/ncurses | |
39e6e9cf | 665 | |
1da177e4 LT |
666 | To set specific flags for a single file the following construction |
667 | is used: | |
668 | ||
669 | Example: | |
670 | #arch/ppc64/boot/Makefile | |
671 | HOSTCFLAGS_piggyback.o := -DKERNELBASE=$(KERNELBASE) | |
39e6e9cf | 672 | |
1da177e4 | 673 | It is also possible to specify additional options to the linker. |
39e6e9cf | 674 | |
1da177e4 LT |
675 | Example: |
676 | #scripts/kconfig/Makefile | |
677 | HOSTLOADLIBES_qconf := -L$(QTDIR)/lib | |
678 | ||
a07f6033 JE |
679 | When linking qconf, it will be passed the extra option |
680 | "-L$(QTDIR)/lib". | |
39e6e9cf | 681 | |
62e22107 | 682 | --- 4.5 When host programs are actually built |
1da177e4 LT |
683 | |
684 | Kbuild will only build host-programs when they are referenced | |
685 | as a prerequisite. | |
686 | This is possible in two ways: | |
687 | ||
688 | (1) List the prerequisite explicitly in a special rule. | |
689 | ||
690 | Example: | |
691 | #drivers/pci/Makefile | |
692 | hostprogs-y := gen-devlist | |
693 | $(obj)/devlist.h: $(src)/pci.ids $(obj)/gen-devlist | |
694 | ( cd $(obj); ./gen-devlist ) < $< | |
695 | ||
39e6e9cf | 696 | The target $(obj)/devlist.h will not be built before |
1da177e4 LT |
697 | $(obj)/gen-devlist is updated. Note that references to |
698 | the host programs in special rules must be prefixed with $(obj). | |
699 | ||
700 | (2) Use $(always) | |
701 | When there is no suitable special rule, and the host program | |
702 | shall be built when a makefile is entered, the $(always) | |
703 | variable shall be used. | |
704 | ||
705 | Example: | |
706 | #scripts/lxdialog/Makefile | |
707 | hostprogs-y := lxdialog | |
708 | always := $(hostprogs-y) | |
709 | ||
710 | This will tell kbuild to build lxdialog even if not referenced in | |
711 | any rule. | |
712 | ||
62e22107 | 713 | --- 4.6 Using hostprogs-$(CONFIG_FOO) |
1da177e4 | 714 | |
39e6e9cf | 715 | A typical pattern in a Kbuild file looks like this: |
1da177e4 LT |
716 | |
717 | Example: | |
718 | #scripts/Makefile | |
719 | hostprogs-$(CONFIG_KALLSYMS) += kallsyms | |
720 | ||
721 | Kbuild knows about both 'y' for built-in and 'm' for module. | |
39fed701 | 722 | So if a config symbol evaluates to 'm', kbuild will still build |
a07f6033 JE |
723 | the binary. In other words, Kbuild handles hostprogs-m exactly |
724 | like hostprogs-y. But only hostprogs-y is recommended to be used | |
725 | when no CONFIG symbols are involved. | |
1da177e4 LT |
726 | |
727 | === 5 Kbuild clean infrastructure | |
728 | ||
a07f6033 | 729 | "make clean" deletes most generated files in the obj tree where the kernel |
1da177e4 LT |
730 | is compiled. This includes generated files such as host programs. |
731 | Kbuild knows targets listed in $(hostprogs-y), $(hostprogs-m), $(always), | |
732 | $(extra-y) and $(targets). They are all deleted during "make clean". | |
733 | Files matching the patterns "*.[oas]", "*.ko", plus some additional files | |
734 | generated by kbuild are deleted all over the kernel src tree when | |
735 | "make clean" is executed. | |
736 | ||
737 | Additional files can be specified in kbuild makefiles by use of $(clean-files). | |
738 | ||
739 | Example: | |
97659181 MM |
740 | #lib/Makefile |
741 | clean-files := crc32table.h | |
1da177e4 | 742 | |
bd55daf4 JR |
743 | When executing "make clean", the file "crc32table.h" will be deleted. |
744 | Kbuild will assume files to be in the same relative directory as the | |
97659181 | 745 | Makefile, except if prefixed with $(objtree). |
1da177e4 | 746 | |
39e6e9cf BH |
747 | To delete a directory hierarchy use: |
748 | ||
1da177e4 LT |
749 | Example: |
750 | #scripts/package/Makefile | |
751 | clean-dirs := $(objtree)/debian/ | |
752 | ||
97659181 MM |
753 | This will delete the directory debian in the toplevel directory, including all |
754 | subdirectories. | |
1da177e4 | 755 | |
ef8ff89b MM |
756 | To exclude certain files from make clean, use the $(no-clean-files) variable. |
757 | This is only a special case used in the top level Kbuild file: | |
758 | ||
759 | Example: | |
760 | #Kbuild | |
761 | no-clean-files := $(bounds-file) $(offsets-file) | |
762 | ||
1da177e4 LT |
763 | Usually kbuild descends down in subdirectories due to "obj-* := dir/", |
764 | but in the architecture makefiles where the kbuild infrastructure | |
765 | is not sufficient this sometimes needs to be explicit. | |
766 | ||
767 | Example: | |
25eb650a | 768 | #arch/x86/boot/Makefile |
1da177e4 LT |
769 | subdir- := compressed/ |
770 | ||
771 | The above assignment instructs kbuild to descend down in the | |
772 | directory compressed/ when "make clean" is executed. | |
773 | ||
39fed701 | 774 | To support the clean infrastructure in the Makefiles that build the |
1da177e4 LT |
775 | final bootimage there is an optional target named archclean: |
776 | ||
777 | Example: | |
25eb650a | 778 | #arch/x86/Makefile |
1da177e4 | 779 | archclean: |
25eb650a | 780 | $(Q)$(MAKE) $(clean)=arch/x86/boot |
1da177e4 | 781 | |
25eb650a WG |
782 | When "make clean" is executed, make will descend down in arch/x86/boot, |
783 | and clean as usual. The Makefile located in arch/x86/boot/ may use | |
1da177e4 LT |
784 | the subdir- trick to descend further down. |
785 | ||
786 | Note 1: arch/$(ARCH)/Makefile cannot use "subdir-", because that file is | |
787 | included in the top level makefile, and the kbuild infrastructure | |
788 | is not operational at that point. | |
789 | ||
790 | Note 2: All directories listed in core-y, libs-y, drivers-y and net-y will | |
791 | be visited during "make clean". | |
792 | ||
793 | === 6 Architecture Makefiles | |
794 | ||
795 | The top level Makefile sets up the environment and does the preparation, | |
796 | before starting to descend down in the individual directories. | |
a07f6033 JE |
797 | The top level makefile contains the generic part, whereas |
798 | arch/$(ARCH)/Makefile contains what is required to set up kbuild | |
799 | for said architecture. | |
800 | To do so, arch/$(ARCH)/Makefile sets up a number of variables and defines | |
1da177e4 LT |
801 | a few targets. |
802 | ||
a07f6033 JE |
803 | When kbuild executes, the following steps are followed (roughly): |
804 | 1) Configuration of the kernel => produce .config | |
1da177e4 | 805 | 2) Store kernel version in include/linux/version.h |
b22ae40e | 806 | 3) Updating all other prerequisites to the target prepare: |
1da177e4 | 807 | - Additional prerequisites are specified in arch/$(ARCH)/Makefile |
b22ae40e | 808 | 4) Recursively descend down in all directories listed in |
1da177e4 | 809 | init-* core* drivers-* net-* libs-* and build all targets. |
a07f6033 | 810 | - The values of the above variables are expanded in arch/$(ARCH)/Makefile. |
b22ae40e | 811 | 5) All object files are then linked and the resulting file vmlinux is |
a07f6033 | 812 | located at the root of the obj tree. |
1da177e4 LT |
813 | The very first objects linked are listed in head-y, assigned by |
814 | arch/$(ARCH)/Makefile. | |
b22ae40e | 815 | 6) Finally, the architecture-specific part does any required post processing |
1da177e4 LT |
816 | and builds the final bootimage. |
817 | - This includes building boot records | |
5c811e59 | 818 | - Preparing initrd images and the like |
1da177e4 LT |
819 | |
820 | ||
821 | --- 6.1 Set variables to tweak the build to the architecture | |
822 | ||
823 | LDFLAGS Generic $(LD) options | |
824 | ||
825 | Flags used for all invocations of the linker. | |
826 | Often specifying the emulation is sufficient. | |
827 | ||
828 | Example: | |
829 | #arch/s390/Makefile | |
830 | LDFLAGS := -m elf_s390 | |
f77bf014 | 831 | Note: ldflags-y can be used to further customise |
a9af3305 | 832 | the flags used. See chapter 3.7. |
39e6e9cf | 833 | |
1da177e4 LT |
834 | LDFLAGS_MODULE Options for $(LD) when linking modules |
835 | ||
836 | LDFLAGS_MODULE is used to set specific flags for $(LD) when | |
837 | linking the .ko files used for modules. | |
838 | Default is "-r", for relocatable output. | |
839 | ||
840 | LDFLAGS_vmlinux Options for $(LD) when linking vmlinux | |
841 | ||
842 | LDFLAGS_vmlinux is used to specify additional flags to pass to | |
a07f6033 | 843 | the linker when linking the final vmlinux image. |
1da177e4 LT |
844 | LDFLAGS_vmlinux uses the LDFLAGS_$@ support. |
845 | ||
846 | Example: | |
25eb650a | 847 | #arch/x86/Makefile |
1da177e4 LT |
848 | LDFLAGS_vmlinux := -e stext |
849 | ||
850 | OBJCOPYFLAGS objcopy flags | |
851 | ||
852 | When $(call if_changed,objcopy) is used to translate a .o file, | |
a07f6033 | 853 | the flags specified in OBJCOPYFLAGS will be used. |
1da177e4 LT |
854 | $(call if_changed,objcopy) is often used to generate raw binaries on |
855 | vmlinux. | |
856 | ||
857 | Example: | |
858 | #arch/s390/Makefile | |
859 | OBJCOPYFLAGS := -O binary | |
860 | ||
861 | #arch/s390/boot/Makefile | |
862 | $(obj)/image: vmlinux FORCE | |
863 | $(call if_changed,objcopy) | |
864 | ||
a07f6033 | 865 | In this example, the binary $(obj)/image is a binary version of |
1da177e4 LT |
866 | vmlinux. The usage of $(call if_changed,xxx) will be described later. |
867 | ||
222d394d | 868 | KBUILD_AFLAGS $(AS) assembler flags |
1da177e4 LT |
869 | |
870 | Default value - see top level Makefile | |
871 | Append or modify as required per architecture. | |
872 | ||
873 | Example: | |
874 | #arch/sparc64/Makefile | |
222d394d | 875 | KBUILD_AFLAGS += -m64 -mcpu=ultrasparc |
1da177e4 | 876 | |
a0f97e06 | 877 | KBUILD_CFLAGS $(CC) compiler flags |
1da177e4 LT |
878 | |
879 | Default value - see top level Makefile | |
880 | Append or modify as required per architecture. | |
881 | ||
a0f97e06 | 882 | Often, the KBUILD_CFLAGS variable depends on the configuration. |
1da177e4 LT |
883 | |
884 | Example: | |
ff4eb04c PB |
885 | #arch/x86/boot/compressed/Makefile |
886 | cflags-$(CONFIG_X86_32) := -march=i386 | |
887 | cflags-$(CONFIG_X86_64) := -mcmodel=small | |
a0f97e06 | 888 | KBUILD_CFLAGS += $(cflags-y) |
1da177e4 LT |
889 | |
890 | Many arch Makefiles dynamically run the target C compiler to | |
891 | probe supported options: | |
892 | ||
25eb650a | 893 | #arch/x86/Makefile |
1da177e4 LT |
894 | |
895 | ... | |
896 | cflags-$(CONFIG_MPENTIUMII) += $(call cc-option,\ | |
897 | -march=pentium2,-march=i686) | |
898 | ... | |
899 | # Disable unit-at-a-time mode ... | |
a0f97e06 | 900 | KBUILD_CFLAGS += $(call cc-option,-fno-unit-at-a-time) |
1da177e4 LT |
901 | ... |
902 | ||
903 | ||
a07f6033 | 904 | The first example utilises the trick that a config option expands |
1da177e4 LT |
905 | to 'y' when selected. |
906 | ||
80c00ba9 | 907 | KBUILD_AFLAGS_KERNEL $(AS) options specific for built-in |
1da177e4 | 908 | |
80c00ba9 | 909 | $(KBUILD_AFLAGS_KERNEL) contains extra C compiler flags used to compile |
1da177e4 LT |
910 | resident kernel code. |
911 | ||
6588169d | 912 | KBUILD_AFLAGS_MODULE Options for $(AS) when building modules |
1da177e4 | 913 | |
39fed701 | 914 | $(KBUILD_AFLAGS_MODULE) is used to add arch-specific options that |
6588169d SR |
915 | are used for $(AS). |
916 | From commandline AFLAGS_MODULE shall be used (see kbuild.txt). | |
1da177e4 | 917 | |
80c00ba9 SR |
918 | KBUILD_CFLAGS_KERNEL $(CC) options specific for built-in |
919 | ||
920 | $(KBUILD_CFLAGS_KERNEL) contains extra C compiler flags used to compile | |
921 | resident kernel code. | |
922 | ||
6588169d SR |
923 | KBUILD_CFLAGS_MODULE Options for $(CC) when building modules |
924 | ||
39fed701 | 925 | $(KBUILD_CFLAGS_MODULE) is used to add arch-specific options that |
6588169d SR |
926 | are used for $(CC). |
927 | From commandline CFLAGS_MODULE shall be used (see kbuild.txt). | |
928 | ||
929 | KBUILD_LDFLAGS_MODULE Options for $(LD) when linking modules | |
930 | ||
39fed701 | 931 | $(KBUILD_LDFLAGS_MODULE) is used to add arch-specific options |
6588169d SR |
932 | used when linking modules. This is often a linker script. |
933 | From commandline LDFLAGS_MODULE shall be used (see kbuild.txt). | |
39e6e9cf | 934 | |
40df759e MM |
935 | KBUILD_ARFLAGS Options for $(AR) when creating archives |
936 | ||
937 | $(KBUILD_ARFLAGS) set by the top level Makefile to "D" (deterministic | |
938 | mode) if this option is supported by $(AR). | |
939 | ||
61754c18 MM |
940 | ARCH_CPPFLAGS, ARCH_AFLAGS, ARCH_CFLAGS Overrides the kbuild defaults |
941 | ||
942 | These variables are appended to the KBUILD_CPPFLAGS, | |
943 | KBUILD_AFLAGS, and KBUILD_CFLAGS, respectively, after the | |
944 | top-level Makefile has set any other flags. This provides a | |
945 | means for an architecture to override the defaults. | |
946 | ||
947 | ||
052ad274 PA |
948 | --- 6.2 Add prerequisites to archheaders: |
949 | ||
950 | The archheaders: rule is used to generate header files that | |
951 | may be installed into user space by "make header_install" or | |
952 | "make headers_install_all". In order to support | |
953 | "make headers_install_all", this target has to be able to run | |
954 | on an unconfigured tree, or a tree configured for another | |
955 | architecture. | |
956 | ||
957 | It is run before "make archprepare" when run on the | |
958 | architecture itself. | |
959 | ||
960 | ||
961 | --- 6.3 Add prerequisites to archprepare: | |
1da177e4 | 962 | |
a07f6033 | 963 | The archprepare: rule is used to list prerequisites that need to be |
1da177e4 | 964 | built before starting to descend down in the subdirectories. |
a07f6033 | 965 | This is usually used for header files containing assembler constants. |
1da177e4 LT |
966 | |
967 | Example: | |
5bb78269 SR |
968 | #arch/arm/Makefile |
969 | archprepare: maketools | |
1da177e4 | 970 | |
a07f6033 | 971 | In this example, the file target maketools will be processed |
5bb78269 | 972 | before descending down in the subdirectories. |
1da177e4 LT |
973 | See also chapter XXX-TODO that describe how kbuild supports |
974 | generating offset header files. | |
975 | ||
976 | ||
052ad274 | 977 | --- 6.4 List directories to visit when descending |
1da177e4 LT |
978 | |
979 | An arch Makefile cooperates with the top Makefile to define variables | |
980 | which specify how to build the vmlinux file. Note that there is no | |
981 | corresponding arch-specific section for modules; the module-building | |
982 | machinery is all architecture-independent. | |
983 | ||
39e6e9cf | 984 | |
1da177e4 LT |
985 | head-y, init-y, core-y, libs-y, drivers-y, net-y |
986 | ||
a07f6033 JE |
987 | $(head-y) lists objects to be linked first in vmlinux. |
988 | $(libs-y) lists directories where a lib.a archive can be located. | |
5c811e59 | 989 | The rest list directories where a built-in.o object file can be |
a07f6033 | 990 | located. |
1da177e4 LT |
991 | |
992 | $(init-y) objects will be located after $(head-y). | |
993 | Then the rest follows in this order: | |
994 | $(core-y), $(libs-y), $(drivers-y) and $(net-y). | |
995 | ||
a07f6033 | 996 | The top level Makefile defines values for all generic directories, |
5c811e59 | 997 | and arch/$(ARCH)/Makefile only adds architecture-specific directories. |
1da177e4 LT |
998 | |
999 | Example: | |
1000 | #arch/sparc64/Makefile | |
1001 | core-y += arch/sparc64/kernel/ | |
1002 | libs-y += arch/sparc64/prom/ arch/sparc64/lib/ | |
1003 | drivers-$(CONFIG_OPROFILE) += arch/sparc64/oprofile/ | |
1004 | ||
1005 | ||
052ad274 | 1006 | --- 6.5 Architecture-specific boot images |
1da177e4 LT |
1007 | |
1008 | An arch Makefile specifies goals that take the vmlinux file, compress | |
1009 | it, wrap it in bootstrapping code, and copy the resulting files | |
1010 | somewhere. This includes various kinds of installation commands. | |
1011 | The actual goals are not standardized across architectures. | |
1012 | ||
1013 | It is common to locate any additional processing in a boot/ | |
1014 | directory below arch/$(ARCH)/. | |
1015 | ||
1016 | Kbuild does not provide any smart way to support building a | |
1017 | target specified in boot/. Therefore arch/$(ARCH)/Makefile shall | |
1018 | call make manually to build a target in boot/. | |
1019 | ||
1020 | The recommended approach is to include shortcuts in | |
1021 | arch/$(ARCH)/Makefile, and use the full path when calling down | |
1022 | into the arch/$(ARCH)/boot/Makefile. | |
1023 | ||
1024 | Example: | |
25eb650a WG |
1025 | #arch/x86/Makefile |
1026 | boot := arch/x86/boot | |
1da177e4 LT |
1027 | bzImage: vmlinux |
1028 | $(Q)$(MAKE) $(build)=$(boot) $(boot)/$@ | |
1029 | ||
1030 | "$(Q)$(MAKE) $(build)=<dir>" is the recommended way to invoke | |
1031 | make in a subdirectory. | |
1032 | ||
5c811e59 | 1033 | There are no rules for naming architecture-specific targets, |
1da177e4 | 1034 | but executing "make help" will list all relevant targets. |
a07f6033 | 1035 | To support this, $(archhelp) must be defined. |
1da177e4 LT |
1036 | |
1037 | Example: | |
25eb650a | 1038 | #arch/x86/Makefile |
1da177e4 LT |
1039 | define archhelp |
1040 | echo '* bzImage - Image (arch/$(ARCH)/boot/bzImage)' | |
39e6e9cf | 1041 | endif |
1da177e4 LT |
1042 | |
1043 | When make is executed without arguments, the first goal encountered | |
1044 | will be built. In the top level Makefile the first goal present | |
1045 | is all:. | |
a07f6033 JE |
1046 | An architecture shall always, per default, build a bootable image. |
1047 | In "make help", the default goal is highlighted with a '*'. | |
1da177e4 LT |
1048 | Add a new prerequisite to all: to select a default goal different |
1049 | from vmlinux. | |
1050 | ||
1051 | Example: | |
25eb650a | 1052 | #arch/x86/Makefile |
39e6e9cf | 1053 | all: bzImage |
1da177e4 LT |
1054 | |
1055 | When "make" is executed without arguments, bzImage will be built. | |
1056 | ||
052ad274 | 1057 | --- 6.6 Building non-kbuild targets |
1da177e4 LT |
1058 | |
1059 | extra-y | |
1060 | ||
39fed701 | 1061 | extra-y specifies additional targets created in the current |
1da177e4 LT |
1062 | directory, in addition to any targets specified by obj-*. |
1063 | ||
1064 | Listing all targets in extra-y is required for two purposes: | |
1065 | 1) Enable kbuild to check changes in command lines | |
1066 | - When $(call if_changed,xxx) is used | |
1067 | 2) kbuild knows what files to delete during "make clean" | |
1068 | ||
1069 | Example: | |
25eb650a | 1070 | #arch/x86/kernel/Makefile |
1da177e4 LT |
1071 | extra-y := head.o init_task.o |
1072 | ||
a07f6033 | 1073 | In this example, extra-y is used to list object files that |
1da177e4 LT |
1074 | shall be built, but shall not be linked as part of built-in.o. |
1075 | ||
39e6e9cf | 1076 | |
052ad274 | 1077 | --- 6.7 Commands useful for building a boot image |
1da177e4 LT |
1078 | |
1079 | Kbuild provides a few macros that are useful when building a | |
1080 | boot image. | |
1081 | ||
1082 | if_changed | |
1083 | ||
1084 | if_changed is the infrastructure used for the following commands. | |
1085 | ||
1086 | Usage: | |
1087 | target: source(s) FORCE | |
ef80f0a1 | 1088 | $(call if_changed,ld/objcopy/gzip/...) |
1da177e4 | 1089 | |
a07f6033 | 1090 | When the rule is evaluated, it is checked to see if any files |
5c811e59 | 1091 | need an update, or the command line has changed since the last |
1da177e4 LT |
1092 | invocation. The latter will force a rebuild if any options |
1093 | to the executable have changed. | |
1094 | Any target that utilises if_changed must be listed in $(targets), | |
1095 | otherwise the command line check will fail, and the target will | |
1096 | always be built. | |
1097 | Assignments to $(targets) are without $(obj)/ prefix. | |
1098 | if_changed may be used in conjunction with custom commands as | |
052ad274 | 1099 | defined in 6.8 "Custom kbuild commands". |
49490571 | 1100 | |
1da177e4 | 1101 | Note: It is a typical mistake to forget the FORCE prerequisite. |
49490571 PBG |
1102 | Another common pitfall is that whitespace is sometimes |
1103 | significant; for instance, the below will fail (note the extra space | |
1104 | after the comma): | |
1105 | target: source(s) FORCE | |
ef80f0a1 | 1106 | #WRONG!# $(call if_changed, ld/objcopy/gzip/...) |
1da177e4 LT |
1107 | |
1108 | ld | |
a07f6033 | 1109 | Link target. Often, LDFLAGS_$@ is used to set specific options to ld. |
39e6e9cf | 1110 | |
1da177e4 | 1111 | Example: |
25eb650a | 1112 | #arch/x86/boot/Makefile |
1da177e4 LT |
1113 | LDFLAGS_bootsect := -Ttext 0x0 -s --oformat binary |
1114 | LDFLAGS_setup := -Ttext 0x0 -s --oformat binary -e begtext | |
1115 | ||
1116 | targets += setup setup.o bootsect bootsect.o | |
1117 | $(obj)/setup $(obj)/bootsect: %: %.o FORCE | |
1118 | $(call if_changed,ld) | |
1119 | ||
a07f6033 JE |
1120 | In this example, there are two possible targets, requiring different |
1121 | options to the linker. The linker options are specified using the | |
1da177e4 | 1122 | LDFLAGS_$@ syntax - one for each potential target. |
5d3f083d | 1123 | $(targets) are assigned all potential targets, by which kbuild knows |
1da177e4 LT |
1124 | the targets and will: |
1125 | 1) check for commandline changes | |
1126 | 2) delete target during make clean | |
1127 | ||
1128 | The ": %: %.o" part of the prerequisite is a shorthand that | |
39fed701 | 1129 | frees us from listing the setup.o and bootsect.o files. |
ef80f0a1 | 1130 | Note: It is a common mistake to forget the "targets :=" assignment, |
1da177e4 LT |
1131 | resulting in the target file being recompiled for no |
1132 | obvious reason. | |
1133 | ||
d87e47e1 C |
1134 | objcopy |
1135 | Copy binary. Uses OBJCOPYFLAGS usually specified in | |
1136 | arch/$(ARCH)/Makefile. | |
1137 | OBJCOPYFLAGS_$@ may be used to set additional options. | |
1138 | ||
1139 | gzip | |
1140 | Compress target. Use maximum compression to compress target. | |
1141 | ||
1142 | Example: | |
1143 | #arch/x86/boot/compressed/Makefile | |
1144 | $(obj)/vmlinux.bin.gz: $(vmlinux.bin.all-y) FORCE | |
1145 | $(call if_changed,gzip) | |
1146 | ||
aab94339 | 1147 | dtc |
c1410562 | 1148 | Create flattened device tree blob object suitable for linking |
aab94339 DB |
1149 | into vmlinux. Device tree blobs linked into vmlinux are placed |
1150 | in an init section in the image. Platform code *must* copy the | |
1151 | blob to non-init memory prior to calling unflatten_device_tree(). | |
1152 | ||
90b335fb SW |
1153 | To use this command, simply add *.dtb into obj-y or targets, or make |
1154 | some other target depend on %.dtb | |
aab94339 | 1155 | |
90b335fb SW |
1156 | A central rule exists to create $(obj)/%.dtb from $(src)/%.dts; |
1157 | architecture Makefiles do no need to explicitly write out that rule. | |
aab94339 | 1158 | |
90b335fb SW |
1159 | Example: |
1160 | targets += $(dtb-y) | |
90b335fb | 1161 | DTC_FLAGS ?= -p 1024 |
1da177e4 | 1162 | |
052ad274 | 1163 | --- 6.8 Custom kbuild commands |
1da177e4 | 1164 | |
a07f6033 | 1165 | When kbuild is executing with KBUILD_VERBOSE=0, then only a shorthand |
1da177e4 LT |
1166 | of a command is normally displayed. |
1167 | To enable this behaviour for custom commands kbuild requires | |
1168 | two variables to be set: | |
1169 | quiet_cmd_<command> - what shall be echoed | |
1170 | cmd_<command> - the command to execute | |
1171 | ||
1172 | Example: | |
1173 | # | |
1174 | quiet_cmd_image = BUILD $@ | |
1175 | cmd_image = $(obj)/tools/build $(BUILDFLAGS) \ | |
1176 | $(obj)/vmlinux.bin > $@ | |
1177 | ||
1178 | targets += bzImage | |
1179 | $(obj)/bzImage: $(obj)/vmlinux.bin $(obj)/tools/build FORCE | |
1180 | $(call if_changed,image) | |
1181 | @echo 'Kernel: $@ is ready' | |
1182 | ||
a07f6033 | 1183 | When updating the $(obj)/bzImage target, the line |
1da177e4 | 1184 | |
25eb650a | 1185 | BUILD arch/x86/boot/bzImage |
1da177e4 LT |
1186 | |
1187 | will be displayed with "make KBUILD_VERBOSE=0". | |
39e6e9cf | 1188 | |
1da177e4 | 1189 | |
052ad274 | 1190 | --- 6.9 Preprocessing linker scripts |
1da177e4 | 1191 | |
a07f6033 | 1192 | When the vmlinux image is built, the linker script |
1da177e4 LT |
1193 | arch/$(ARCH)/kernel/vmlinux.lds is used. |
1194 | The script is a preprocessed variant of the file vmlinux.lds.S | |
1195 | located in the same directory. | |
a07f6033 | 1196 | kbuild knows .lds files and includes a rule *lds.S -> *lds. |
39e6e9cf | 1197 | |
1da177e4 | 1198 | Example: |
25eb650a | 1199 | #arch/x86/kernel/Makefile |
1da177e4 | 1200 | always := vmlinux.lds |
39e6e9cf | 1201 | |
1da177e4 LT |
1202 | #Makefile |
1203 | export CPPFLAGS_vmlinux.lds += -P -C -U$(ARCH) | |
39e6e9cf BH |
1204 | |
1205 | The assignment to $(always) is used to tell kbuild to build the | |
a07f6033 JE |
1206 | target vmlinux.lds. |
1207 | The assignment to $(CPPFLAGS_vmlinux.lds) tells kbuild to use the | |
1da177e4 | 1208 | specified options when building the target vmlinux.lds. |
39e6e9cf | 1209 | |
a07f6033 | 1210 | When building the *.lds target, kbuild uses the variables: |
06c5040c | 1211 | KBUILD_CPPFLAGS : Set in top-level Makefile |
f77bf014 | 1212 | cppflags-y : May be set in the kbuild makefile |
39fed701 | 1213 | CPPFLAGS_$(@F) : Target-specific flags. |
1da177e4 LT |
1214 | Note that the full filename is used in this |
1215 | assignment. | |
1216 | ||
39fed701 | 1217 | The kbuild infrastructure for *lds files is used in several |
5c811e59 | 1218 | architecture-specific files. |
1da177e4 | 1219 | |
052ad274 | 1220 | --- 6.10 Generic header files |
d8ecc5cd SR |
1221 | |
1222 | The directory include/asm-generic contains the header files | |
1223 | that may be shared between individual architectures. | |
1224 | The recommended approach how to use a generic header file is | |
1225 | to list the file in the Kbuild file. | |
d87e47e1 | 1226 | See "7.2 generic-y" for further info on syntax etc. |
d8ecc5cd | 1227 | |
fbe6e37d NP |
1228 | --- 6.11 Post-link pass |
1229 | ||
1230 | If the file arch/xxx/Makefile.postlink exists, this makefile | |
1231 | will be invoked for post-link objects (vmlinux and modules.ko) | |
1232 | for architectures to run post-link passes on. Must also handle | |
1233 | the clean target. | |
1234 | ||
1235 | This pass runs after kallsyms generation. If the architecture | |
1236 | needs to modify symbol locations, rather than manipulate the | |
1237 | kallsyms, it may be easier to add another postlink target for | |
1238 | .tmp_vmlinux? targets to be called from link-vmlinux.sh. | |
1239 | ||
1240 | For example, powerpc uses this to check relocation sanity of | |
1241 | the linked vmlinux file. | |
1242 | ||
c7bb349e SR |
1243 | === 7 Kbuild syntax for exported headers |
1244 | ||
39fed701 | 1245 | The kernel includes a set of headers that is exported to userspace. |
c95940f2 | 1246 | Many headers can be exported as-is but other headers require a |
c7bb349e SR |
1247 | minimal pre-processing before they are ready for user-space. |
1248 | The pre-processing does: | |
39fed701 | 1249 | - drop kernel-specific annotations |
c7bb349e | 1250 | - drop include of compiler.h |
c95940f2 | 1251 | - drop all sections that are kernel internal (guarded by ifdef __KERNEL__) |
c7bb349e | 1252 | |
fcc8487d | 1253 | All headers under include/uapi/, include/generated/uapi/, |
61562f98 | 1254 | arch/<arch>/include/uapi/ and arch/<arch>/include/generated/uapi/ |
fcc8487d | 1255 | are exported. |
c7bb349e | 1256 | |
fcc8487d ND |
1257 | A Kbuild file may be defined under arch/<arch>/include/uapi/asm/ and |
1258 | arch/<arch>/include/asm/ to list asm files coming from asm-generic. | |
1259 | See subsequent chapter for the syntax of the Kbuild file. | |
c7bb349e | 1260 | |
d87e47e1 | 1261 | --- 7.1 no-export-headers |
c7bb349e | 1262 | |
fcc8487d ND |
1263 | no-export-headers is essentially used by include/uapi/linux/Kbuild to |
1264 | avoid exporting specific headers (e.g. kvm.h) on architectures that do | |
1265 | not support it. It should be avoided as much as possible. | |
c7bb349e | 1266 | |
d87e47e1 | 1267 | --- 7.2 generic-y |
d8ecc5cd SR |
1268 | |
1269 | If an architecture uses a verbatim copy of a header from | |
1270 | include/asm-generic then this is listed in the file | |
1271 | arch/$(ARCH)/include/asm/Kbuild like this: | |
1272 | ||
1273 | Example: | |
1274 | #arch/x86/include/asm/Kbuild | |
1275 | generic-y += termios.h | |
1276 | generic-y += rtc.h | |
1277 | ||
1278 | During the prepare phase of the build a wrapper include | |
1279 | file is generated in the directory: | |
1280 | ||
1281 | arch/$(ARCH)/include/generated/asm | |
1282 | ||
1283 | When a header is exported where the architecture uses | |
1284 | the generic header a similar wrapper is generated as part | |
1285 | of the set of exported headers in the directory: | |
1286 | ||
1287 | usr/include/asm | |
1288 | ||
1289 | The generated wrapper will in both cases look like the following: | |
1290 | ||
1291 | Example: termios.h | |
1292 | #include <asm-generic/termios.h> | |
c7bb349e | 1293 | |
d87e47e1 | 1294 | --- 7.3 generated-y |
54b880ca JH |
1295 | |
1296 | If an architecture generates other header files alongside generic-y | |
ae3f4151 | 1297 | wrappers, generated-y specifies them. |
54b880ca JH |
1298 | |
1299 | This prevents them being treated as stale asm-generic wrappers and | |
1300 | removed. | |
1301 | ||
1302 | Example: | |
1303 | #arch/x86/include/asm/Kbuild | |
1304 | generated-y += syscalls_32.h | |
1305 | ||
d87e47e1 | 1306 | --- 7.4 mandatory-y |
fcc8487d ND |
1307 | |
1308 | mandatory-y is essentially used by include/uapi/asm-generic/Kbuild.asm | |
468f8763 | 1309 | to define the minimum set of headers that must be exported in |
fcc8487d ND |
1310 | include/asm. |
1311 | ||
1312 | The convention is to list one subdir per line and | |
1313 | preferably in alphabetic order. | |
1314 | ||
c7bb349e | 1315 | === 8 Kbuild Variables |
1da177e4 LT |
1316 | |
1317 | The top Makefile exports the following variables: | |
1318 | ||
1319 | VERSION, PATCHLEVEL, SUBLEVEL, EXTRAVERSION | |
1320 | ||
1321 | These variables define the current kernel version. A few arch | |
1322 | Makefiles actually use these values directly; they should use | |
1323 | $(KERNELRELEASE) instead. | |
1324 | ||
1325 | $(VERSION), $(PATCHLEVEL), and $(SUBLEVEL) define the basic | |
1326 | three-part version number, such as "2", "4", and "0". These three | |
1327 | values are always numeric. | |
1328 | ||
1329 | $(EXTRAVERSION) defines an even tinier sublevel for pre-patches | |
1330 | or additional patches. It is usually some non-numeric string | |
1331 | such as "-pre4", and is often blank. | |
1332 | ||
1333 | KERNELRELEASE | |
1334 | ||
1335 | $(KERNELRELEASE) is a single string such as "2.4.0-pre4", suitable | |
1336 | for constructing installation directory names or showing in | |
1337 | version strings. Some arch Makefiles use it for this purpose. | |
1338 | ||
1339 | ARCH | |
1340 | ||
1341 | This variable defines the target architecture, such as "i386", | |
1342 | "arm", or "sparc". Some kbuild Makefiles test $(ARCH) to | |
1343 | determine which files to compile. | |
1344 | ||
1345 | By default, the top Makefile sets $(ARCH) to be the same as the | |
1346 | host system architecture. For a cross build, a user may | |
1347 | override the value of $(ARCH) on the command line: | |
1348 | ||
1349 | make ARCH=m68k ... | |
1350 | ||
1351 | ||
1352 | INSTALL_PATH | |
1353 | ||
1354 | This variable defines a place for the arch Makefiles to install | |
1355 | the resident kernel image and System.map file. | |
5c811e59 | 1356 | Use this for architecture-specific install targets. |
1da177e4 LT |
1357 | |
1358 | INSTALL_MOD_PATH, MODLIB | |
1359 | ||
1360 | $(INSTALL_MOD_PATH) specifies a prefix to $(MODLIB) for module | |
1361 | installation. This variable is not defined in the Makefile but | |
1362 | may be passed in by the user if desired. | |
1363 | ||
1364 | $(MODLIB) specifies the directory for module installation. | |
1365 | The top Makefile defines $(MODLIB) to | |
1366 | $(INSTALL_MOD_PATH)/lib/modules/$(KERNELRELEASE). The user may | |
1367 | override this value on the command line if desired. | |
1368 | ||
ac031f26 TT |
1369 | INSTALL_MOD_STRIP |
1370 | ||
39fed701 | 1371 | If this variable is specified, it will cause modules to be stripped |
ac031f26 | 1372 | after they are installed. If INSTALL_MOD_STRIP is '1', then the |
39fed701 | 1373 | default option --strip-debug will be used. Otherwise, the |
177b241d GE |
1374 | INSTALL_MOD_STRIP value will be used as the option(s) to the strip |
1375 | command. | |
ac031f26 TT |
1376 | |
1377 | ||
c7bb349e | 1378 | === 9 Makefile language |
1da177e4 | 1379 | |
a07f6033 | 1380 | The kernel Makefiles are designed to be run with GNU Make. The Makefiles |
1da177e4 LT |
1381 | use only the documented features of GNU Make, but they do use many |
1382 | GNU extensions. | |
1383 | ||
1384 | GNU Make supports elementary list-processing functions. The kernel | |
1385 | Makefiles use a novel style of list building and manipulation with few | |
1386 | "if" statements. | |
1387 | ||
1388 | GNU Make has two assignment operators, ":=" and "=". ":=" performs | |
1389 | immediate evaluation of the right-hand side and stores an actual string | |
1390 | into the left-hand side. "=" is like a formula definition; it stores the | |
1391 | right-hand side in an unevaluated form and then evaluates this form each | |
1392 | time the left-hand side is used. | |
1393 | ||
1394 | There are some cases where "=" is appropriate. Usually, though, ":=" | |
1395 | is the right choice. | |
1396 | ||
c7bb349e | 1397 | === 10 Credits |
1da177e4 LT |
1398 | |
1399 | Original version made by Michael Elizabeth Chastain, <mailto:mec@shout.net> | |
1400 | Updates by Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de> | |
1401 | Updates by Sam Ravnborg <sam@ravnborg.org> | |
a07f6033 | 1402 | Language QA by Jan Engelhardt <jengelh@gmx.de> |
1da177e4 | 1403 | |
c7bb349e | 1404 | === 11 TODO |
1da177e4 | 1405 | |
a07f6033 | 1406 | - Describe how kbuild supports shipped files with _shipped. |
1da177e4 LT |
1407 | - Generating offset header files. |
1408 | - Add more variables to section 7? | |
1409 | ||
39e6e9cf BH |
1410 | |
1411 |