Reinier Olislagers schrieb:
Trying out FPDocManager.
Thanks for trying out, and for all your feedback :-)
Have somme comments/questions - sorry if these have been raised before: 1. What is the "common documentation directory" you are asked to select when starting it for the first time? Does it contain your sources? Compiled documentation? Would be nice if there were a bit more description. (Probably is the "root directory" in the config assistant. Ok.)
Sorry for the confusion :-( [Please suggest the most descriptive name for it] Yes, that directory will hold all FPDoc output and the config files for the manager itself. It can be initally empty.
2. Configuration assistant: good idea! 2nd tab, FPC: "Now select the FPC source directory and the FPC documentation directory in it" Assuming that means the fpcdocs SVN repository I keep fpcdocs separate as I have multiple fpc installs. Is it required to have fpcdocs under your FPC directory?
No, that's why you have to tell the manager where that directory is.
3. RTL step: noticed you need to create 2 Windows batch files. Wouldn't it be more useful if there were some cross platform way of generating the rtl etc docs (e.g. shelling out to fpdoc with parameters like lazbuild is doing right now?)
These files can be omitted as soon as somebody explains how to use the FPCDocs Makefile to *only* create the FPDoc projects.
4. Trying to select the newly generated rtl.bat gives an access violation (Lazarus SVN 36494, FPC SVN 20683 x86). Any fix for that?
That looks like a bug in the Makefile and/or FPDoc. Does the AV also occur when you invoke "make ..." directly, without generating the batch file? The Makefile is designed on/for Linux, with possible problems on other platforms. Is it related to Mantis 0021148? (still open, no response) FPDoc showed a strange behaviour with duplicate paths and options, as may be inserted by the Makefile. If this is the reason of the AV, I'll have to supply an according patch for FPDoc. It's already known that "touch" is not normally available on Windows, and the CSS file didn't (still doesn't?) exist and consequently cannot be copied. These lines should be removed from the batch file, but they never should cause an AV. DoDi -- _______________________________________________ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
