Hello,
We use a customized version of doxygen to read C++ source (and
doxyfiles) and translate it into the equivalent code for perl, python,
ruby, and tcl. Why? Because we use swig to generate modules and
wrapper libraries extending a suite of database libraries. Our
customized version of doxygen filters and modifies the syntax from the
C++ source substituting the specific scripting language syntax and data
types.
Our issue is we need to migrate from the doxygen-1.8.7 version to the
doxygen-1.8.20 version. A lot has happened between the two and I don't
have a map to translate from the old methods to the new. I have
migrated our custom code from the old configure environment to the cmake
environment, but I get about a dozen errors for methods that no longer
exist. How can I map the old to the new?
Alternatively, can anyone suggest a better way to map the C++
documentation without using a customized version of doxygen?
Thanks,
Matthew
--
Matthew Wheaton
Silicon Integration Initiative
Senior Programmer
12335 Hymeadow Drive, Suite 450
Austin, TX 78750
mw...@si...
512-745-7810
www.si2.org
|
