doxygen-users — List for users of doxygen

RE: [Doxygen-users] Latex problems

[Markus L. <lo...@ce...>]

Petr,
thanks for your very detailed answer. I'm not using any custom tex code.
I actually tried some other C++ files, and they work fine.
I will try to send Dimitri my example that doesn't work
Markus


> -----Original Message-----
> From: dox...@li...
> [mailto:dox...@li...]On Behalf Of
> Prikryl,Petr
> Sent: Wednesday, August 22, 2001 1:38 AM
> To: dox...@li...
> Subject: RE: [Doxygen-users] Latex problems
>
>
> You should focus on
> --------------------------
> Runaway argument?
> height=\end {center} \end {figure} \subsubsection *{Public Methods} \begin
> \ETC
> .
> ! Paragraph ended before \Gin@ii was complete.
> <to be read again>
>                    \par
> l.31
> --------------------------
>
> If you did not write any LaTeX code into your sources, then it is probably
> doygen's bug.  In such case, try to create as small as possible example
> and send it to Dimitri.
>
> If you did write some LaTeX code, it may be your problem.
>
> Earlier in the text you should see the name of the file where it happened.
> The problem was discovered on the line 31 (l.31).  The messages
> from screen
> are also captured in the .log file.
>
> The warnings like:
> "LaTeX Warning: Reference `class_ObjectManager' on page 1
> undefined on input
> line 3."
>
> are normal and you should ignore them in the first run. LaTeX collects
> the labels and the related information to your .aux file and warns
> if the reference is placed earlier than the label.  Bold question marks
> are used instead of real values in the document (page, chapter, section
> numbers).
> When you run the LaTeX for the second time, the warnings will disappear
> because the values for the labels are found in the .aux file.  It
> can happen
> that the text moves, so the numbers for the labels change.  In such
> case, you can observe:
>
> "LaTeX Warning: Label(s) may have changed. Rerun to get cross-references
> right."
>
> Then you are expected to run LaTeX again.  I have observed that
> the process
> always converges.  If index and table of contents is generated,
> it can take
> more that 2 (usually 3 or 4 runs).
>
> Also, if you were prepare the document manually, the .aux file is
> gradually
> updated with each run that you need for generating preview.  In such case,
> you only sometimes need more than one run.  This fact and the speed
> of earlier computers was probably the reason not to do the subsequent run
> automatically.  And also, there still is some chance that the label really
> does not exist.
>
> Regards,
>   Petr
>
> --
> Petr Prikryl, SKIL, spol. s r.o., pri...@sk...
>
>
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> http://lists.sourceforge.net/lists/listinfo/doxygen-users
>

Re: [Doxygen-users] Re: Documentation of Fortran code?

[Clayton C. <crc...@cs...>]

	Would f2c do the trick?  It's a GNU project that claims to
convert FROTRAN to C.  It's worth a shot I guess, if you don't want to
roll your own.

http://cm.bell-labs.com/netlib/f2c/index.html

--c


On Wed, Aug 22, 2001 at 08:49:26AM +0200, John Sturton wrote:
> Ole Streicher wrote:
> > 
> > Hello John!
> > 
> > John Sturton wrote:
> > > > >We have used Doxygen to document FORTRAN code by using an INPUT_FILTER
> > > > >to convert the original FORTRAN source to C-style function prototypes.
> > > > Can you send or post me this INPUT_FILTER?
> > > No, sorry I can't.
> > 
> > :-( Is it a commercial program, or something you developed internally?
> > 
> 
> It's an internal development, basically a 500-line awk script, that
> produces a C header file compatible with our in-house version of the
> cfortran.h file you mentioned. Maybe the author of cfortran.h has, or
> knows of, a more readily available FORTRAN->C-header script that you
> could modify.
> 
> Good luck,
> 
> John
> 
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> http://lists.sourceforge.net/lists/listinfo/doxygen-users

-- 
Clayton Carter   crcarter @ cs indiana edu
"My mom says I'm the handsomest guy [at work]"

[Doxygen-users] Very strange behaviors

[Luigi B. <lui...@ri...>]

(sorry if this is received twice - it probably didn't get through the first 
time due to mail server problems, but one never knows)

Hi all (and especially Dimitri),
	I'm probably abusing the Doxygen parser here, but I found a couple of 
issues related with namespaces which I isolated in the two short files 
attached. The problems are explained in the comments inside the files 
themselves (they are kind of difficult to explain without code to look at).
A fresh Doxyfile with
INPUT = test1.cpp test2.cpp
will trigger the thing.

Thanks in advance,
			Luigi

P.S. The same behavior is observed in Doxygen 1.2.8.1, 1.2.9.1, and the 
current CVS snapshot. 

[Doxygen-users] Sorting problem

[Luigi B. <lui...@ri...>]

Hi all (and especially Dimitri),
	With both Doxygen 1.2.9.1 and the latest CVS, the compound list is sorted 
taking into account namespaces - even though they are not displayed.
Namely, the following classes:

namespace A {
	class C {};
	class F {};
	class M {};
}

namespace B {
	class D {};
	class G {};
}

are sorted as C,F,M,D,G which would only make sense if I chose to display 
the namespaces, i.e., A::C,A::F,A::M,B::D,B::G

Thanks,
	Luigi

[Doxygen-users] Very strange behaviors

[Luigi B. <lui...@ri...>]

Hi all (and especially Dimitri),
	I'm probably abusing the Doxygen parser here, but I found a couple of 
issues related with namespaces which I isolated in the two short files 
attached. The problems are explained in the comments inside the files 
themselves (they are kind of difficult to explain without code to look at).
A fresh Doxyfile with
INPUT = test1.cpp test2.cpp
will trigger the thing.

Thanks in advance,
			Luigi

P.S. The same behavior is observed in Doxygen 1.2.8.1, 1.2.9.1, and the 
current CVS snapshot.

Re: [Doxygen-users] Re: Documentation of Fortran code?

[John S. <joh...@se...>]

Ole Streicher wrote:
> 
> Hello John!
> 
> John Sturton wrote:
> > > >We have used Doxygen to document FORTRAN code by using an INPUT_FILTER
> > > >to convert the original FORTRAN source to C-style function prototypes.
> > > Can you send or post me this INPUT_FILTER?
> > No, sorry I can't.
> 
> :-( Is it a commercial program, or something you developed internally?
> 

It's an internal development, basically a 500-line awk script, that
produces a C header file compatible with our in-house version of the
cfortran.h file you mentioned. Maybe the author of cfortran.h has, or
knows of, a more readily available FORTRAN->C-header script that you
could modify.

Good luck,

John

RE: [Doxygen-users] Latex problems

[Prikryl,Petr <PRI...@sk...>]

You should focus on
--------------------------
Runaway argument?
height=\end {center} \end {figure} \subsubsection *{Public Methods} \begin
\ETC
.
! Paragraph ended before \Gin@ii was complete.
<to be read again>
                   \par
l.31
--------------------------

If you did not write any LaTeX code into your sources, then it is probably
doygen's bug.  In such case, try to create as small as possible example
and send it to Dimitri.

If you did write some LaTeX code, it may be your problem.

Earlier in the text you should see the name of the file where it happened.
The problem was discovered on the line 31 (l.31).  The messages from screen
are also captured in the .log file.

The warnings like: 
"LaTeX Warning: Reference `class_ObjectManager' on page 1 undefined on input
line 3."

are normal and you should ignore them in the first run. LaTeX collects 
the labels and the related information to your .aux file and warns 
if the reference is placed earlier than the label.  Bold question marks 
are used instead of real values in the document (page, chapter, section
numbers). 
When you run the LaTeX for the second time, the warnings will disappear
because the values for the labels are found in the .aux file.  It can happen
that the text moves, so the numbers for the labels change.  In such
case, you can observe:

"LaTeX Warning: Label(s) may have changed. Rerun to get cross-references
right."

Then you are expected to run LaTeX again.  I have observed that the process
always converges.  If index and table of contents is generated, it can take
more that 2 (usually 3 or 4 runs).

Also, if you were prepare the document manually, the .aux file is gradually
updated with each run that you need for generating preview.  In such case,
you only sometimes need more than one run.  This fact and the speed
of earlier computers was probably the reason not to do the subsequent run
automatically.  And also, there still is some chance that the label really
does not exist.

Regards,
  Petr

-- 
Petr Prikryl, SKIL, spol. s r.o., pri...@sk...

[Doxygen-users] Latex problems

[Markus L. <lo...@ce...>]

I'm using teTex. When I try to compile the doxygen generated latex file with
"make", I get a lot of warnings, and finally the created dvi only contains
the table of contents.
(Using doxygen 1.2.3)

This is TeX, Version 3.14159 (Web2C 7.3.1) (format=latex 2000.11.10)  21 AUG
2001 11:21
**refman.tex
(refman.tex
LaTeX2e <1999/12/01> patch level 1
Babel <v3.6Z> and hyphenation patterns for american, french, german,
ngerman, n
ohyphenation, loaded.
(/root/teTeX/texmf/tex/latex/base/article.cls
Document Class: article 1999/09/10 v1.4a Standard LaTeX document class
(/root/teTeX/texmf/tex/latex/base/size10.clo
File: size10.clo 1999/09/10 v1.4a Standard LaTeX file (size option)
)

....

(hierarchy.tex

LaTeX Warning: Reference `class_ObjectManager' on page 1 undefined on input
lin
e 3.


LaTeX Warning: Reference `class_RoboticObject' on page 1 undefined on input
lin
e 4.

....


Runaway argument?
height=\end {center} \end {figure} \subsubsection *{Public Methods} \begin
\ETC
.
! Paragraph ended before \Gin@ii was complete.
<to be read again>
                   \par
l.31

....


I don't know much about latex. Any help would be greatly appreciated.
Thanks
Markus




-----------------------------
Markus Loffler
Research Assistant
Clemson University
http://markus.ces.clemson.edu

[Doxygen-users] Re: Documentation of Fortran code?

[Ole S. <ole...@gm...>]

Hello John!

John Sturton wrote:
> > >We have used Doxygen to document FORTRAN code by using an INPUT_FILTER
> > >to convert the original FORTRAN source to C-style function prototypes.
> > Can you send or post me this INPUT_FILTER?
> No, sorry I can't.

:-( Is it a commercial program, or something you developed internally?

> if you do mixed FORTRAN/C programming then you've probably got some
> handy script somewhere that automatically creates a header file from
> you FORTRAN source code, haven't you?

Unfortunately, I don't. I use cfortran.h to mix C and Fortran, and I
write the header files necessary by hand.

> Dunno - what's cfortran.h??

It is a header file that allows a portable mixing between Fortran-77
and C (C++).

http://www-zeus.desy.de/~burow/cfortran

It needs that you write for every Fortran function which should be
callable by C something like

#define MYFUNC(A,B,C) CCALLSFFUN3(MYFUNC, myfunc, INT, STRING, PINT, A, B, C)

when the F77 function is like

     FUNCTION MYFUNC(A, B, C)
     INTEGER A
     CHARACTER*(*) B
     INTEGER C
C    ...

As far as I know, there is no tool available that is able to create
the C header file automatically. 

Is there anything I could use for documentation in such an
environment? How difficult is it to add Fortran to doxygen?

Tschuessi

Ole

Re: [Doxygen-users] Re: Documentation of Fortran code?

[John S. <joh...@se...>]

Ole Streicher wrote:
> 
> Hello John!
> 
> Ole Streicher wrote:
> >> Is there a possibility to use Doxygen to document FORTRAN code? Or is
> >> it easy to extend Doxygen for this language?
> 
> >We have used Doxygen to document FORTRAN code by using an INPUT_FILTER
> >to convert the original FORTRAN source to C-style function prototypes.
> 
> Can you send or post me this INPUT_FILTER?
> 

No, sorry I can't. On the other hand, if you do mixed FORTRAN/C
programming then you've probably got some handy script somewhere that
automatically creates a header file from you FORTRAN source code,
haven't you? i.e. if you've got some FORTRAN functions that you call
from C, then someone/something/somewhere must have generated an
associated C header file to give the FORTRAN functions' prototypes. If
so, then you just need to tweak this script to include the Doxygen
comments in its output...

> BTW, is there also a good way to document FORTRAN callable functions
> wrapped by cfortran.h?

Dunno - what's cfortran.h??


Cheers,

John

[Doxygen-users] Re: Documentation of Fortran code?

[Ole S. <ole...@gm...>]

Hello John!

Ole Streicher wrote:
>> Is there a possibility to use Doxygen to document FORTRAN code? Or is
>> it easy to extend Doxygen for this language?

>We have used Doxygen to document FORTRAN code by using an INPUT_FILTER
>to convert the original FORTRAN source to C-style function prototypes.

Can you send or post me this INPUT_FILTER?

BTW, is there also a good way to document FORTRAN callable functions
wrapped by cfortran.h?

Tschuessi

Ole

Re: [Doxygen-users] Documentation of Fortran code?

[John S. <joh...@se...>]

Ole Streicher wrote:
> 
> Hi!
> 
> Is there a possibility to use Doxygen to document FORTRAN code? Or is
> it easy to extend Doxygen for this language?
> 
> Or doesn anyone a better solution to document mixed F77/C code?
> 

We have used Doxygen to document FORTRAN code by using an INPUT_FILTER
to convert the original FORTRAN source to C-style function prototypes.

Cheers,

John

[Doxygen-users] Documentation of Fortran code?

[Ole S. <ole...@gm...>]

Hi!

Is there a possibility to use Doxygen to document FORTRAN code? Or is
it easy to extend Doxygen for this language?

Or doesn anyone a better solution to document mixed F77/C code?

Tschuessi

Ole

[Doxygen-users] Problem generating dox for typedef void

[Geoff D. <gef...@di...>]

Hi,

Not sure if this is a bug/quirk, or something that I need to take care of=
 explicitly in the
doxygen config setup.

The source file I'm having problems with contains a bunch of typedefs lik=
e the following;
  typedef void(APIENTRY* PFN_QGLALPHAFUNC) (GLenum func, GLclampf ref);

the file igl.h can be viewed here via viewcvs at the following url:
http://zerowing.idsoftware.com/viewcvs/viewcvs.cgi/~checkout~/GtkRadiant/=
include/igl.h?rev=3DHEAD&content-type=3Dtext/plain

Doxygen generates unexpected results from this file...
eg:
...
Compounds
  struct =A0_QERQglTable
  class =A0IGL2DWindow
  class =A0IGL3DWindow

Functions
  typedef=A0void (APIENTRY *PFN_QGLALPHAFUNC)(GLenum func, GLclampf ref)
  typedef=A0void (APIENTRY *PFN_QGLCALLLISTS)(GLsizei n, GLenum type, con=
st GLvoid *lists)
  typedef=A0GLuint (APIENTRY *PFN_QGLGENLISTS)(GLsizei range)
  typedef=A0void (WINAPI *PFN_QE_CHECKOPENGLFORERRORS)()

Variables
  const GUID=A0QERQglTable_GUID
...

We've only just started using doxygen to generate documentation for GtkRa=
diant, so the
doxygen docs are not available online as yet (although you can check out =
the source & generate
the docs with the included scripts .. see http://zerowing.idsoftware.com).

Gef :]
--

[Doxygen-users] Doxygen-1.2.9-20010819 in CVS

[Dimitri v. H. <di...@st...>]

Hi,

Here's the changelog for this week's release:
--------------------------------------------------------------------------------
+ ADD: Added new command \dotfile which can be used to include a user
       specified dot file as an image in the documentation. The new config
       option DOTFILE_DIRS should be used to specify directories in which
       doxygen should look for dot files (thanks to Samit Basu for the patch).
+ ADD: Added now build target macosx-c++ to build doxygen for Mac OS X 
       (Thanks to Jason Harris for telling me what needed to be changed).
+ ADD: Added --enable-langs option to the configure script which can be used
       to compile-in support for a specified set of languages (thanks to
       Vitaly Repin for the patch).
+ ADD: Included update for Russian & Italian translation.
+ BUG: The "list of all members" was no longer generated for nested classes.
+ BUG: Fixed bug in XML output causing mismatched <para> tags.
+ BUG: Fixed parse problem for enum initializers like: "enumVal = A<T,C>::val"
+ BUG: \hideinitializer did not hide the initializer of enum values.
+ BUG: Undocumented enums and enum values now behave correctly when
       HIDE_UNDOC_MEMBERS is set to YES.
+ BUG: Fixed a problem with using \if inside alias definitions.
--------------------------------------------------------------------------------
Enjoy,
  Dimitri

[Doxygen-users] more compiling errors in UNIX

[Yin, Z. <zy...@le...>]

I follow the suggeston in Doxygen-users digest, Vol 1 #105 - 4 msgs.

When I run configuration, I try ./configure -platform solaris-g++.
Following is the output messages. It seems everytime after "rm -f
../lib/libdoxygen.a" is called. I will get some error related to
libdoxygen.a. Can anyone tell me how to fix this problem?


//configure output
***************************************************************
neihu{zyin}57: sh ./configure -platform solaris-g++
-n   Checking for platform solaris-g++...
supported
-n   Checking for GNU make tool...
using /usr/local/bin/gmake
-n   Checking for GNU install tool...
using /usr/local/bin/install
-n   Checking for dot (part of GraphViz)...
not found!
-n   Checking for perl...
using /usr/local/bin/perl
  Created Makefile from Makefile.in...
  Created qtools/Makefile from qtools/Makefile.in...
  Created src/Makefile from src/Makefile.in...
  Created examples/Makefile from examples/Makefile.in...
  Created doc/Makefile from doc/Makefile.in...
  Created addon/doxywizard/Makefile from addon/doxywizard/Makefile.in...

  Created addon/xmlparse/Makefile from addon/xmlparse/Makefile.in...
  Created qtools/qtools.pro from qtools/qtools.pro.in...
  Created src/libdoxygen.pro from src/libdoxygen.pro.in...
  Created src/libdoxycfg.pro from src/libdoxycfg.pro.in...
  Created src/doxygen.pro from src/doxygen.pro.in...
  Created src/doxytag.pro from src/doxytag.pro.in...
  Created src/doxysearch.pro from src/doxysearch.pro.in...
  Created addon/doxywizard/doxywizard.pro from
addon/doxywizard/doxywizard.pro.in...
  Created addon/xmlparse/xmlparse.pro from
addon/xmlparse/xmlparse.pro.in...


//make output
***************************************************************
neihu{zyin}58: make
echo "char versionString[]=\"1.2.9.1\";" > src/version.cpp
/usr/local/bin/gmake -C qtools
gmake: Entering directory `/space2/temp/doxygen-1.2.9.1/qtools'
env TMAKEPATH=/space2/temp/doxygen-1.2.9.1/tmake/lib/solaris-g++
/usr/local/bin/perl /space2/temp/doxygen-1.2.9.1/tmake/bin/tmake
qtools.pro >Makefile.qtools
/usr/local/bin/gmake -f Makefile.qtools    all
gmake[1]: Entering directory `/space2/temp/doxygen-1.2.9.1/qtools'
gmake[1]: Nothing to be done for `all'.
gmake[1]: Leaving directory `/space2/temp/doxygen-1.2.9.1/qtools'
gmake: Leaving directory `/space2/temp/doxygen-1.2.9.1/qtools'
/usr/local/bin/gmake -C src
gmake: Entering directory `/space2/temp/doxygen-1.2.9.1/src'
env TMAKEPATH=/space2/temp/doxygen-1.2.9.1/tmake/lib/solaris-g++
/usr/local/bin/perl /space2/temp/doxygen-1.2.9.1/tmake/bin/tmake
libdoxygen.pro >Makefile.libdoxygen
env TMAKEPATH=/space2/temp/doxygen-1.2.9.1/tmake/lib/solaris-g++
/usr/local/bin/perl /space2/temp/doxygen-1.2.9.1/tmake/bin/tmake
libdoxycfg.pro >Makefile.libdoxycfg
env TMAKEPATH=/space2/temp/doxygen-1.2.9.1/tmake/lib/solaris-g++
/usr/local/bin/perl /space2/temp/doxygen-1.2.9.1/tmake/bin/tmake
doxygen.pro >Makefile.doxygen
env TMAKEPATH=/space2/temp/doxygen-1.2.9.1/tmake/lib/solaris-g++
/usr/local/bin/perl /space2/temp/doxygen-1.2.9.1/tmake/bin/tmake
doxytag.pro >Makefile.doxytag
env TMAKEPATH=/space2/temp/doxygen-1.2.9.1/tmake/lib/solaris-g++
/usr/local/bin/perl /space2/temp/doxygen-1.2.9.1/tmake/bin/tmake
doxysearch.pro >Makefile.doxysearch
/usr/local/bin/gmake -f Makefile.libdoxycfg all
gmake[1]: Entering directory `/space2/temp/doxygen-1.2.9.1/src'
g++ -c -Wall -W -O2 -I../qtools -o ../objects/config.o config.cpp
config.l: In function `void substEnvVarsInStrList(QStrList &)':
config.l:714: warning: `char c' might be used uninitialized in this
function
rm -f ../lib/libdoxycfg.a
ar cq ../lib/libdoxycfg.a ../objects/config.o
gmake[1]: Leaving directory `/space2/temp/doxygen-1.2.9.1/src'
/usr/local/bin/gmake -f Makefile.libdoxygen all
gmake[1]: Entering directory `/space2/temp/doxygen-1.2.9.1/src'
g++ -c -Wall -W -O2 -I../qtools -o ../objects/ce_lex.o ce_lex.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/ce_parse.o ce_parse.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/classdef.o classdef.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/classlist.o classlist.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/code.o code.cpp
../qtools/qstack.h: In method `void QStack<void>::deleteItem(void *)':
code.l:129:   instantiated from here
../qtools/qstack.h:66: warning: `void *' is not a pointer-to-object type

g++ -c -Wall -W -O2 -I../qtools -o ../objects/cppvalue.o cppvalue.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/debug.o debug.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/declinfo.o declinfo.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/defargs.o defargs.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/define.o define.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/definition.o
definition.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/diagram.o diagram.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/doc.o doc.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/dot.o dot.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/doxygen.o doxygen.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/entry.o entry.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/filedef.o filedef.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/filename.o filename.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/formula.o formula.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/ftvhelp.o ftvhelp.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/gifenc.o gifenc.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/groupdef.o groupdef.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/htmlgen.o htmlgen.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/htmlhelp.o htmlhelp.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/image.o image.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/index.o index.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/instdox.o instdox.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/language.o language.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/latexgen.o latexgen.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/logos.o logos.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/mangen.o mangen.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/memberdef.o memberdef.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/membergroup.o
membergroup.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/memberlist.o
memberlist.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/membername.o
membername.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/message.o message.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/namespacedef.o
namespacedef.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/outputgen.o outputgen.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/outputlist.o
outputlist.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/packagedef.o
packagedef.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/pre.o pre.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/reflist.o reflist.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/rtfgen.o rtfgen.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/scanner.o scanner.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/searchindex.o
searchindex.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/suffixtree.o
suffixtree.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/tagreader.o tagreader.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/translator.o
translator.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/util.o util.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/version.o version.cpp
g++ -c -Wall -W -O2 -I../qtools -o ../objects/xmlgen.o xmlgen.cpp
rm -f ../lib/libdoxygen.a
ar cq ../lib/libdoxygen.a ../objects/ce_lex.o ../objects/ce_parse.o
../objects/classdef.o ../objects/classlist.o ../objects/code.o
../objects/cppvalue.o ../objects/debug.o ../objects/declinfo.o
../objects/defargs.o ../objects/define.o ../objects/definition.o
../objects/diagram.o ../objects/doc.o ../objects/dot.o
../objects/doxygen.o ../objects/entry.o ../objects/filedef.o
../objects/filename.o ../objects/formula.o ../objects/ftvhelp.o
../objects/gifenc.o ../objects/groupdef.o ../objects/htmlgen.o
../objects/htmlhelp.o ../objects/image.o ../objects/index.o
../objects/instdox.o ../objects/language.o ../objects/latexgen.o
../objects/logos.o ../objects/mangen.o ../objects/memberdef.o
../objects/membergroup.o ../objects/memberlist.o ../objects/membername.o
../objects/message.o ../objects/namespacedef.o ../objects/outputgen.o
../objects/outputlist.o ../objects/packagedef.o ../objects/pre.o
../objects/reflist.o ../objects/rtfgen.o ../objects/scanner.o
../objects/searchindex.o ../objects/suffixtree.o ../objects/tagreader.o
../objects/translator.o ../objects/util.o ../objects/version.o
../objects/xmlgen.o
gmake[1]: Leaving directory `/space2/temp/doxygen-1.2.9.1/src'
/usr/local/bin/gmake -f Makefile.doxygen    all
gmake[1]: Entering directory `/space2/temp/doxygen-1.2.9.1/src'
g++ -c -Wall -W -O2 -I../qtools -I. -o ../objects/main.o main.cpp
g++  -o ../bin/doxygen ../objects/main.o  -L../lib -ldoxygen -ldoxycfg
-lqtools
ld: warning: symbol `QList<char> virtual table' has differing sizes:
        (file ../lib/libdoxygen.a(htmlhelp.o) value=0x50; file
../lib/libqtools.a(qdir.o) value=0x48);
        ../lib/libdoxygen.a(htmlhelp.o) definition taken
ld: warning: symbol `QList<char> virtual table' has differing sizes:
        (file ../lib/libdoxygen.a(htmlhelp.o) value=0x50; file
../lib/libqtools.a(qfileinfo.o) value=0x48);
        ../lib/libdoxygen.a(htmlhelp.o) definition taken
ld: warning: symbol `QList<char> virtual table' has differing sizes:
        (file ../lib/libdoxygen.a(htmlhelp.o) value=0x50; file
../lib/libqtools.a(qtextcodec.o) value=0x48);
        ../lib/libdoxygen.a(htmlhelp.o) definition taken
ld: warning: symbol `QList<char> virtual table' has differing sizes:
        (file ../lib/libdoxygen.a(htmlhelp.o) value=0x50; file
../lib/libqtools.a(qstringlist.o) value=0x48);
        ../lib/libdoxygen.a(htmlhelp.o) definition taken
ld: warning: symbol `QList<char> virtual table' has differing sizes:
        (file ../lib/libdoxygen.a(htmlhelp.o) value=0x50; file
../lib/libqtools.a(qdir_unix.o) value=0x48);
        ../lib/libdoxygen.a(htmlhelp.o) definition taken
ld: warning: symbol `QList<char> virtual table' has differing sizes:
        (file ../lib/libdoxygen.a(htmlhelp.o) value=0x50; file
../lib/libqtools.a(qfileinfo_unix.o) value=0x48);
        ../lib/libdoxygen.a(htmlhelp.o) definition taken
Undefined                       first referenced
 symbol                             in file
QGList type_info function           ../lib/libdoxygen.a(doxygen.o)
QGList type_info node               ../lib/libdoxygen.a(doxygen.o)
QGDict type_info function           ../lib/libdoxygen.a(doxygen.o)
QGDict type_info node               ../lib/libdoxygen.a(doxygen.o)
QGArray type_info node              ../lib/libdoxygen.a(doxygen.o)
QXmlDefaultHandler type_info function../lib/libdoxygen.a(tagreader.o)
QGArray type_info function          ../lib/libdoxygen.a(doxygen.o)
QXmlDefaultHandler type_info node   ../lib/libdoxygen.a(tagreader.o)
ld: fatal: Symbol referencing errors. No output written to
../bin/doxygen
collect2: ld returned 1 exit status
gmake[1]: *** [../bin/doxygen] Error 1
gmake[1]: Leaving directory `/space2/temp/doxygen-1.2.9.1/src'
gmake: *** [all] Error 2
gmake: Leaving directory `/space2/temp/doxygen-1.2.9.1/src'
*** Error code 2
make: Fatal error: Command failed for target `all'

[Doxygen-users] Small bug ?!? dot(graph_legend.html)

[<vel...@te...>]

When I click to legend of dot graph i have new IE window open with adress :
mk:@MSITStore:C:\VV\Techsia\TechLog\doc\html\index.chm::/graph_legend.html

May be the html page (graph_legend.html) must be in the CHM widget ?!?

Tnx,
VV

--
_______________________________________________________________________

 Vélizar VESSELINOV
 Chef de projet                       Téléphone : +33.(0)4.67.59.30.47
 Pôle Informatique             E-mail : vel...@te...

 Techsia S.A.
 Cap Alpha - Avenue de l'Europe, Clapiers
 34940 Montpellier Cedex 9                      http://www.techsia.com
 France                                     Fax : +33.(0)4.67.59.36.19
_______________________________________________________________________

      Les données maîtrisées        ~         The end of doubt

[Doxygen-users] Table size and a Problem with Source filter

[Gregory R. <gre...@ya...>]

Hi All!

2 questions :
- I'm using the source filter option in doxygen to extract the file version information from clearcase and I manage
  to make it work. But it seems that the FILTER_SOURCE_FILES doen't work. If I put a "NO" my filter is still
  used. Is this a bug ?

- With the HTML files, I'm using a .css file to change the color of heading 2 (H2) to be grey on a black background (I find
easier to read). The problem is, on the class description the first table (the public member) is not as wide as the browser
(actually the size depend on the largest member declarartion). Is it possible to change it to be be 100% large. It's juste a
WIDTH=100% to add on the table .

Thanks.

PS: Sorry for my english

Greg

Re: [Doxygen-users] Problem with Make

[<Lar...@ra...>]

To All,
I removed the files in objects/SunWS_cache and re-ran make, and got these
set of errors:
make[2]: Entering directory `/usr/home/lwkemp/doxygen-1.2.9.1/src'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/usr/home/lwkemp/doxygen-1.2.9.1/src'
/software/fsf/bin/make -f Makefile.libdoxygen all
make[2]: Entering directory `/usr/home/lwkemp/doxygen-1.2.9.1/src'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/usr/home/lwkemp/doxygen-1.2.9.1/src'
/software/fsf/bin/make -f Makefile.doxygen    all
make[2]: Entering directory `/usr/home/lwkemp/doxygen-1.2.9.1/src'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/usr/home/lwkemp/doxygen-1.2.9.1/src'
/software/fsf/bin/make -f Makefile.doxytag    all
make[2]: Entering directory `/usr/home/lwkemp/doxygen-1.2.9.1/src'
CC  -o ../bin/doxytag ../objects/doxytag.o ../objects/suffixtree.o ../objects/se
archindex.o ../objects/logos.o ../objects/version.o  -L../lib -lqtools
Undefined                       first referenced
 symbol                             in file
QDict<DocRef>::__vtbl     ../objects/searchindex.o
[Hint: try checking whether the first non-inlined, non-pure virtual function of
class QDict<DocRef> is defined]

QList<MemberDef>::__vtbl  ../objects/doxytag.o
[Hint: try checking whether the first non-inlined, non-pure virtual function of
class QList<MemberDef> is defined]

QList<ClassDef>::__vtbl   ../objects/doxytag.o
[Hint: try checking whether the first non-inlined, non-pure virtual function of
class QList<ClassDef> is defined]

QDict<ClassDef>::__vtbl   ../objects/doxytag.o
[Hint: try checking whether the first non-inlined, non-pure virtual function of
class QDict<ClassDef> is defined]

QList<SuffixNode>::__vtbl ../objects/suffixtree.o
[Hint: try checking whether the first non-inlined, non-pure virtual function of
class QList<SuffixNode> is defined

QList<DocRef>::__vtbl     ../objects/searchindex.o
[Hint: try checking whether the first non-inlined, non-pure virtual function of
class QList<DocRef> is defined]

QIntDict<DocRef>::__vtbl  ../objects/searchindex.o
[Hint: try checking whether the first non-inlined, non-pure virtual function of
class QIntDict<DocRef> is defined]

QArray<WordRef>::__vtbl   ../objects/suffixtree.o
[Hint: try checking whether the first non-inlined, non-pure virtual function of
class QArray<WordRef> is defined]

ld: fatal: Symbol referencing errors. No output written to ../bin/doxytag
make[2]: *** [../bin/doxytag] Error 1
make[2]: Leaving directory `/usr/home/lwkemp/doxygen-1.2.9.1/src'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/usr/home/lwkemp/doxygen-1.2.9.1/src'
make: *** [all] Error 2

Thank you,
Larry

P.S. This information might be of some help to.  I received another error when I first ran the make:

flex -PscanYY -t scanner.l >scanner.cpp
CC -c -DENGLISH_ONLY -O2 -I../qtools -o ../objects/scanner.o scanner.cpp
CC -c -DENGLISH_ONLY -O2 -I../qtools -o ../objects/searchindex.o searchindex.cpp
CC -c -DENGLISH_ONLY -O2 -I../qtools -o ../objects/suffixtree.o suffixtree.cpp
CC -c -DENGLISH_ONLY -O2 -I../qtools -o ../objects/tagreader.o tagreader.cpp
CC -c -DENGLISH_ONLY -O2 -I../qtools -o ../objects/translator.o translator.cpp
CC -c -DENGLISH_ONLY -O2 -I../qtools -o ../objects/util.o util.cpp
CC -c -DENGLISH_ONLY -O2 -I../qtools -o ../objects/version.o version.cpp
CC -c -DENGLISH_ONLY -O2 -I../qtools -o ../objects/xmlgen.o xmlgen.cpp
"xmlgen.cpp", line 402: Error: The name writeXMLLink(QTextStream&, const char*, const char*, const char*) is unusable in
XMLGenerator::writeCodeLink(const char*, const char*, const char*, const char*).
"xmlgen.cpp", line 390: Error: The name writeXMLLink(QTextStream&, const char*, const char*, const char*) is unusable in
XMLGenerator::writeObjectLink(const char*, const char*, const char*, const char*).
"xmlgen.cpp", line 72: Error: The name writeXMLLink(QTextStream&, const char*, const char*, const char*) is unusable in
TextGeneratorXMLImpl::writeLink(const char*, const char*, const char*, const char*) const.
3 Error(s) detected.
make[2]: *** [../objects/xmlgen.o] Error 3
make[2]: Leaving directory `/usr/home/lwkemp/doxygen-1.2.9.1/src'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/usr/home/lwkemp/doxygen-1.2.9.1/src'
make: *** [all] Error 2

To get past this I went to the file xmlgen.cpp and made writeXMLLink and writeCodeLink inline functions:
static inline void writeXMLString(QTextStream &t,const char *s)
{
  t << convertToXML(s);
}

static inline void writeXMLLink(QTextStream &t,const char *compoundId,
                  const char *memId,const char *text)
{
  if (memId==0)
  {
    t << "<compoundref idref=\"" << compoundId << "\">";
    writeXMLString(t,text);
    t << "</compoundref>";
  }
  else
  {
    t << "<memberref idref=\"" << compoundId << "_1" << memId << "\">";
    writeXMLString(t,text);
    t << "</memberref>";
  }
}

Thank you,
Larry Kemp]






"Dimitri van Heesch" <dox...@li...> on
08/16/2001 02:37:42 PM

Please respond to dox...@li...

To:   dox...@li...
cc:    (bcc: Larry W Kemp/US/Raytheon)
Subject:  Re: [Doxygen-users] Problem with Make



On Wed, Aug 15, 2001 at 04:28:19PM -0500, Lar...@ra... wrote:
> To Group,
> I am running Solaris 2.7 and using gnu compiler.  Below is the printout
> after initiating make.  Any help would be greatly appreciated.

Ah, that problem again...

As you may have noticed the doxygen executable is already build in bin.
Removing the junk in objects/SunWS_cache and then trying make again will
give you doxytag as well.

Regards,
  Dimitri

>
> Thank you,
> Larry Kemp
>
> make[2]: Nothing to be done for `all'.
> make[2]: Leaving directory `/usr/home/lwkemp/doxygen-1.2.9.1/src'
> /software/fsf/bin/make -f Makefile.doxygen    all
> make[2]: Entering directory `/usr/home/lwkemp/doxygen-1.2.9.1/src'
> make[2]: Nothing to be done for `all'.
> make[2]: Leaving directory `/usr/home/lwkemp/doxygen-1.2.9.1/src'
> /software/fsf/bin/make -f Makefile.doxytag    all
> make[2]: Entering directory `/usr/home/lwkemp/doxygen-1.2.9.1/src'
> CC  -o ../bin/doxytag ../objects/doxytag.o ../objects/suffixtree.o
../objects/se
> archindex.o ../objects/logos.o ../objects/version.o  -L../lib -lqtools
> Undefined                       first referenced
>  symbol                             in file
> QList<Argument>::__vtbl
/usr/home/lwkemp/doxygen-1.2.9.1/objects/SunWS_cache/C
> C_obj_j/jKyElLK8EP2B9pONhnx4.o
> [Hint: try checking whether the first non-inlined, non-pure virtual
function of
> class QList<Argument> is defined]
>
[snip]

_______________________________________________
Doxygen-users mailing list
Dox...@li...
http://lists.sourceforge.net/lists/listinfo/doxygen-users

Re: [Doxygen-users] Problem with Make

[Dimitri v. H. <di...@st...>]

On Wed, Aug 15, 2001 at 04:28:19PM -0500, Lar...@ra... wrote:
> To Group,
> I am running Solaris 2.7 and using gnu compiler.  Below is the printout
> after initiating make.  Any help would be greatly appreciated.

Ah, that problem again...

As you may have noticed the doxygen executable is already build in bin. 
Removing the junk in objects/SunWS_cache and then trying make again will 
give you doxytag as well.

Regards,
  Dimitri

> 
> Thank you,
> Larry Kemp
> 
> make[2]: Nothing to be done for `all'.
> make[2]: Leaving directory `/usr/home/lwkemp/doxygen-1.2.9.1/src'
> /software/fsf/bin/make -f Makefile.doxygen    all
> make[2]: Entering directory `/usr/home/lwkemp/doxygen-1.2.9.1/src'
> make[2]: Nothing to be done for `all'.
> make[2]: Leaving directory `/usr/home/lwkemp/doxygen-1.2.9.1/src'
> /software/fsf/bin/make -f Makefile.doxytag    all
> make[2]: Entering directory `/usr/home/lwkemp/doxygen-1.2.9.1/src'
> CC  -o ../bin/doxytag ../objects/doxytag.o ../objects/suffixtree.o ../objects/se
> archindex.o ../objects/logos.o ../objects/version.o  -L../lib -lqtools
> Undefined                       first referenced
>  symbol                             in file
> QList<Argument>::__vtbl   /usr/home/lwkemp/doxygen-1.2.9.1/objects/SunWS_cache/C
> C_obj_j/jKyElLK8EP2B9pONhnx4.o
> [Hint: try checking whether the first non-inlined, non-pure virtual function of
> class QList<Argument> is defined]
> 
[snip]

[Doxygen-users] Problem with Make

[<Lar...@ra...>]

To Group,
I am running Solaris 2.7 and using gnu compiler.  Below is the printout
after initiating make.  Any help would be greatly appreciated.

Thank you,
Larry Kemp

make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/usr/home/lwkemp/doxygen-1.2.9.1/src'
/software/fsf/bin/make -f Makefile.doxygen    all
make[2]: Entering directory `/usr/home/lwkemp/doxygen-1.2.9.1/src'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/usr/home/lwkemp/doxygen-1.2.9.1/src'
/software/fsf/bin/make -f Makefile.doxytag    all
make[2]: Entering directory `/usr/home/lwkemp/doxygen-1.2.9.1/src'
CC  -o ../bin/doxytag ../objects/doxytag.o ../objects/suffixtree.o ../objects/se
archindex.o ../objects/logos.o ../objects/version.o  -L../lib -lqtools
Undefined                       first referenced
 symbol                             in file
QList<Argument>::__vtbl   /usr/home/lwkemp/doxygen-1.2.9.1/objects/SunWS_cache/C
C_obj_j/jKyElLK8EP2B9pONhnx4.o
[Hint: try checking whether the first non-inlined, non-pure virtual function of
class QList<Argument> is defined]

QDict<UsesClassDef>::__vtbl /usr/home/lwkemp/doxygen-1.2.9.1/objects/SunWS_cache
/CC_obj_j/jKyElLK8EP2B9pONhnx4.o
[Hint: try checking whether the first non-inlined, non-pure virtual function of
class QDict<UsesClassDef> is defined]

QList<BaseClassDef>::__vtbl /usr/home/lwkemp/doxygen-1.2.9.1/objects/SunWS_cache
/CC_obj_j/jKyElLK8EP2B9pONhnx4.o
[Hint: try checking whether the first non-inlined, non-pure virtual function of
class QList<BaseClassDef> is defined]

QIntDict<MemberGroup>::__vtbl /usr/home/lwkemp/doxygen-1.2.9.1/objects/SunWS_cac
he/CC_obj_j/jKyElLK8EP2B9pONhnx4.o
[Hint: try checking whether the first non-inlined, non-pure virtual function of
class QIntDict<MemberGroup> is defined]

SDict<MemberNameInfo>::__vtbl /usr/home/lwkemp/doxygen-1.2.9.1/objects/SunWS_cac
he/CC_obj_j/jKyElLK8EP2B9pONhnx4.o
[Hint: try checking whether the first non-inlined, non-pure virtual function of
class SDict<MemberNameInfo> is defined]

MemberGroup::~MemberGroup()             /usr/home/lwkemp/doxygen-1.2.9.1/objects
/SunWS_cache/CC_obj_j/jKyElLK8EP2B9pONhnx4.o
SDict<Example>::__vtbl      /usr/home/lwkemp/doxygen-1.2.9.1/objects/SunWS_cache
/CC_obj_j/jKyElLK8EP2B9pONhnx4.o
[Hint: try checking whether the first non-inlined, non-pure virtual function of
class SDict<Example> is defined]

QList<MemberGroup>::__vtbl /usr/home/lwkemp/doxygen-1.2.9.1/objects/SunWS_cache/
CC_obj_j/jKyElLK8EP2B9pONhnx4.o
[Hint: try checking whether the first non-inlined, non-pure virtual function of
class QList<MemberGroup> is defined]

ld: fatal: Symbol referencing errors. No output written to ../bin/doxytag
make[2]: *** [../bin/doxytag] Error 1
make[2]: Leaving directory `/usr/home/lwkemp/doxygen-1.2.9.1/src'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/usr/home/lwkemp/doxygen-1.2.9.1/src'
make: *** [all] Error 2

[Doxygen-users] VPATH?

[Monmouth D. <da...@ya...>]

It doesn't look like doxygen supports vpath directly.
I tried to write a script that uses VPATH, in the
filter option, but wasn't able to get it work work the
way I wanted. Has any gotten doxygen to work in VPATH environment?

=====
(o o)
------------oOOo-(_)-oOOo-----------------------------------------
dan                              Manasquan, NJ
email (da...@ya...)        IM on Yahoo/AOL (dan5691)

__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/

Re: [Doxygen-users] XML output in Doxygen-1.2.9.1

[Dimitri v. H. <di...@st...>]

On Tue, Aug 14, 2001 at 01:17:33PM +1000, Tom Harris wrote:
> > Hi, 
> > 
> > My apologies if this has already been noted, but I have just played with
> > enabling XML output in version 1.2.9.1, and I find that the XML is broken,
> > with tags being closed in the wrong order, eg
> > 
> > <detaileddescription>
> >   <para>
> >     Blah blah...
> >     <simplesect>
> >       <title><bold>Returns: </bold></title>
> >         More blah.
> >     </para>
> >   </simplesect>
> >   <simplesect>
> >     <title>
> >       <para>
> >         <bold>Warning: </bold>
> >       </title>Even more blah.
> >     </para>
> >   </simplesect>        
> > </detaileddescription>

This is a bug indeed (due to an uninitialized member variable). 
Will be fixed.

Regards,
  Dimitri

[Doxygen-users] Hiding unocumented enums

[Moshe K. <Kr...@Pa...>]

Hi!
 
When I document any number of specific enums in a .h file, all of the enums
appear.
 
They show up in black, as opposed to those I wanted to appear (which show up
as active links)
 
Of course, I have the following settings:
EXTRACT_ALL            = NO
EXTRACT_PRIVATE        = NO
EXTRACT_STATIC         = NO
HIDE_UNDOC_MEMBERS     = YES
HIDE_UNDOC_CLASSES     = YES
BRIEF_MEMBER_DESC      = YES
REPEAT_BRIEF           = YES
ALWAYS_DETAILED_SEC    = YES

How do I get the undocumened enums not to show up??
 
Moshe Kruger
 

RE: [Doxygen-users] compiling error in UNIX

[Martin S. <ms...@cl...>]

The output from configure reckons its using solaris-cc , try rerunning
configure but specifying the platform like.

	configure -platform solaris-g++


hope it helps

martin

-----Original Message-----
From: dox...@li...
[mailto:dox...@li...]On Behalf Of Yin, Zhen
Sent: 15 August 2001 01:01
To: dox...@li...
Cc: zy...@le...
Subject: [Doxygen-users] compiling error in UNIX


I was trying to compile 1.2.9.1 in Solaris 2.5, the default compiler in
my solaris is gcc.

sh ./configure goes well. output message is in output.configure.

However, I kept got error message when I run "make". Error message is
included in output.make.

It seems in Makefile.qtools, the tag "AR" is not recognizable.

Is there anyway to solve this problem?

thanks

zhen