[Doxygen-users] Customising doxgen into a toolchain

[Simon G. <sim...@at...>]

Hi folks,

I just spotted this little bug in the current (1.2.16) version:

$ doxygen -w latex header.tex
Error: option "-w html" does not have enough arguments

This message should refer to "-w latex". It appears that
one message is used for the html version (which should
have three file arguments) and the latex one which should
have two (though I only wanted the first one). Actually the
resultant header.tex didn`t work till I edited in some
lines from a real refman.tex:

\batchmode

at the top and:

\usepackage{times}
\ifx\pdfoutput\undefined
\usepackage[ps2pdf,
            pagebackref=3Dtrue,
            colorlinks=3Dtrue,
            linkcolor=3Dblue
           ]{hyperref}
\else
\usepackage[pdftex,
            pagebackref=3Dtrue,
            colorlinks=3Dtrue,
            linkcolor=3Dblue
           ]{hyperref}
\fi

right before:

\usepackage{doxygen}

but I guess the -w can't infer the need for
those lines without having a Doxyfile to
chew on. However this seems to point up
a weakness in the -w option documentation
in section 14 of the User Manual. If the user
wants PDF output the template will need
more tweaking, as suggested above.=20

A quick fix for the misleading message is
to change line 6741 of doxygen.cpp from

            err("Error: option \"-w html\" does not have enough arguments\n=
");

to=20
            err("Error: option \"-w\" does not have enough arguments\n");

The code for -w rtf is already correct in this respect.

I understand that the tweaked .tex file can be
specified in LATEX_HEADER, giving a custom
title page, but I'm not clear how the replacement
stylesheet gets automatically used, and at the
moment I'm copying it over the default one in
the script I use to automate cleanup of the
output directories, copying in of graphics
used in my HTML header, running the M$
Help Compiler and the 'make pdf' as well as
launching Doxygen itself:

=2E..
cp Sample.sty latex/doxygen.sty
cd latex
make pdf=20
=2E..

Is there an elegant way to do this? The
snag of a blind copy is that $date and
such is not updated in the .sty file. I also
wonder if anyone else producing MSDN
help has integrated the procedure to make
the help files visible to DevStudio (as
opposed to simply compiling them) into
a script. I aim to make documentation
updates part of the check-in procedure,
but I'm a few steps short of this at the
moment - though I guess these are steps
others may have trodden. I have asked
Metrowerks to automate integration into
CodeWarrior, too...

Thanks to Dimitri and all involved for the
work so far; I hope to have some more
substantial things to add once I get to
grips fully with what's there already.

Cheers

Simon Goodwin
Technology Programmer
Attention to Detail Ltd

--=20
Simon Goodwin <sim...@at...>


This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is privileged
and/or confidential. If the reader of this message is not the intended
recipient please notify us immediately and delete this e-mail from your
system. E-mail transmissions cannot be guaranteed to be secure or error
free and may contain viruses. We therefore do not accept liability for
any loss occasioned by any such errors, omissions or viruses in the
contents of this message.=20