Changes between Version 9 and Version 10 of BuildSystem
- Timestamp:
- Nov 26, 2009, 5:45:02 PM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BuildSystem
v9 v10 123 123 `default value`:: 124 124 Set the token default value. `defined` and `undefined` values act as booleans. 125 `depend TOKEN […]`:: 126 Dependencies, having at least one of the tokens on the line is required, if unsatisfied the current token gets undefined and a warning is emitted. May be used to disable features because of missing prerequisites. 125 127 `parent TOKEN`:: 126 Parent token in help screen. This is only for pretty-printing and allow hidding unrelevant tokensif the parent token is undefined.128 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 unrelevant tokens from the help screen if the parent token is undefined. 127 129 `require TOKEN […]`:: 128 130 Mandatory requirements, having at least one of the tokens on the line is mandatory, conflict yields error. May be usd to enforce definition of some mandatory configuration values. 129 `depend TOKEN […]`::130 Dependencies, having at least one of the tokens on the line is mandatory, conflict implicitly undefines the current token. May be used to disable features because of missing prerequisites.131 131 `provide TOKEN […]`:: 132 132 Defining the current token enforce definition of the specified token.