fpdoc.1 5.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173
  1. .TH fpdoc 1 "9 march 2002" "Free Pascal" "Free Pascal unit documentation generator"
  2. .SH NAME
  3. fpdoc \- The FPC Pascal unit documentation generator.
  4. .SH SYNOPSIS
  5. \fBfpdoc\fP --input=inputcommand [--output=output] [--format=fmt]
  6. [--descr=descriptionfile] [--show-private] [--hide-protected]
  7. [--lang=language] [--content=contentfile] [--import=importfile]
  8. [--package=packagename] [--html-search=searchpage] [--ostarget=target]
  9. [--cpu-target=target] [--latex-extension=ext] [--latex-highlight]
  10. .SH Description
  11. .B fpdoc
  12. scans a Free Pascal unit source file and generates documentation for it.
  13. The documentation can be in various formats (currently HTML and LaTeX)
  14. It can read various description files which contain the description for the
  15. various symbols found in the unit file.
  16. .SH Usage
  17. You can invoke
  18. .B fpdoc
  19. with as the only required argument the 'input' and 'package' arguments.
  20. It should at least contain the name of the unit file for which
  21. documentation should be generated and the name of the package to which the
  22. unit belongs.
  23. .SH Options
  24. .B fpdoc
  25. has several options, most of them optional, defaults will be used in most
  26. cases.
  27. .TP
  28. .BI \-\-content
  29. This option tells
  30. .B fpdoc
  31. to generate a content file. A content file contains a list of all the
  32. possible anchors (labels) in the generated documentation file, and can be
  33. used to create cross-links in documentation for different units, using the
  34. .B --import
  35. option.
  36. .TP
  37. .BI \-\-descr=descfile
  38. This option specifies the name of a description file
  39. .B descfile
  40. that contains the actual documentation for the unit.
  41. This option can be given several times, for several description files.
  42. .TP
  43. .BI \-\-format=fmt
  44. Specifies the format
  45. .B fmt
  46. in which the documentation will be generated. Currenly,
  47. the following formats are known:
  48. .RS
  49. .TP
  50. .I htm
  51. HTML with 8.3 conforming filenames.
  52. .TP
  53. .I html
  54. HTML with long filenames.
  55. .TP
  56. .I xhtml
  57. XHTML with long filesnames.
  58. .TP
  59. .I latex
  60. LaTex, which uses the fpc.sty style used by the Free Pascal documentation.
  61. .TP
  62. .I xml-struct
  63. Structured XML.
  64. .RE
  65. .TP
  66. .BI \-\-hide\-protected
  67. By default, the documentation will include descriptions and listings of
  68. protected fields and methods in classes or objects. This option changes this
  69. behaviour; if it is specified, no documentation will be generated for these
  70. methods. Note that public methods or properties that refer to these
  71. protected method will then have a dangling (i.e. unavailable) link.
  72. .TP
  73. .BI \-\-html\-search=link
  74. Adds an entry for an HTML search page at location
  75. .B link
  76. in the headers of the generated HTML pages. There is no search page
  77. provided, this should be made and provided by the user.
  78. .TP
  79. .BI \-\-import=impfile
  80. imports a content file
  81. .B impfile
  82. from another documentation set. This can be used to
  83. resolve references to elements within this other documentation file;
  84. .TP
  85. .B \-\-input=cmd
  86. This option tells
  87. .B fpdoc
  88. what input file should be used. The argument
  89. .B cmd
  90. can be just a filename, but can
  91. also be a complete compiler command-line with options that concern the
  92. scanning of the pascal source: defines, include files, syntax options,
  93. as they would be specified to the free pascal compiler when compiling
  94. the file. If a complete command is used, then it should be enclosed in
  95. single or double quotes, so the shell will not break them in parts.
  96. It is possible to specify multiple input commands; they will be treated one
  97. by one, and documentation will be generated for each of them.
  98. .TP
  99. .BI \-\-lang=language
  100. Sets the language for the output file. This will mainly set the strings used
  101. for the headers in various parts of the documentation files (by default
  102. they're in english). Currently, valid options are
  103. .RS
  104. .TP
  105. .I de
  106. German.
  107. .TP
  108. .I fr
  109. French.
  110. .TP
  111. .I nl
  112. Dutch.
  113. .RE
  114. .TP
  115. .BI \-\-latex\-extension=ext
  116. Sets the extension to use for the LaTeX file to
  117. .I ext
  118. the default is
  119. .BI .tex
  120. (with . (dot) included).
  121. .TP
  122. .BI \-\-latex\-highlight
  123. Switches on an internal latex syntax highlighter. This is not yet
  124. implemented. By default, syntax highlighting is provided by the syntax
  125. package that comes with fpc.
  126. .TP
  127. .BI \-\-output=name
  128. This option tells
  129. .B fpdoc
  130. where the output file should be generated. How this option is interpreted
  131. depends on the format that is used. For latex,
  132. .B name
  133. is interpreted as the
  134. filename for the tex file. For all other formats,
  135. .B name
  136. is interpreted as
  137. the directory where all documentation files will be written. The directory
  138. will be created if it does not yet exist. Standard this equals the package
  139. name.
  140. .TP
  141. .BI \-\-package=packagename
  142. Specifies the package name. All units will be documented as part of
  143. .I packagename
  144. , which is also the default output filename or directory. Only documentation
  145. nodes inside a package node with this name will be considered when
  146. documenting.
  147. .TP
  148. .BI \-\-show\-private
  149. By default, no documentation is generated for private methods or fields.
  150. This option causes
  151. .B fpdoc
  152. to generate documentation for these methods as well.
  153. .TP
  154. .BI \-\-warn\-no\-node
  155. If this option is specified,
  156. .B fpdoc
  157. will emit a warning if it does not find a description node for an identifier
  158. it is documenting.
  159. .SH SEE ALSO
  160. .IP
  161. .BR ppc386 (1)
  162. .BR latex (1)
  163. .BR makeskel (1)