| |
| |
NOTE: Problem solved, see below!
--------------------------------
On 9/17/20 1:38 PM duncan wrote:
I'm afraid that I don't have a Linux box at home under my own control, and
only a centrally managed CentOS 7.7 box at work which is quite old, where:
latex -v shows it's from the TeX Live 2013 distribution (but I found
it's broken)
Mine is:
$ latex -v
pdfTeX 3.14159265-2.6-1.40.20 (TeX Live 2019/Debian)
...
doxygen -v shows 1.8.5
cmake --version shows 2.8.12.2
After installingTeX Live 2020 and cmake 3.18.2 I was able to build the
current fltk-1.4.x documentation, both html and pdf with doxygen 1.8.5
So partial success at this point
Thanks for your help, I appreciate that you took the time to do all
this. BTW, sorry for the late reply, I've been busy with other stuff today.
I cloned the doxygen git repository and checked out 1.8.15, which should
have worked, if your experience is anything to go by,
Yes, I could indeed build doxygen 1.8.15 using cmake 3.16.3 and it
worked (with our old header file, see below for more info).
but I got a warning
and/or error message when trying to build it, which might be significant:
...
But when I then tried to build fltk-1.4.x using the DOXYGEN_EXECUTABLE
parameter to cmake, the build fails with the following, but this might be
because I also need to update quite a few other support packages too :-(
Again, thanks a lot... (more error messages elided)
I'm afraid I don't have time to track this down while I'm at work, sorry.
I think it would make more sense to use a full distro where all packages
should already be compatible and test against each other, than to try
to continue on a piecemeal basis.
I agree. My idea (question) was more about whether someone had a newer
doxygen version (newer than 1.8.15) and *could* build the PDF docs, or -
if not - the second question would be if an older doxygen version (like
1.8.15) worked as it did for me. This should not only be an issue on
Linux but also on macOS (or Windows if anybody installed doxygen and
latex on Windows).
Anyway, thanks for all your work. I *just* found the cause (but not yet
a complete solution):
I had a faint recollection that a previous issue with similar negative
results was caused by our doxygen pdf/latex header file
'fltk-book.tex.in' which can be (re)created partially by doxygen. This
header file contains (obviously necessary) LaTeX code which *is*
{doxygen + latex} version dependent, i.e. the header file appears to
define some latex code (macros, commands?) used in the latex code
generated by doxygen to build the pdf docs.
Consequently I regenerated the latex header file [1], merged it with our
existing 'fltk-book.tex.in', et voilà: it worked. I can now generate
FLTK pdf docs with my upgraded Linux box and its default doxygen version
(1.8.17).
To do: the next problem will be to find out how to integrate this with
our sources so devs with older doxygen/latex versions can still generate
the pdf docs. But that's something I can do myself later.
-----
[1] see doxygen docs (man doxygen):
$ doxygen -w latex headerFile footerFile styleSheetFile
Then merge 'headerFile' with 'fltk-book.tex.in' keeping our own title
and FLTK specific header parts. Attached file fltk-book.diff is a
working patch for now.
--
You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkcoredev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/211cae5d-095e-453b-c0f0-5c6ad6d6880c%40online.de.
[ Direct Link to Message ] | |
|
| |
