Forum > Documentation (Maintaining -)
FPC(fixes)+lazarus(trunk) CHM doc snapshot beta
marcov:
I did a rehearsal for FPC release building, and uploaded the results to the usual site:
http://www.stack.nl/~marcov/doc-chmbeta.zip
FPC is fixes3.2, lazarus is from trunk (as of today), and the used fpdoc is from fixes, as the trunk fpdoc seems to segfault (which I assume Don already noticed in July, from comments in build_chm.sh)
Also I can't get latex to compile it anymore on Windows, probably due to the docs restructure and maybe newer latex snapshots. Compiling a file with path\filename seems to not work (with either / or \)
dsiders:
--- Quote from: marcov on December 23, 2023, 02:35:06 pm ---I did a rehearsal for FPC release building, and uploaded the results to the usual site:
http://www.stack.nl/~marcov/doc-chmbeta.zip
--- End quote ---
Nice. Internal links to identifiers with dotted unit namespaces seem to be working well.
--- Quote from: marcov on December 23, 2023, 02:35:06 pm ---FPC is fixes3.2, lazarus is from trunk (as of today), and the used fpdoc is from fixes, as the trunk fpdoc seems to segfault (which I assume Don already noticed in July, from comments in build_chm.sh)
--- End quote ---
You are correct. I've tried a couple of FPC trunk builds since then... with no change.
dsiders:
--- Quote from: dsiders on December 24, 2023, 12:45:07 am ---Nice. Internal links to identifiers with dotted unit namespaces seem to be working well.
--- End quote ---
I stand corrected. It didn't pull in any of the content. Not for system.uitypes.TColor at least.
marcov:
I assume that support is in trunk. Fixes is still mostly 3.2.2 level I guess.
I also saw that the system.uitypes index had two unclickable entries for "string" and "String".
I tried yesterday to reproduce the crashing on windows compiling, but couldn't. It compiled fine.
Do those links work in the online version, and what link do you use to test?
dsiders:
--- Quote from: marcov on December 24, 2023, 11:37:42 am ---I assume that support is in trunk. Fixes is still mostly 3.2.2 level I guess.
--- End quote ---
I need to rebuild my FPC Trunk and try again. I haven't been tracking the 3.2 fixes branch... perhaps it's time to start.
--- Quote from: marcov on December 24, 2023, 11:37:42 am ---I also saw that the system.uitypes index had two unclickable entries for "string" and "String".
--- End quote ---
I noticed some of those for ordinal types like Word too.
--- Quote from: marcov on December 24, 2023, 11:37:42 am ---I tried yesterday to reproduce the crashing on windows compiling, but couldn't. It compiled fine.
--- End quote ---
My problem was a run-time error in the FPDOc output. At some point, it decided to spew binary content on the screen and stopped writing the help output. I'll try again and see what happens now.
--- Quote from: marcov on December 24, 2023, 11:37:42 am ---Do those links work in the online version, and what link do you use to test?
--- End quote ---
If you mean existing online versions at https://www.freepascal.org/docs.html... then No. system.uitypes is not icluded there.
I use any property defined as TColor to test, like TControl.Color.
https://lazarus-ccr.sourceforge.io/docs/lcl/controls/tcontrol.color.html
Clicking on the type in the source declaration or navigating between topics should ultimately take you to system.uitypes. It doesn't work in the link above.
I noticed that your beta did navigate to the topic, but it does not have the content for the "TColor" topic in the XML file as if it was not found. But that content exists in Trunk. I haven't looked at fixes yet.
I try my luck after rebuilding trunk and making a build for fixes.
Navigation
[0] Message Index
[#] Next page