From: Dylan Trotter (trotterdylan_at_[hidden])
Date: 2005-08-23 11:24:31
I'm having problems getting the Doxygen toolset to work with
Boost.Build. First off, I'm running Windows XP, VC7.1 and Boost 1.33.
The first problem is that the filenames specified in the INPUT of the
.doxyfile aren't enclosed in quotes. This is a problem in general, since
it's not an unlikely situation. I fixed this in the doxygen.jam file in
The next problem was that the doxygen.xml.dir --stringparam argument to
xsltproc also wasn't enclosed in quotes. I changed this in xsltproc.jam
because the parameter should generally be enclosed in quotes.
Finally, the problem I'm experiencing now, and have been unable to fix
so far is that xsltproc doesn't execute as might be expected. When I
execute bjam, there is no apparent problem, I suspect because xsltproc
is only issuing warnings and not returning an error value. But the big
.doxygen file that's supposed to be generated is nearly empty. The
warnings are something like (apologies, I'm at work now and can't
remember the exact warnings) "can't find
Apparently, xsltproc assumes that the included Doxygen-generated xml
files are in the same directory as the .xsl file. Why? I'm not sure. I
would expect it to look from the current directory (e.g. "./xml").
I messed around with it for a while and got it to compile the monolithic
.doxygen file by moving the .xsl file into the current directory and
ommitting the --stringparam argument. I suspect, however, there is a
better way. So here are a few questions:
1) Does anyone know why xsltproc would run in this way?
2) What's the purpose of the doxygen.xml.dir --stringparam passed in to
3) Has anyone else experienced these problems and found a workaround
without hacking the jam sources?
Thanks for your time,
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk