Commit 0dbbc713 authored by Sam Ravnborg's avatar Sam Ravnborg

kbuild: Trivial spelling / rephrasing

From: Ingo Molnar <mingo@elte.hu>
parent 0f4619a8
...@@ -119,7 +119,7 @@ more details, with real examples. ...@@ -119,7 +119,7 @@ more details, with real examples.
obj-y += foo.o obj-y += foo.o
This tell kbuild that there is one object in that directory named This tell kbuild that there is one object in that directory named
foo.o. foo.o will be build from foo.c or foo.S. foo.o. foo.o will be built from foo.c or foo.S.
If foo.o shall be built as a module, the variable obj-m is used. If foo.o shall be built as a module, the variable obj-m is used.
Therefore the following pattern is often used: Therefore the following pattern is often used:
...@@ -334,7 +334,7 @@ more details, with real examples. ...@@ -334,7 +334,7 @@ more details, with real examples.
--- 3.9 Dependency tracking --- 3.9 Dependency tracking
Kbuild track dependencies on the following: Kbuild tracks dependencies on the following:
1) All prerequisite files (both *.c and *.h) 1) All prerequisite files (both *.c and *.h)
2) CONFIG_ options used in all prerequisite files 2) CONFIG_ options used in all prerequisite files
3) Command-line used to compile target 3) Command-line used to compile target
...@@ -411,7 +411,7 @@ Both possibilities are described in the following. ...@@ -411,7 +411,7 @@ Both possibilities are described in the following.
--- 4.2 Composite Host Programs --- 4.2 Composite Host Programs
Host programs can be made up based on composite objects. Host programs can be made up based on composite objects.
The syntax used to define composite objetcs for host programs is The syntax used to define composite objects for host programs is
similar to the syntax used for kernel objects. similar to the syntax used for kernel objects.
$(<executeable>-objs) list all objects used to link the final $(<executeable>-objs) list all objects used to link the final
executable. executable.
...@@ -811,7 +811,7 @@ When kbuild executes the following steps are followed (roughly): ...@@ -811,7 +811,7 @@ When kbuild executes the following steps are followed (roughly):
extra-y extra-y
extra-y specify additional targets created in current extra-y specify additional targets created in the current
directory, in addition to any targets specified by obj-*. directory, in addition to any targets specified by obj-*.
Listing all targets in extra-y is required for two purposes: Listing all targets in extra-y is required for two purposes:
...@@ -829,7 +829,7 @@ When kbuild executes the following steps are followed (roughly): ...@@ -829,7 +829,7 @@ When kbuild executes the following steps are followed (roughly):
--- 6.6 Commands useful for building a boot image --- 6.6 Commands useful for building a boot image
Kbuild provide a few macros that are useful when building a Kbuild provides a few macros that are useful when building a
boot image. boot image.
if_changed if_changed
...@@ -872,7 +872,7 @@ When kbuild executes the following steps are followed (roughly): ...@@ -872,7 +872,7 @@ When kbuild executes the following steps are followed (roughly):
$(obj)/setup $(obj)/bootsect: %: %.o FORCE $(obj)/setup $(obj)/bootsect: %: %.o FORCE
$(call if_changed,ld) $(call if_changed,ld)
In this example there is two possible targets, requiring different In this example there are two possible targets, requiring different
options to the linker. the linker options are specified using the options to the linker. the linker options are specified using the
LDFLAGS_$@ syntax - one for each potential target. LDFLAGS_$@ syntax - one for each potential target.
$(targets) are assinged all potential targets, herby kbuild knows $(targets) are assinged all potential targets, herby kbuild knows
......
...@@ -38,7 +38,7 @@ ...@@ -38,7 +38,7 @@
* *
* The idea above dates, by the way, back to Michael E Chastain, AFAIK. * The idea above dates, by the way, back to Michael E Chastain, AFAIK.
* *
* So to get dependencies right, there two issues: * So to get dependencies right, there are two issues:
* o if any of the files the compiler read changed, we need to rebuild * o if any of the files the compiler read changed, we need to rebuild
* o if the command line given to the compile the file changed, we * o if the command line given to the compile the file changed, we
* better rebuild as well. * better rebuild as well.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment