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