Details
Details
- Reviewers
wblock bcr - Group Reviewers
Doc Committers - Commits
- rD50190: Add a section about the order the variables must come in a Makefile.
Diff Detail
Diff Detail
- Lint
No Lint Coverage - Unit
No Test Coverage - Build Status
Buildable 8455 Build 8752: arc lint + arc unit
Event Timeline
en_US.ISO8859-1/books/porters-handbook/porting-samplem/chapter.xml | ||
---|---|---|
103 | s/Ports/Port/ | |
105 | The first sections of the <filename>Makefile</filename> | |
106 | This standard makes it so everyone | |
107 | can easily read any port without having to search for variables in a random order. | |
110 | <para>The first line of a <filename>Makefile</filename> is always | |
112 | s/RCS ID/VCS ID/ actually, `version control ID``` is probably clearer. s/will look/looks/ | |
119 | has expanded it to look like this:</para> | |
125 | s/only// | |
126 | s/normal/ordinary/ | |
134 | In the following blocks, only set the variables that are required by the port. Define these variables in the order they are shown here.</para> | |
142 | Comma splice. <para>This block is the most important. It defines the port | |
143 | name, version, distribution file location, and category. The | |
144 | variables must be in this order:</para> | |
266 | Better off without a count of variables to get out of sync: <para>This block is mandatory. The variables are:</para> | |
284 | s/thought/although it is/ | |
343 | s/by/variables by/ | |
397 | "Always" is not necessary, make it imperative: <para>Keep related variables close together. For example, | |
433 | the same order as the different stages run:</para> |