doxygen_manual-1.8.1 (Методичка, задание и документация на ЛР №7), страница 5

If you compile graphvizyourself, make sure you do include freetype support (which requires the freetype library and header files),otherwise the graphs will not render proper text labels.• For formulas or if you do not wish to use pdflatex, the ghostscript interpreter is needed. You can find it atwww.ghostscript.com.• In order to generate doxygen’s own documentation, Python is needed, you can find it at www.python.org.Compilation is now done by performing the following steps:1.

Unpack the archive, unless you already have done that:gunzip doxygen-$VERSION.src.tar.gztar xf doxygen-$VERSION.src.tar# uncompress the archive# unpack it2. Run the configure script:sh ./configureThe script tries to determine the platform you use, the make tool (which must be GNU make) and the perlinterpreter. It will report what it finds.To override the auto detected platform and compiler you can run configure as follows:8Installationconfigure –platform platform-typeSee the PLATFORMS file for a list of possible platform options.If you have Qt-4.3 or higher installed and want to build the GUI front-end, you should run the configure scriptwith the -with-doxywizard option:configure –with-doxywizardFor an overview of other configuration options useconfigure –help3.

Compile the program by running make:makeThe program should compile without problems and the binaries (doxygen and optionally doxywizard)should be available in the bin directory of the distribution.4. Optional: Generate the user manual.make docsTo let doxygen generate the HTML documentation.The HTML directory of the distribution will now contain the html documentation (just point a HTML browser tothe file index.html in the html directory). You will need the python interpreter for this.5.

Optional: Generate a PDF version of the manual (you will need pdflatex, makeindex, and egrep forthis).make pdfThe PDF manual doxygen_manual.pdf will be located in the latex directory of the distribution. Just viewand print it via the acrobat reader.1.2Installing the binaries on UNIXAfter the compilation of the source code do a make install to install doxygen. If you downloaded the binarydistribution for UNIX, type:./configuremake installBinaries are installed into the directory <prefix>/bin. Use make install_docs to install the documentation and examples into <docdir>/doxygen.<prefix> defaults to /usr/local but can be changed with the -prefix option of the configure script.

Thedefault <docdir> directory is <prefix>/share/doc/packages and can be changed with the -docdiroption of the configure script.Alternatively, you can also copy the binaries from the bin directory manually to some bin directory in your searchpath. This is sufficient to use doxygen.NoteYou need the GNU install tool for this to work (it is part of the coreutils package). Other install tools may put thebinaries in the wrong directory!If you have a RPM or DEP package, then please follow the standard installation procedure that is required for thesepackages.Generated by Doxygen1.3 Known compilation problems for UNIX1.39Known compilation problems for UNIXQt problemsThe Qt include files and libraries are not a subdirectory of the directory pointed to by QTDIR on some systems (forinstance on Red Hat 6.0 includes are in /usr/include/qt and libs are in /usr/lib).The solution: go to the root of the doxygen distribution and do:mkdir qtcd qtln -s your-qt-include-dir-here includeln -s your-qt-lib-dir-here libln -s your-qt-bin-dir-here binexport QTDIR=$PWDIf you have a csh-like shell you should use setenv QTDIR $PWD instead of the export command above.Now install doxygen as described above.Bison problemsVersions 1.31 to 1.34 of bison contain a "bug" that results in a compiler errors like this:ce_parse.cpp:348: member ‘class CPPValue yyalloc::yyvs’ with constructor not allowed in unionThis problem has been solved in version 1.35 (versions before 1.31 will also work).Latex problemsThe file a4wide.sty is not available for all distributions.

If your distribution does not have it please select anotherpaper type in the config file (see the PAPER_TYPE tag in the config file).HP-UX & Digital UNIX problemsIf you are compiling for HP-UX with aCC and you get this error:/opt/aCC/lbin/ld: Unsatisfied symbols:alloca (code)then you should (according to Anke Selig) edit ce_parse.cpp and replaceextern "C" {void *alloca (unsigned int);};with#include <alloca.h>If that does not help, try removing ce_parse.cpp and let bison rebuild it (this worked for me).If you are compiling for Digital UNIX, the same problem can be solved (according to Barnard Schmallhof) by replacing the following in ce_parse.cpp:#else /* not GNU C. */#if (!defined (__STDC__) && defined (sparc)) || defined (__sparc__) \|| defined (__sparc) || defined (__sgi)#include <alloca.h>with#else /* not GNU C.

*/#if (!defined (__STDC__) && defined (sparc)) || defined (__sparc__) \|| defined (__sparc) || defined (__sgi) || defined (__osf__)#include <alloca.h>Alternatively, one could fix the problem at the bison side. Here is patch for bison.simple (provided by AndreJohansen):Generated by Doxygen10Installation--- bison.simple~Tue Nov 18 11:45:53 1997+++ bison.simpleMon Jan 26 15:10:26 1998@@ -27,7 +27,7 @@#ifdef __GNUC__#define alloca __builtin_alloca#else /* not GNU C. */-#if (!defined (__STDC__) && defined (sparc)) || defined (__sparc__) \|| defined (__sparc) || defined (__sgi)+#if (!defined (__STDC__) && defined (sparc)) || defined (__sparc__) \|| defined (__sparc) || defined (__sgi) || defined (__alpha)#include <alloca.h>#else /* not sparc */#if defined (MSDOS) && !defined (__TURBOC__)The generated scanner.cpp that comes with doxygen is build with this patch applied.Sun compiler problemsIt appears that doxygen doesn’t work properly if it is compiled with Sun’s C++ WorkShop 6 Compiler.

I cannot verifythis myself as I do not have access to a Solaris machine with this compiler. With GNU compiler it does work andinstalling Sun patch 111679-13 has also been reported as a way to fix the problem.when configuring with -static I got:Undefinedsymboldlclosedlsymdlopenfirst referencedin file/usr/lib/libc.a(nss_deffinder.o)/usr/lib/libc.a(nss_deffinder.o)/usr/lib/libc.a(nss_deffinder.o)Manually adding -Bdynamic after the target rule in Makefile.doxygen will fix this:$(TARGET): $(OBJECTS) $(OBJMOC)$(LINK) $(LFLAGS) -o $(TARGET) $(OBJECTS) $(OBJMOC) $(LIBS) -BdynamicGCC compiler problemsOlder versions of the GNU compiler have problems with constant strings containing characters with character codeslarger than 127. Therefore the compiler will fail to compile some of the translator_xx.h files. A workaround, if youare planning to use the English translation only, is to configure doxygen with the -english-only option.On some platforms (such as OpenBSD) using some versions of gcc with -O2 can lead to eating all memory duringthe compilation of files such as config.cpp.

As a workaround use –debug as a configure option or omit the -O2 forthe particular files in the Makefile.Gcc versions before 2.95 may produce broken binaries due to bugs in these compilers.Dot problemsDue to a change in the way image maps are generated, older versions of doxygen (<=1.2.17) will not work correctlywith newer versions of graphviz (>=1.8.8). The effect of this incompatibility is that generated graphs in HTML arenot properly clickable. For doxygen 1.3 it is recommended to use at least graphviz 1.8.10 or higher.

For doxygen1.4.7 or higher it is recommended to use GraphViz 2.8 or higher to avoid font issues.Red Hat 9.0 problemsIf you get the following error after running maketmake error: qtools.pro:70: Syntax errorthen first typeexport LANG=before running make.Generated by Doxygen1.4 Compiling from source on Windows1.411Compiling from source on WindowsFrom version 1.7.0 onwards, build files are provided for Visual Studio 2008.

Also the free (as in beer) "Express"version of Developer Studio can be used to compile doxygen. Alternatively, you can compile doxygen the UNIX wayusing Cygwin or MinGW.The next step is to install unxutils (see http://sourceforge.net/projects/unxutils). This packagescontains the tools flex and bison which are needed during the compilation process if you use a CVS snapshotof doxygen (the official source releases come with pre-generated sources). Download the zip extract it to e.g.c:\tools\unxutils.Now you need to add/adjust the following environment variables (via Control Panel/System/Advanced/EnvironmentVariables):• add c:\tools\unxutils\usr\local\wbin; to the start of PATH• set BISON_SIMPLE to c:\tools\unxutils\usr\local\share\bison.simpleDownload doxygen’s source tarball and put it somewhere (e.g.