On 2-4-2012 9:43, Hans-Peter Diettrich wrote: > Reinier Olislagers schrieb: >> On 1-4-2012 18:28, Hans-Peter Diettrich wrote: >>> Reinier Olislagers schrieb: >>>> Is it required to have fpcdocs under your FPC directory? > > Correction: you are right, according to the FPDoc documentation fpcdocs > must reside inside a FPC source directory, so that the Makefile can find > the units. Hmmm... Where did you find that? I know it's at least the easiest option, but IIRC, you can use things like the FPCSRCDIR environment variable and css-file command line option to tweak things.
Having the structure is how I currently have my directories set up; I think I'll try and make that work if possible: c:\development | +-extras | +-fpcdocs | +-synapse | +-tiopf | +-... +-fpctrunk +-fpcfixes26 +-.... +-lazarusfpctrunk +-lazarusfpctrunkx64 +-lazarusfixes26 +-.... >>>> 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. >> Not going there... make files are not my forte at all.. > Me2 :-( Wondering how you are going to make that work for Linux/other OS... Perhaps you could create the batch/shell files from within fpdoc manager using TProcess.Execute? >>>> 4. Trying to select the newly generated rtl.bat gives an access >>>> violation (Lazarus SVN 36494, FPC SVN 20683 x86). Any fix for that? > > You're right, I could reproduce and fix this bug :-) > Please update and try again. Ok. -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
