README 3.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108
  1. README (documentation)
  2. ----------------------
  3. FLTK 1.3 (and higher) documentation is available in HTML and PDF format.
  4. The documentation must be generated in a separate step or downloaded
  5. from FLTK's software download pages. The documentation can also
  6. be accessed online.
  7. To read the docs after downloading or generating them, open the
  8. files:
  9. documentation/html/index.html
  10. documentation/fltk.pdf
  11. with your browser or PDF viewer, respectively.
  12. Online Documentation:
  13. ---------------------
  14. A documentation version is available online at the FLTK web site,
  15. along with the PDF version of the manual. The docs on the web site
  16. are usually somewhat older (latest release). Use this URL to find
  17. the current online documentation:
  18. http://www.fltk.org/documentation.php
  19. Documentation Download:
  20. -----------------------
  21. To download pre-generated docs, go to
  22. http://www.fltk.org/software.php
  23. and look for the files
  24. fltk-<version>-docs-html.tar.gz
  25. fltk-<version>-docs-pdf.tar.gz
  26. Extract the documentation tarballs into the same directory as you
  27. did with the source tarball.
  28. Generation of Documentation (common part):
  29. ------------------------------------------
  30. To generate the documentation yourself, you should have Doxygen
  31. version 1.5.7 or later (recommended version is 1.7.3 or later).
  32. To generate the PDF version you also need a current version of LaTeX.
  33. You can use the packages tetex (older) or texlive (current) if your
  34. distribution provides them. You may need to install additional fonts
  35. and other sub-packages for the PDF version to be generated correctly.
  36. Generation of Documentation with autoconf (configure) + make:
  37. -------------------------------------------------------------
  38. Use "make html" in the documentation directory to generate the HTML
  39. documentation, or "make pdf" to generate the PDF version. "make docs"
  40. generates both versions in one step (as would do "make clean html pdf").
  41. To read the HTML or PDF docs, see above.
  42. Generation of Documentation with CMake + make:
  43. ----------------------------------------------
  44. We assume that you use an out-of-source build as recommended.
  45. Documentation is not generated in a default build. You must set one or
  46. more CMake options using cmake-gui, ccmake, or cmake -DOPTION...
  47. These options are predefined to OFF and can be switched ON:
  48. - OPTION_BUILD_HTML_DOCUMENTATION:BOOL=OFF target: html
  49. - OPTION_BUILD_PDF_DOCUMENTATION:BOOL=OFF target: pdf
  50. - OPTION_INSTALL_HTML_DOCUMENTATION:BOOL=OFF
  51. - OPTION_INSTALL_PDF_DOCUMENTATION:BOOL=OFF
  52. If you switch one or both of the first two options ON, then the
  53. targets 'html' and/or 'pdf' are generated, respectively. Target 'docs'
  54. is added to generate both 'html' and 'pdf'. As said above, you need
  55. installed Doxygen and LaTeX software for this to work.
  56. Use "make html" in the root or documentation directory of the build tree
  57. to generate the HTML documentation, or "make pdf" to generate the PDF
  58. version. "make docs" generates both versions in one step (as would do
  59. "make clean html pdf").
  60. To read the HTML or PDF docs, see above, but use the build directory.
  61. Note: if you enable one or more of the "*INSTALL*" options, then
  62. `make install' will install the docs, but you must still build them
  63. manually, because the generation is not included in the standard ('all')
  64. target. This may be changed in the future.
  65. FLTK Developer Snapshots or Subversion Usage:
  66. ---------------------------------------------
  67. There is no pre-generated documentation available if you use a current
  68. developer snapshot or subversion. You must generate the documentation
  69. yourself or access the online documentation.
  70. Bugs and Feature Requests:
  71. --------------------------
  72. If you find any typos, things that are unclear, or would like to
  73. contribute an example, section, or chapter to the FLTK manual, please
  74. post a question in the fltk newsgroup fltk.general or post a bug
  75. report or feature request at:
  76. http://www.fltk.org/str.php