doxygen-users — List for users of doxygen

Re: [Doxygen-users] Problems compiling Doxygen on Solaris

[Jac G. <ja...@ma...>]

>I am trying to build doxygen 1.2.8.1 on solaris 5.8, and am getting 
errors. 
>We're using GCC/G++ 2.95.3, and have flex, bison and gmake installed 
on the
>machine.

>  Autodetected platform solaris-cc... 

>CC      =       cc
>CXX     =       CC

There you have it: the configuration script detects that you are using 
the cc compiler instead of the gcc compiler.

You should run the configure script with a --platform option (not sure 
which one) to tell it that you have gcc installed, instead of Solaris' 
compiler.

===Jac

[Doxygen-users] Problems compiling Doxygen on Solaris

[Sanjay B. <sb...@ya...>]

Hi,

I am trying to build doxygen 1.2.8.1 on solaris 5.8, and am getting errors. 
We're using GCC/G++ 2.95.3, and have flex, bison and gmake installed on the
machine.  Can someone tell me what could be going wrong?  Here are the
details... please mail me if you need more info.

Thanks,
sb



The following is the output from configure : 

sb@molokai:~/doxygen-1.2.8.1: ./configure --prefix /usr/local
  Autodetected platform solaris-cc... 
-n   Checking for GNU make tool... 
using /usr/local/bin/gmake
-n   Checking for dot (part of GraphViz)... 
not found!
-n   Checking for perl... 
using /usr/local/bin/perl
  Created Makefile from Makefile.in...
  Created addon/xmlgen/Makefile from addon/xmlgen/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/xmlread/Makefile from addon/xmlread/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/xmlread/xmlread.pro from addon/xmlread/xmlread.pro.in...
  Created addon/xmlgen/xmlgen.pro from addon/xmlgen/xmlgen.pro.in...

and this is what I get when I run make/gmake : 

sb@molokai:~/doxygen-1.2.8.1: make
/usr/local/bin/gmake -C qtools
gmake[1]: Entering directory `/home/sb/doxygen-1.2.8.1/qtools'
/usr/local/bin/gmake -f Makefile.qtools    all
gmake[2]: Entering directory `/home/sb/doxygen-1.2.8.1/qtools'
CC -c -DQT_NO_CODECS -DQT_LITE_UNICODE -O2 -I. -o ../objects/qbuffer.o
qbuffer.cpp
gmake[2]: CC: Command not found
gmake[2]: *** [../objects/qbuffer.o] Error 127
gmake[2]: Leaving directory `/home/sb/doxygen-1.2.8.1/qtools'
gmake[1]: *** [all] Error 2
gmake[1]: Leaving directory `/home/sb/doxygen-1.2.8.1/qtools'
make: *** [all] Error 2



Makefile.qtools has the following defined : 


CC      =       cc
CXX     =       CC
CFLAGS  =       -O
CXXFLAGS=       -DQT_NO_CODECS -DQT_LITE_UNICODE -O2
INCPATH =       -I.
AR      =       CC -xar -o
RANLIB  =       
MOC     =       moc

TAR     =       tar -cf
GZIP    =       gzip -9f


__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/

Re: [Doxygen-users] Searchable email list archive?

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

On Mon, Jun 25, 2001 at 10:13:11AM -0400, Dan Muller wrote:
> Is there a searchable and reasonably up-to-date archive of doxygen-users
> somewhere? The GeoCrawler site's search functionality seems to be broken,
> and clicking the "About" link gives me a message saying that GeoCrawler is
> no longer being maintained.

I depend on the facilities offered by sourceforge for this. So as long as
they don't fix the problem, there will be no searching :-(
(I don't think doxygen is the only project with this problem, but if 
anyone knows how to get the searching to work again, please let me know).

Regards,
  Dimitri

Re: [Doxygen-users] Index/TOC entries in .chm files

[Bogdan I. <bo...@ne...>]

I think the question was how to get those references to be listed in the
left pane of a html help window, together with the 'Compound List' and the
'Class Hierarchy'.

I didn't find any direct way to do that. One workaround would be to use the
modules facility, but this will list your entries under a 'Modules' title
in the TOC. For this, look up the 'Grouping' section in the main
documentation page of doxygen. I'm not sure if this will be of any use to
you, but it's the closest one I know about.

Cheers,
Bogdan



----- Original Message -----
From: "David Cramer" <dav...@br...>
To: <dox...@li...>
Sent: Tuesday, June 26, 2001 5:21 PM
Subject: RE: [Doxygen-users] Index/TOC entries in .chm files


Create an file named whatever you like (e.g. componentname.overview) in
the following format. The \htmlinclude command pulls in the content from
the html page verbatim (though there won't be any autolinking). I find
that if you make the name of the page (e.g. "naming" in "\page naming")
must not be the same as the base of any of your .html files. Poke around
in the Doxygen documentation under these command and you'll find the
info you need
(http://www.stack.nl/~dimitri/doxygen/commands.html#commands):

/*! \mainpage Internationalization Overview

\section intro Introduction
Internationalization is good.

\subsection topics Related Topics:
<ul>
<li> \ref collation
<li> \ref conversion
<li> \ref languagecodes
<li> \ref countrycodes
<li> \ref linking
<li> \ref naming
<li> \ref icudocmain
</ul>
*/

/*! \page naming Library Naming Conventions
\htmlinclude BroadJumpLibNaming.html
*/

/*! \page linking Linking
\htmlinclude BJIntlLinking.html
*/

/*! \page collation Collation Overview
\htmlinclude CollationOverview.html
*/

/*! \page conversion Conversion Overview
\htmlinclude ConversionOverview.html
*/

/*! \page languagecodes ISO 639 Language Codes
\htmlinclude ISO-639--Language-Codes.html
*/

/*! \page countrycodes ISO 3166 Country Codes
\htmlinclude ISO-3166--Country-Codes.html
*/


-David

> -----Original Message-----
> From: Gordian Elsinger [mailto:els...@is...]
> Sent: Tuesday, June 26, 2001 4:55 AM
> To: Doxygen Mailinglist
> Subject: [Doxygen-users] Index/TOC entries in .chm files
>
>
> Hi,
> when I add external HTML files to a doxygen help project I
> would also like
> to add index and TOC entries for the MS HTML help workshop
> referencing those
> files. Otherwise my external files can only be found either
> by direct links
> from the mainpage or by searching the help project.
> Is there an easy way to include those references (other than
> editing the
> .hhc and .hhk files by hand, which is not such a good idea
> for automatic
> build jobs)? Like a special command I have overlooked ;-)?
>
> Thanks,
> Gordian
>
>
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> http://lists.sourceforge.net/lists/listinfo/doxygen-users
>

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

RE: [Doxygen-users] Index/TOC entries in .chm files

[David C. <dav...@br...>]

Create an file named whatever you like (e.g. componentname.overview) in
the following format. The \htmlinclude command pulls in the content from
the html page verbatim (though there won't be any autolinking). I find
that if you make the name of the page (e.g. "naming" in "\page naming")
must not be the same as the base of any of your .html files. Poke around
in the Doxygen documentation under these command and you'll find the
info you need
(http://www.stack.nl/~dimitri/doxygen/commands.html#commands):

/*! \mainpage Internationalization Overview

	\section intro Introduction
	Internationalization is good.
=09
	\subsection topics Related Topics:
	<ul>
		<li> \ref collation
		<li> \ref conversion
		<li> \ref languagecodes
		<li> \ref countrycodes
		<li> \ref linking
		<li> \ref naming
		<li> \ref icudocmain
	</ul>
*/

/*! \page naming Library Naming Conventions
\htmlinclude BroadJumpLibNaming.html
*/

/*! \page linking Linking
\htmlinclude BJIntlLinking.html
*/

/*! \page collation Collation Overview
\htmlinclude CollationOverview.html
*/

/*! \page conversion Conversion Overview
\htmlinclude ConversionOverview.html
*/

/*! \page languagecodes ISO 639 Language Codes
\htmlinclude ISO-639--Language-Codes.html
*/

/*! \page countrycodes ISO 3166 Country Codes
\htmlinclude ISO-3166--Country-Codes.html
*/


-David

> -----Original Message-----
> From: Gordian Elsinger [mailto:els...@is...]
> Sent: Tuesday, June 26, 2001 4:55 AM
> To: Doxygen Mailinglist
> Subject: [Doxygen-users] Index/TOC entries in .chm files
>=20
>=20
> Hi,
> when I add external HTML files to a doxygen help project I=20
> would also like
> to add index and TOC entries for the MS HTML help workshop=20
> referencing those
> files. Otherwise my external files can only be found either=20
> by direct links
> from the mainpage or by searching the help project.
> Is there an easy way to include those references (other than=20
> editing the
> .hhc and .hhk files by hand, which is not such a good idea=20
> for automatic
> build jobs)? Like a special command I have overlooked ;-)?
>=20
> Thanks,
> Gordian
>=20
>=20
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> http://lists.sourceforge.net/lists/listinfo/doxygen-users
>=20

[Doxygen-users] Index/TOC entries in .chm files

[Gordian E. <els...@is...>]

Hi,
when I add external HTML files to a doxygen help project I would also like
to add index and TOC entries for the MS HTML help workshop referencing those
files. Otherwise my external files can only be found either by direct links
from the mainpage or by searching the help project.
Is there an easy way to include those references (other than editing the
.hhc and .hhk files by hand, which is not such a good idea for automatic
build jobs)? Like a special command I have overlooked ;-)?

Thanks,
Gordian

[Doxygen-users] Static members

[Proskuriakov, I. <Igo...@gs...>]

Hi,
Unfortunately I could not use search facilities of mailing list, so I do
apologies in advance if this question was already asked.
The question is: in Class Reference doxygen shows definition of static class
members, rather than declaration, is it a desired feature?
Example of doxygen output:

Static Protected Attributes
char* subjectName = new char[MAX_SUBJECT_LEN];

I would expect:

Static Protected Attributes 
char*  subjectName;

instead. Please comment,
Regards,
Igor Proskuriakov

 

[Doxygen-users] Searchable email list archive?

[Dan M. <dm...@Cr...>]

Is there a searchable and reasonably up-to-date archive of doxygen-users
somewhere? The GeoCrawler site's search functionality seems to be broken,
and clicking the "About" link gives me a message saying that GeoCrawler is
no longer being maintained.

---
Dan Muller
http://home.att.net/~dmuller

Re: [Doxygen-users] Grouping of reimplemented members (now with a patch)

[Johan E. <Joh...@ua...>]

Johan Eriksson wrote:
> 
> Hi,
>    grouping of reimplemented members derived from a pure virtual member
> doesn't seem to work, using versions 1.2.6 or 1.2.8.1 (other versions
> not tested).
> 
snip....

> This gives in the HTML output:
> 
> The module description of someGroupName contains only the pure virtual
> method and not the derived method.....
> 
> Have I documented the methods OK and if that's the case is it a bug?

In the CVS update dated 20010617 it is fixed.....thanks for the quick
response on that.
I've continued and fixed that it is possible to 'click' between
different implementations of the method, HTML output (it didn't work if
the method is assigned to a group).
A patch is attached for that....

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

Re: [Doxygen-users] Doxygen 2.0 (was Re: RTF questions; resend)

[<Gra...@Sy...>]

Hi Dimitri

     Would it be possible to provide a compiled (for Windows NT) version of
Doxygen with the -xmlgen feature switched on so I could have a look at the
xml it generates.  I'm fairly new to xml and xslt but my first impression
is the xslt is going to be very popular as it is extremely powerful and
fairly intuitive to use.

Thanks

Graham Smith



                                                                                                              
                    Dimitri van Heesch                                                                        
                    <di...@st...>                     To:     dox...@li...        
                    Sent by:                               cc:                                                
                    dox...@li...urc        Subject:     [Doxygen-users] Doxygen 2.0 (was Re:  
                    eforge.net                             RTF questions; resend)                             
                                                                                                              
                                                                                                              
                    20/06/2001 21:31                                                                          
                    Please respond to doxygen-users                                                           
                                                                                                              
                                                                                                              



On Tue, Jun 19, 2001 at 07:23:06PM -0400, Joe Ninety wrote:
>
> As an aside... I know that the plan is to move doxygen
> to where it generates an intermediate XML file, and then
> use a number of independent front-ends to format the XML
> in the target format (html, rtf, etc.).

Yes, that's still the idea.

>
> Is there any target date on when that will happen?

No date, but when it is ready it will be called doxygen 2.0.

The big plan towards 2.0 is:
- improve the way diagrams/hierarchies are displayed (for templates
mostly).
- merge the now separate XML generator back into doxygen.
- investigate if it makes sense to use schema's i.s.o. DTD's
- add much more information to the XML output
  (structured documentation, descriptions of the diagrams, etc.)
- provide front-ends for HTML and LaTeX
  (I expect/hope that other front-ends (including man and RTF) are
   provided and maintained people other than myself!)

In the meantime I try to handle any bug reports as well.

Regards,
  Dimitri

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






**********************************************************************
Symbian Ltd is a company registered in England and Wales with registered number 01796587 and registered office at 19 Harcourt Street, London, W1H 4HF, UK.
This message is intended only for use by the named addressee and may contain privileged and/or confidential information. If you are not the named addressee you should not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify pos...@sy... and delete the message and any attachments accompanying it immediately. Symbian does not accept liability for any corruption, interception, amendment, tampering or viruses occurring to this message in transit or for any message sent by its employees which is not in compliance with Symbian corporate policy.
**********************************************************************

RE: [Doxygen-users] Doxygen 2.0 (was Re: RTF questions; resend)

[Marshall, H. <hun...@vi...>]

> - provide front-ends for HTML and LaTeX
>   (I expect/hope that other front-ends (including man and RTF) are 
>    provided and maintained people other than myself!)

Doesn't that job become much easier once the material is in XML? I'm
thinking of XSLT et al. 

Note, I am not an XML expert, nor do I play one on TV.   :-)

	hunter

[Doxygen-users] Doxygen 2.0 (was Re: RTF questions; resend)

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

On Tue, Jun 19, 2001 at 07:23:06PM -0400, Joe Ninety wrote:
> 
> As an aside... I know that the plan is to move doxygen
> to where it generates an intermediate XML file, and then
> use a number of independent front-ends to format the XML 
> in the target format (html, rtf, etc.).

Yes, that's still the idea.

> 
> Is there any target date on when that will happen?

No date, but when it is ready it will be called doxygen 2.0.

The big plan towards 2.0 is: 
- improve the way diagrams/hierarchies are displayed (for templates mostly).
- merge the now separate XML generator back into doxygen.
- investigate if it makes sense to use schema's i.s.o. DTD's
- add much more information to the XML output
  (structured documentation, descriptions of the diagrams, etc.)
- provide front-ends for HTML and LaTeX
  (I expect/hope that other front-ends (including man and RTF) are 
   provided and maintained people other than myself!)

In the meantime I try to handle any bug reports as well.

Regards,
  Dimitri

RE: [Doxygen-users] RTF questions; resend

[CHUVALA, K. G. (JSC-D. (USA) <kei...@js...>]

Markus regarding your issue #1, we use \verbatim instead of <PRE> to work
around this.  Be advised, though, that we're concerned only with RTF output
here; I don't know what effect \verbatim has on HTML output.

kgc

___________________________________
Keith G. Chuvala
Space Operations Computing (SpOC) Team
Johnson Space Center
Houston, Texas, USA


> -----Original Message-----
> From: Mar...@no... [mailto:Mar...@no...]
> Sent: Tuesday, June 19, 2001 4:04 PM
> To: dox...@li...
> Subject: [Doxygen-users] RTF questions; resend
> 
> 
> Hi all,
> 
> is there really nobody with at least a tiny comment or tip?
> 
> BR, 
>  /Markus
> 
> PS: All questions below refer to DG 1.2.8
> 
> > -----Ursprungliche Nachricht-----
> > Von: ext Mar...@no... [mailto:Mar...@no...]
> > Gesendet: Donnerstag, 7. Juni 2001 10:58
> > An: dox...@li...
> > Betreff: [Doxygen-users] RTF questions
> > 
> > 
> > Hi Doxygeners!
> > 
> > Maybe you can help me solving following problems:
> > 
> > ## 1 ##
> > 
> > Suppose following header file comment:
> > 
> > /**
> > ...
> >  * <PRE>
> >  * -------------------    -----------------------    -------
> >  * | mem buf       1 |    | mem buf 2           |    | mb3 |
> >  * -------------------    -----------------------    -------
> >  * </PRE>
> > ...
> > */
> > 
> > In HTML output I get correct stuff:
> > 
> >    -------------------    -----------------------    -------
> >    | mem buf       1 |    | mem buf 2           |    | mb3 |
> >    -------------------    -----------------------    -------
> > 
> > 
> > But in RTF the output is as follows (with grey background):
> > 
> >  -------------------    -----------------------    ------- | 
> > mem buf       1
> > |    | mem buf 2           |    | mb3 | -------------------
> > -----------------------    ------- 
> > 
> > 
> > i.e. the linebreaks are not considered.
> > 
> > Any idea to solve this. (If I use <BR> in header the RTF 
> > output is ok, but
> > the HTML contains empty lines)
> > 
> > 
> > ## 2 ##
> > 
> > With 'doxygen -ertf RET_extension.txt' I can generate and RTF 
> > extension
> > file,
> > but how to get doxygen using the content when generating 
> RTF document?
> > 
> > 
> > ## 3 ##
> > Is there any way to tell m$-word to automatically update RTF 
> > file content
> > (simulate STRG-A, F9)?
> > 
> > 
> > Thanks a lot for any suggestion or tip!
> > 
> > BR,
> >  Markus Lepper
> > 
> > _______________________________________________
> > Doxygen-users mailing list
> > Dox...@li...
> > http://lists.sourceforge.net/lists/listinfo/doxygen-users
> > 
> 
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> http://lists.sourceforge.net/lists/listinfo/doxygen-users
> 

[Doxygen-users] RE: problem with class hierarchies with templates

[Don M. <dmc...@In...>]

"Hendrik Schober" <Do...@HS...> wrote:
> "Christoph Koegl" <ko...@in...> wrote:
>
> > [...] I am afraid that templates are somewhat on a back burner
> > since they are not heavily used by most developers. [...]
>
>   If this is the impression then we, who use templates,
>   have to change it! Templates _are_ used by many
>   developers! ;^>

Dan Muller <dm...@Cr...> wrote

>Agreed! Especially since good-quality implementations of the STL have
become
>available.

I'm mostly a lurker on this list, but I'll chime in here and say that I too
use templates and doxygen, and have struggled to get useful output for my
classes. Improvements here would be most welcome.

At the same time, I do appreciate Doxygen -- it's a great tool. Thanks
Dimitri.

Don

RE: [Doxygen-users] rtf stylesheets

[Philippe L. <Ph...@gm...>]

Marshall Hunter wrote:
> Does anyone have suggestions for learning about trying to use rtf
> stylesheets?

RTF 1.4 reference (101KB!):
http://www.logictran.com/RTF11405.htm
or on a more global level (content page):
http://www.logictran.com/RTF114_c.htm

This is actually a HTML version of a Microsoft document.

You can find an updated (1.5) version of this file, in Word format, at:
http://www.wotsit.org/search.asp?page=3&s=text

Of course, these are not really tutorial, rather reference documents, a bit
dry...
A search of "RTF stylesheet tutorial -CSS -XML -jade" in Google didn't gave
much signifiant result...
The same without "stylesheet" isn't better...

Note: I haven't read these documentes (yet) and I know nothing about RTF
format... So I can't answer any question (sorry Markus).

Regards.


-- 
--._.·´¯`·._.·´¯`·._.·´¯`·._.·´¯`·._.·´¯`·._.·´¯`·._.--
Philippe Lhoste (Paris -- France)
Professional programmer and amateur artist
http://jove.prohosting.com/~philho/
--´¯`·._.·´¯`·._.·´¯`·._.·´¯`·._.·´¯`·._.·´¯`·._.·´¯`--

Sent through GMX FreeMail - http://www.gmx.net

Re: [Doxygen-users] doxygen on AIX 4.3

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

dr...@ca... wrote:
> >
> > I get the following result when compiling doxygen on AIX aix 4.3.3  VAC++
> > V5:
> >
> > gmake[1]: Leaving directory `/home/dricard/tmp/doxygen-1.2.8.1/src'
> > /local/bin/gmake -f Makefile.libdoxygen all
> > gmake[1]: Entering directory `/home/dricard/tmp/doxygen-1.2.8.1/src'
> > xlC -c -+ -qstrict -D_BSD -O3 -I../qtools -o ../objects/ce_lex.o
> ce_lex.cpp
> > xlC -c -+ -qstrict -D_BSD -O3 -I../qtools -o ../objects/ce_parse.o
> > ce_parse.cpp
> > "ce_parse.cpp", line 940.11: 1540-0274 (S) The name lookup for
> "parseOctal"
> > did not find a declaration.
> 
>

Try editting cppvalue.h to add a declaration of parseOctal() outside of
the CPPValue class definition.

John

[Doxygen-users] brief command in conditional parts of the documentation

[Tobias Z. <Tob...@cw...>]

Hi,
did anyone ever try to use the "brief"-command in or with conditional
commands "if" and "endif"?
I tried the following:

/**
*   \if eng
*   @brief  Function for handling UDP errors.
*
*   \endif
*
*   \if ger
*   @brief  Funktion zur Behandlung von UDP-Fehlern.
*
*   \endif
*/
int UDP_err(int err_code);

but doxygen always puts both @brief discriptions into the documentation no
matter whether I
set ENABLED_SECTIONS to eng (x)or ger.

I'd really like to use the "brief"-command cause the project I'm trying to
document is quite complex. Did anyone here build multilingual dokumentation
using brief discription? Or does anyone know how to this problem?

Thanks,
	Tobias

---
Tobias Zimmer
Tob...@cw...

[Doxygen-users] rtf stylesheets

[Marshall, H. <hun...@vi...>]

Does anyone have suggestions for learning about trying to use rtf
stylesheets?

Thanks

	hunter

Re: [Doxygen-users] doxygen on AIX 4.3

[<dr...@ca...>]

did a  src/   "make distclean; make"

)-: didn't work.


//-----------------------------------
// Denis Ricard,  IBM Canada
//   dr...@ca...
//-----------------------------------


Dimitri van Heesch <di...@st...>@lists.sourceforge.net on 06/19/2001
02:10:54 AM

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

Sent by:  dox...@li...


To:   dox...@li...
cc:
Subject:  Re: [Doxygen-users] doxygen on AIX 4.3


On Mon, Jun 18, 2001 at 05:12:22PM -0400, dr...@ca... wrote:
> Did anyone successfully compile doxygen 1.2.7+ on AIX 4.3 ?
> What compiler version and machine type was used?
>
> I've tried doxygen 1.2.6 but it gave an "illegal instruction error" with
> two of my larger directories.
> I've finally decided to use VAC++ 5 but now, no doxygen version will
> compile.
>
> I get the following result when compiling doxygen on AIX aix 4.3.3  VAC++
> V5:
>
> gmake[1]: Leaving directory `/home/dricard/tmp/doxygen-1.2.8.1/src'
> /local/bin/gmake -f Makefile.libdoxygen all
> gmake[1]: Entering directory `/home/dricard/tmp/doxygen-1.2.8.1/src'
> xlC -c -+ -qstrict -D_BSD -O3 -I../qtools -o ../objects/ce_lex.o
ce_lex.cpp
> xlC -c -+ -qstrict -D_BSD -O3 -I../qtools -o ../objects/ce_parse.o
> ce_parse.cpp
> "ce_parse.cpp", line 940.11: 1540-0274 (S) The name lookup for
"parseOctal"
> did not find a declaration.

Maybe (just a wild guess) it would help if you let yacc regenerate the
ce_parse.cpp file. Just do a "make distclean ; make" in the src dir.

Regards,
  Dimitri


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

Re: [Doxygen-users] RTF questions; resend

[Joe N. <jo...@ho...>]

> > ## 2 ##
> >
> > With 'doxygen -ertf RET_extension.txt' I can generate and RTF
> > extension
> > file,
> > but how to get doxygen using the content when generating RTF document?

In the doxygen configuration file, you set a variable:

RTF_EXTENSIONS  = RET_extension.txt

(I'm working from memory, but I think that's the syntax.)

Don't have any answers for the other two questions you
had.


As an aside... I know that the plan is to move doxygen
to where it generates an intermediate XML file, and then
use a number of independent front-ends to format the XML 
in the target format (html, rtf, etc.).

Is there any target date on when that will happen?



joe90

RE: [Doxygen-users] document structure

[Marshall, H. <hun...@vi...>]

OK, replying to my own email is lame, but I wanted to inject something
before I get flamed for an ill-defined question or outright laziness.

I am experimenting with the "group" command. I think that is going to do the
coarse organiztion I'm looking for. I just now thought to look for an
example directory in the distribution, which has a nice group example.
(doh!)

So given that I see some solutions to experiment with, does anyone have any
keen lessons of experience to impart?

Thanks

	hunter


> -----Original Message-----
> From: Marshall, Hunter [mailto:hun...@vi...]
> Sent: Tuesday, June 19, 2001 2:46 PM
> To: 'dox...@li...'
> Subject: [Doxygen-users] document structure
> 
> 
> I have been using doxygen for browseable documentation, but 
> I'd like to
> create a printed document that is similar to a design 
> document (generated
> from a bunch of header files that contain the unpopulated
> classes/functions).
> 
> I haven't done much printing of dox. output. Is there a way 
> to play with the
> default organization? I suspect that use of the \page, \section, etc
> commands will be one way to control some aspect of the structure.
> 
> While I am busy experimenting, does anyone have any hints or 
> example files?
> How was the doxygen documentation itself written (was it in doxygen?).
> 
> Thanks
> 
> 	hunter
> 
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> http://lists.sourceforge.net/lists/listinfo/doxygen-users
> 

[Doxygen-users] document structure

[Marshall, H. <hun...@vi...>]

I have been using doxygen for browseable documentation, but I'd like to
create a printed document that is similar to a design document (generated
from a bunch of header files that contain the unpopulated
classes/functions).

I haven't done much printing of dox. output. Is there a way to play with the
default organization? I suspect that use of the \page, \section, etc
commands will be one way to control some aspect of the structure.

While I am busy experimenting, does anyone have any hints or example files?
How was the doxygen documentation itself written (was it in doxygen?).

Thanks

	hunter

[Doxygen-users] RTF questions; resend

[<Mar...@no...>]

Hi all,

is there really nobody with at least a tiny comment or tip?

BR,=20
 /Markus

PS: All questions below refer to DG 1.2.8

> -----Urspr=FCngliche Nachricht-----
> Von: ext Mar...@no... [mailto:Mar...@no...]
> Gesendet: Donnerstag, 7. Juni 2001 10:58
> An: dox...@li...
> Betreff: [Doxygen-users] RTF questions
>=20
>=20
> Hi Doxygeners!
>=20
> Maybe you can help me solving following problems:
>=20
> ## 1 ##
>=20
> Suppose following header file comment:
>=20
> /**
> ...
>  * <PRE>
>  * -------------------    -----------------------    -------
>  * | mem buf       1 |    | mem buf 2           |    | mb3 |
>  * -------------------    -----------------------    -------
>  * </PRE>
> ...
> */
>=20
> In HTML output I get correct stuff:
>=20
>    -------------------    -----------------------    -------
>    | mem buf       1 |    | mem buf 2           |    | mb3 |
>    -------------------    -----------------------    -------
>=20
>=20
> But in RTF the output is as follows (with grey background):
>=20
>  -------------------    -----------------------    ------- |=20
> mem buf       1
> |    | mem buf 2           |    | mb3 | -------------------
> -----------------------    -------=20
>=20
>=20
> i.e. the linebreaks are not considered.
>=20
> Any idea to solve this. (If I use <BR> in header the RTF=20
> output is ok, but
> the HTML contains empty lines)
>=20
>=20
> ## 2 ##
>=20
> With 'doxygen -ertf RET_extension.txt' I can generate and RTF=20
> extension
> file,
> but how to get doxygen using the content when generating RTF =
document?
>=20
>=20
> ## 3 ##
> Is there any way to tell m$-word to automatically update RTF=20
> file content
> (simulate STRG-A, F9)?
>=20
>=20
> Thanks a lot for any suggestion or tip!
>=20
> BR,
>  Markus Lepper
>=20
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> http://lists.sourceforge.net/lists/listinfo/doxygen-users
>=20

RE: [Doxygen-users] problem with class hierarchies with templates

[Dan M. <dm...@Cr...>]

"Hendrik Schober" <Do...@HS...> wrote:
> "Christoph Koegl" <ko...@in...> wrote:
> 
> > [...] I am afraid that templates are somewhat on a back burner
> > since they are not heavily used by most developers. [...] 
> 
>   If this is the impression then we, who use templates, 
>   have to change it! Templates _are_ used by many 
>   developers! ;^> 

Agreed! Especially since good-quality implementations of the STL have become
available.

[Doxygen-users] A couple of issues with output

[Bogdan I. <bo...@ne...>]

Hi,

First of all, thanks a lot to Dimitri for fixing the javadoc {@link}. I saw
it's been included in the latest changelog. Very quick turnaround on that
one. I really appreciate that.

I've seen two other small problems. They are illustrated by the example
below:

/**
 * A test class. <br>
 * Details.
 */
class Test
   {
public:
   /**
    * A character constant. Details.
    */
   static const char cOne;
   };

const char Test::cOne='t';


First, the value of Test::cOne is not included in the generated
documentation. The value is included for int or const char* const
constants. It looks like const chars don't behave the same way for some
reason.

Second, it's the problem with the <br> in the class docs. I use
BRIEF_MEMBER_DESC = YES
REPEAT_BRIEF = YES
JAVADOC_AUTOBRIEF = YES
to get a behavior as close as possible to the output of the javadoc tool.
I'm only interested in HTML docs generation.

With the javadoc tool, the detailed description is made up of all the docs,
including the brief description, all copied verbatim. For that reason, it's
quite common to include a <br> after the brief description, to put it on a
different line from the rest of the docs.

Doxygen inserts some <p> tags to separate the brief description from the
rest of the docs in the detailed description. Not a bad idea, actually, but
this gets combined with the <br> tag, and results in a large space being
inserted between the first line and the rest of the docs.

Could the insertion of <p> tags be made a configurable option, so that one
can use comments written for javadoc without modification?

Again, I can hardly classify these as serious problems, but I guess it
would be nice to have them sorted out.

Cheers,
Bogdan