FPC trunk, Lazarus trunk, Windows

Tried to fix fpcup not generating LCL chm docs.
It uses build_lcl_docs.exe to do that.

Found out that fpdoc is complaining about a missing .css file: Writing 19901 pages...
Exception at 00441644: Exception:
Can't find CSS file "..\fpdoc.css".
306 Warnings hidden. Use --warnings to see them all.

Fiddled with the --arg options like this to pass the path cd C:\Development\lazarus\docs\chm
C:\development\lazarus\docs\html\build_lcl_docs.exe "--fpcdocs" "C:\development\lazarus\docs\chm\" "--fpdoc"
"C:\development\fpctrunk\bin\i386-win32\fpdoc.exe" "--arg css-file=C:\development\fpctrunk\utils\fpdoc\fpdoc.css " "--outfmt" "chm" gives this error message from fpdoc
Ignoring unknown option
"css-file=C:\development\fpctrunk\utils\fpdoc\fpdoc.css"

.. but same error
doing this
"--arg --css-file=C:\development\fpctrunk\utils\fpdoc\fpdoc.css" doesn't help either.

Any suggestions [1]?
Has anybody gotten build_lcl_docs to work?

Thanks,
Reinier

[1] I remember having a big discussion on fpc about where to place .css files; apparently the way things are now are as they should be so I'm not really interested in any fixes that involve changing the fpdoc source code/fpc directory layout.

i notice the above has a trailing space after fpdoc.css...

maybe just one dash?

-css-file=blah

does the build_lcl_docs.exe give any hints or --help?

I typically use build_lcl_html.sh. IIRC I played with chm_docs too last time, and that worked.

[1] I remember having a big discussion on fpc about where to place .css files; apparently the way things are now are as they should be so I'm not really interested in any fixes that involve changing the fpdoc source code/fpc directory layout.

The fpcdoc repository makefile has support for it there. The html is afaik generated with a path to the root of the CHM file, and the --css-file param places it there. So maybe that is about html, and not CHM.

waldo kitty wrote

On 8/2/2013 07:23, Reinier Olislagers wrote: > FPC trunk, Lazarus trunk, Windows i notice the above has a trailing space after fpdoc.css...

Yes, so did I. If it isn't there, fpdoc barfs with an unrecognized options error.

Why? the option is two dashes if you directly call fpdoc

does the build_lcl_docs.exe give any hints or --help?

Do you really think I didn't look there first?

interesting...

i didn't try... perhaps it is the ordering of the parameters fed to that executable? it shouldn't be but stranger things have been seen...

> does the build_lcl_docs.exe give any hints or --help? Do you really think I didn't look there first?

hehehe... i didn't know if you had or not so i asked the obvious question ;)

waldo kitty wrote

On 8/2/2013 07:23, Reinier Olislagers wrote: does the build_lcl_docs.exe give any hints or --help?

Well, waldo, your crystal ball worked ;)

Had another look at the build_lcl_docs source code and found a hardcoded --css-file value that probably is no longer valid because of changed fpc directory layout.

Wrote and tested a patch that allows you to specify a parameter to override the default.

http://bugs.freepascal.org/view.php?id=24823

Thanks,
Reinier