putty-source/doc/chmextra.but

\# If you want to do a Halibut build of the CHM file by hand, without
\# the help of the CMake edifice, then include this file which will
\# refer to chm.css. The CMake edifice builds its own with a different
\# pathname in it, for the sake of out-of-tree builds.

\cfg{chm-extra-file}{chm.css}
Integrate the 'doc' subdir into the CMake system. The standalone separate doc/Makefile is gone, replaced by a CMakeLists.txt that makes 'doc' function as a subdirectory of the main CMake build system. This auto-detects Halibut, and if it's present, uses it to build the man pages and the various forms of the main manual, including the Windows CHM help file in particular. One awkward thing I had to do was to move just one config directive in blurb.but into its own file: the one that cites a relative path to the stylesheet file to put into the CHM. CMake builds often like to be out-of-tree, so there's no longer a fixed relative path between the build directory and chm.css. And Halibut has no concept of an include path to search for files cited by other files, so I can't fix that with an -I option on the Halibut command line. So I moved that single config directive into its own file, and had CMake write out a custom version of that file in the build directory citing the right path. (Perhaps in the longer term I should fix that omission in Halibut; out-of-tree friendliness seems like a useful feature. But even if I do, I still need this build to work now.) 2021-05-02 14:34:57 +00:00			`\# If you want to do a Halibut build of the CHM file by hand, without`
			`\# the help of the CMake edifice, then include this file which will`
			`\# refer to chm.css. The CMake edifice builds its own with a different`
			`\# pathname in it, for the sake of out-of-tree builds.`

			`\cfg{chm-extra-file}{chm.css}`