fpdoc.1 5.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172
  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 files,ames.
  58. .TP
  59. .I latex
  60. LaTex, which uses the fpc.sty style used by the Free Pascal documentation.
  61. .TP xml-struct
  62. Structured XML.
  63. .RE
  64. .TP
  65. .BI \-\-hide\-protected
  66. By default, the documentation will include descriptions and listings of
  67. protected fields and methods in classes or objects. This option changes this
  68. behaviour; if it is specified, no documentation will be generated for these
  69. methods. Note that public methods or properties that refer to these
  70. protected method will then have a dangling (i.e. unavailable) link.
  71. .TP
  72. .BI \-\-html\-search=link
  73. Adds an entry for an HTML search page at location
  74. .B link
  75. in the headers of the generated HTML pages. There is no search page
  76. provided, this should be made and provided by the user.
  77. .TP
  78. .BI \-\-import=impfile
  79. imports a content file
  80. .B impfile
  81. from another documentation set. This can be used to
  82. resolve references to elements within this other documentation file;
  83. .TP
  84. .B \-\-input=cmd
  85. This option tells
  86. .B fpdoc
  87. what input file should be used. The argument
  88. .B cmd
  89. can be just a filename, but can
  90. also be a complete compiler command-line with options that concern the
  91. scanning of the pascal source: defines, include files, syntax options,
  92. as they would be specified to the free pascal compiler when compiling
  93. the file. If a complete command is used, then it should be enclosed in
  94. single or double quotes, so the shell will not break them in parts.
  95. It is possible to specify multiple input commands; they will be treated one
  96. by one, and documentation will be generated for each of them.
  97. .TP
  98. .BI \-\-lang=language
  99. Sets the language for the output file. This will mainly set the strings used
  100. for the headers in various parts of the documentation files (by default
  101. they're in english). Currently, valid options are
  102. .RS
  103. .TP
  104. .I de
  105. German.
  106. .TP
  107. .I fr
  108. French.
  109. .TP
  110. .I nl
  111. Dutch.
  112. .RE
  113. .TP
  114. .BI \-\-latex\-extension=ext
  115. Sets the extension to use for the LaTeX file to
  116. .I ext
  117. the default is
  118. .BI .tex
  119. (with . (dot) included).
  120. .TP
  121. .BI \-\-latex\-highlight
  122. Switches on an internam latex syntax highlighter. This is not yet
  123. implemented. By default, syntax highlighting is provided by the syntax
  124. package that comes with fpc.
  125. .TP
  126. .BI \-\-output=name
  127. This option tells
  128. .B fpdoc
  129. where the output file should be generated. How this option is interpreted
  130. depends on the format that is used. For latex,
  131. .B name
  132. is interpreted as the
  133. filename for the tex file. For all other formats,
  134. .B name
  135. is interpreted as
  136. the directory where all documentation files will be written. The directory
  137. will be created if it does not yet exist. Standard this equals the package
  138. name.
  139. .TP
  140. .BI \-\-package=packagename
  141. Specifies the package name. All units will be documented as part of
  142. .I packagename
  143. , which is also the default output filename or directory. Only documentation
  144. nodes inside a package node with this name will be considered when
  145. documenting.
  146. .TP
  147. .BI \-\-show\-private
  148. By default, no documentation is generated for private methods or fields.
  149. This option causes
  150. .B fpdoc
  151. to generate documentation for these methods as well.
  152. .TP
  153. .BI \-\-warn\-no\-node
  154. If this option is specified,
  155. .B fpdoc
  156. will emit a warning if it does not find a description node for an identifier
  157. it is documenting.
  158. .SH SEE ALSO
  159. .IP
  160. .BR ppc386 (1)
  161. .BR latex (1)
  162. .BR makeskel (1)