11 | | - User manual: we write it in simple HTML, storing the manual in a |
12 | | file '<module>.html' within the subdirectory of the module. |
13 | | The file contains no header nor footer. The complete HTML file is |
14 | | autogenerated during the compilation process (indeed, it is generated |
15 | | in a virtual session directly after compilation of the module). |
16 | | In this virtual session the module is called internally with |
17 | | --html-description which generates the parameters/flags list in |
18 | | HTML format, along with '<module>.html', HTML header and footer |
19 | | the final HTML manual page is created and stored in the target |
20 | | binaries directory. In a separate process the MAN format is |
21 | | generated from the complete HTML files. |
| 10 | - User manual: we write it in simple HTML, storing the manual in a file '<module>.html' within the subdirectory of the module. The file contains no header nor footer. The complete HTML file is autogenerated during the compilation process (indeed, it is generated in a virtual session directly after compilation of the module). In this virtual session the module is called internally with --html-description which generates the parameters/flags list in HTML format, along with '<module>.html', HTML header and footer the final HTML manual page is created and stored in the target binaries directory. In a separate process, the MAN format is generated from the complete HTML files. |