Changes between Version 17 and Version 18 of BuildSystem

Timestamp:

Mar 8, 2010, 7:29:21 PM (14 years ago)

Author:

becoulet

Comment:

--

BuildSystem

@@ -4 +4 @@
 = Overview of the build process =
 
-The build system use one or more used defined *build configuration files* to compiles the desired kernel together with the application.
-
-The build system takes care of features dependencies, file modifications, ... And is still simple to use for the beginner.
-Available features, tweakable values and associated constraints are represented by *configuration tokens* and described by developers through *configuration description files* (.config) in the source tree.
+The build system use one or more used defined '''build configuration files''' to compiles the desired kernel together with the application.
+
+The build system takes care of features dependencies, file modifications, ... but is still simple to use for the beginner.
+Available features, tweakable values and associated constraints are represented by '''configuration tokens'''
+and described by developers through '''configuration description files''' (.config) in the source tree.
 
 Depending on the target architecture, the binary output file may be an ELF (.out), a plain binary file (.bin), an intel-hex file (.hex) or an object file (.o).
@@ -243 +244 @@
    Set some flags with special meaning for the token.
  `parent TOKEN`::
-   Hierarchical dependency, it ensures all token with a parent gets silently undefined if the parent is undefined. This prevents options enabled by default to stay enabled if the parent is disabled; this way it avoids errors due to unneeded requirements. This is also used to hide irrelevant tokens from the help screen if the parent token is undefined. Tokens with no parent must have the `root` flag set.
+   Hierarchical dependency, it ensures all token with a parent gets silently undefined if the parent is undefined. This prevents options enabled by default to stay enabled if the parent is disabled; this way it avoids errors due to unneeded requirements. This is also used to hide irrelevant tokens from the help screen if the parent token is undefined. Tokens with no parent must have the `root` flag set or use the `module` tag.
  `default value`::
    Set the token default value. `defined` and `undefined` values act as booleans. default value is `undefined` if this line is omitted.