doxygen-users — List for users of doxygen

Re: [Doxygen-users] Unknown Error

[Kjkazinski <kjk...@ya...>]

Art,

You can download Doxygen from the web site, both the binaries or the source.

Hope that helps




Sent from my ASUS Pad

Arthur Schwarz <asc...@at...> wrote:

><!--a:link 	{mso-style-priority:99;} span.MSOHYPERLINK 	{mso-style-priority:99;} a:visited 	{mso-style-priority:99;} span.MSOHYPERLINKFOLLOWED 	{mso-style-priority:99;} p.MSOACETATE 	{mso-style-priority:99;} li.MSOACETATE 	{mso-style-priority:99;} div.MSOACETATE 	{mso-style-priority:99;} span.BALLOONTEXTCHAR 	{mso-style-priority:99;} /* Font Definitions */ @font-face 	{font-family:Tahoma; 	panose-1:2 11 6 4 3 5 4 4 2 4;} @font-face 	{font-family:Calibri; 	panose-1:2 15 5 2 2 2 4 3 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal 	{margin:0in; 	margin-bottom:.0001pt; 	font-size:12.0pt; 	font-family:"Times New Roman";} a:link, span.MsoHyperlink 	{color:blue; 	text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed 	{color:blue; 	text-decoration:underline;} p.MsoAcetate, li.MsoAcetate, div.MsoAcetate 	{margin:0in; 	margin-bottom:.0001pt; 	font-size:8.0pt; 	font-family:Tahoma;} span.BalloonTextChar 	{font-family:Tahoma;} span.EmailStyle19 	{mso-style-type:personal; 	font-family:Arial; 	color:navy;} span.EmailStyle20 	{mso-style-type:personal; 	font-family:Calibri; 	color:#1F497D;} span.EmailStyle21 	{mso-style-type:personal-reply; 	font-family:Arial; 	color:navy;} @page Section1 	{size:8.5in 11.0in; 	margin:1.0in 1.25in 1.0in 1.25in;} div.Section1 	{page:Section1;} --> 
>
> 
>
>Well, I’ve given this some thought. Dmitri said that there are path issues when doxygen is compiled for unix and graphviz is compiled for Windows. That is (sigh and unfortunately) my issue. So, I am using Graphviz 2.30 for windows and doxygen 1.8.6 for cygwin. The paths are different, in particular, the paths used by doxygen are absolute (/cygdrive/…) and graphviz expects something like ‘C:/’. I don’t think that using backward slashes or forward slashes is an issue any more. The Windows gods seem to have given in to the inevitable and accepted forward slashes in paths.
>
> 
>
>Anyone know where I can get  a cygwin graphviz or a Windows doxygen?
>
> 
>
>art
>
>From: Stefan Kraxberger [mailto:ste...@nx...] 
>Sent: Friday, January 17, 2014 1:28 AM
>To: asc...@at...; kjk...@ya...
>Cc: dox...@li...
>Subject: RE: [Doxygen-users] Unknown Error
>
> 
>
>Hi,
>
> 
>
>I had the same problem. It happened when the amount of files exceeds the limit allowed by the OS (in my caseWindows). Because the DOT tool is generating new files at some point it is unable to create a new file in the folder due to this limitation and then you see this error. This was at least the cause in my situation. You can config doxygen to generate subfolders and then it will work again. 
>
> 
>
>Hope it helps,
>
>
>Stefan
>
> 
>
>From: Arthur Schwarz [mailto:asc...@at...] 
>Sent: Donnerstag, 16. Jänner 2014 18:18
>To: 'Ken Kazinski'
>Cc: dox...@li...
>Subject: Re: [Doxygen-users] Unknown Error
>
> 
>
>I do have DOT installed and it does work. I do generate an output HTML file with my documentation, but the file is incomplete. It does not contain all of my classes in the inheritance graph (showing all of my classes) and some of the individual classes do not have an inheritance graph when they should. I believe that the files which have failed are all those created in the last few months, but I’m not sure. In any case, I think the fault is with me, not doxygen, but I don’t know how to proceed to find it. In a word, I’m stumped.
>
> 
>
>The eventual product will be public domain (if I finish it in my lifetime). It’s available for anyone that wants to have a look. It consists of about 100 total files in a single directory, and about 18 – 19k lines of code with maybe 300 pages of documentation (unedited) embedded in the files.
>
> 
>
>From: Ken Kazinski [mailto:kjk...@ya...] 
>Sent: Thursday, January 16, 2014 9:08 AM
>To: Arthur Schwarz
>Cc: dox...@li...
>Subject: Re: [Doxygen-users] Unknown Error
>
> 
>
>Art,
>
> 
>
>It looks like DOT errors. Do you have Dot installed?  Is it in your path or in the doxyfile?
>
>Sent from my iPhone
>
>
>On Jan 16, 2014, at 11:29, Arthur Schwarz <asc...@at...> wrote:
>
>Win 7
>
>Doxygen 1.8.6 (cygwin)
>
> 
>
>I have errors generated by Doxygen and don't know how to fix them. Before I ran doxygen I deleted all generated subdirectories (rm -rf *). So execution ran on a clean slate. The errors seem to be generated by interface programs that Doxygen uses.
>
> 
>
>Thanks
>
>art
>
> 
>
>Here is a sample of each error.
>
> 
>
>Error: dot: can't open ReferenceManual/ReferenceManual/dd/d93/_slip_8_bison_8hpp__dep__incl.dot
>
> 
>
>error: Problems running dot: exit code=2, command='dot', arguments='"ReferenceManual/latex/d8/d77/position_8hh__dep__incl.dot" -Tpdf -o "ReferenceManual/latex/d8/d77/position_8hh__dep__incl.pdf"'
>
> 
>
> 
>
>Error: dot: can't open ReferenceManual/latex/d0/d85/_slip_8h__dep__incl.dot
>
> 
>
>error: Problems running dot: exit code=2, command='dot', arguments='"ReferenceManual/latex/d0/d85/_slip_8h__dep__incl.dot" -Tpdf -o "ReferenceManual/latex/d0/d85/_slip_8h__dep__incl.pdf"'
>
> 
>
> 
>
>Error: dot: can't open ReferenceManual/ReferenceManual/graph_legend.dot
>
>
>error: Problems running dot: exit code=2, command='dot', arguments='"ReferenceManual/ReferenceManual/graph_legend.dot" -Tpng -o "ReferenceManual/ReferenceManual/graph_legend.png"'
>
>------------------------------------------------------------------------------
>CenturyLink Cloud: The Leader in Enterprise Cloud Services.
>Learn Why More Businesses Are Choosing CenturyLink Cloud For
>Critical Workloads, Development Environments & Everything In Between.
>Get a Quote or Start a Free Trial Today. 
>http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
>
>_______________________________________________
>Doxygen-users mailing list
>Dox...@li...
>https://lists.sourceforge.net/lists/listinfo/doxygen-users
>

Re: [Doxygen-users] Unknown Error

[Arthur S. <asc...@at...>]

Thanks;

 

I've ignored common sense and relied on the cygwin release instead of going
to sourceforge.net or doxygen.org. 

 

art

 

  _____  

From: Ron Wilson [mailto:ron...@gm...] 
Sent: Friday, January 17, 2014 9:55 AM
To: doxygen-users
Subject: Re: [Doxygen-users] Unknown Error

 

On Fri, Jan 17, 2014 at 12:10 PM,
<dox...@li...> wrote:

Date: Fri, 17 Jan 2014 09:09:53 -0800
From: "Arthur Schwarz" <asc...@at...>

 

Well, I?ve given this some thought. Dmitri said that there are path issues
when doxygen is compiled for unix and graphviz is compiled for Windows. That
is (sigh and unfortunately) my issue. So, I am using Graphviz 2.30 for
windows and doxygen 1.8.6 for cygwin. The paths are different, in
particular, the paths used by doxygen are absolute (/cygdrive/?) and
graphviz expects something like ?C:/?. I don?t think that using backward
slashes or forward slashes is an issue any more. The Windows gods seem to
have given in to the inevitable and accepted forward slashes in paths.

 

Internally, Windows (and MS-DOS) has always accepted forward slashes in
paths. The problem is that CMD.EXE (and COMMAND.COM before it) uses forward
slash as an option introducer. As long as you can hide the slashes from
CMD.EXE, that won't be an issue.

CygWin vs Windows absolute path formats is a different issue. There are
works-around, but easiest to just get a Windows build of Doxygen from the
Doxygen website.

 

Anyone know where I can get  a cygwin graphviz or a Windows doxygen?

 

The Doxygen website has Windows builds of Doxygen.

PS, I started programming at the age of 5, so I'm not as ancient as this
post might make me seem.

Re: [Doxygen-users] Unknown Error

[Arthur S. <asc...@at...>]

Dmitri;

The issue is as you expected. I have a cygwin/unix doxygen and a Windows
graphviz (2.30). The absolute paths (/cygdrive/...) sent to graphviz are
rejected. Since I can't download a linux version of graphviz to a Windows
system, is there a Windows version of doxygen lying around?

I have extracted all the commands, removed absolute paths, and executed them
in a cygwin bash shell. No error messages were generated. Some classes in
the class list are not in the class hierarchy - no hierarchy graphs are
generated. Is there a reason for this?


art

PS: Thanks for the tip below.

-----Original Message-----
From: Dimitri van Heesch [mailto:do...@gm...] 
Sent: Thursday, January 16, 2014 12:20 PM
To: Arthur Schwarz
Cc: dox...@li...
Subject: Re: [Doxygen-users] Unknown Error

Hi Arthur,

Please set DOT_CLEANUP to NO in the config file and run doxygen from the
command line with the -d ExtCmd option.
Doxygen will then output the exact command with parameters it is trying to
execute.

For a failing command, try to execute it directly from the command line.
That may give some more insight on what is wrong
(e.g. maybe your version of dot doesn't have pdf output built in, or maybe
you are mixing a windows build of dot with a Cygwin build of doxygen and dot
cannot handle a cygwin-style path it is fed).

Regards,
  Dimitri

On 16 Jan 2014, at 17:29 , Arthur Schwarz <asc...@at...> wrote:

> Win 7
> Doxygen 1.8.6 (cygwin)
> 
> I have errors generated by Doxygen and don't know how to fix them. Before
I ran doxygen I deleted all generated subdirectories (rm -rf *). So
execution ran on a clean slate. The errors seem to be generated by interface
programs that Doxygen uses.
> 
> Thanks
> art
> 
> Here is a sample of each error.
> 
> Error: dot: can't open
ReferenceManual/ReferenceManual/dd/d93/_slip_8_bison_8hpp__dep__incl.dot
> 
> error: Problems running dot: exit code=2, command='dot',
arguments='"ReferenceManual/latex/d8/d77/position_8hh__dep__incl.dot" -Tpdf
-o "ReferenceManual/latex/d8/d77/position_8hh__dep__incl.pdf"'
> 
> 
> Error: dot: can't open
ReferenceManual/latex/d0/d85/_slip_8h__dep__incl.dot
> 
> error: Problems running dot: exit code=2, command='dot',
arguments='"ReferenceManual/latex/d0/d85/_slip_8h__dep__incl.dot" -Tpdf -o
"ReferenceManual/latex/d0/d85/_slip_8h__dep__incl.pdf"'
> 
> 
> Error: dot: can't open ReferenceManual/ReferenceManual/graph_legend.dot
> 
> error: Problems running dot: exit code=2, command='dot',
arguments='"ReferenceManual/ReferenceManual/graph_legend.dot" -Tpng -o
"ReferenceManual/ReferenceManual/graph_legend.png"'
> 
>
----------------------------------------------------------------------------
--
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today. 
>
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users

Re: [Doxygen-users] Unknown Error

[Ron W. <ron...@gm...>]

On Fri, Jan 17, 2014 at 12:10 PM, <
dox...@li...> wrote:

> Date: Fri, 17 Jan 2014 09:09:53 -0800
> From: "Arthur Schwarz" <asc...@at...>
>


> Well, I?ve given this some thought. Dmitri said that there are path issues
> when doxygen is compiled for unix and graphviz is compiled for Windows.
> That
> is (sigh and unfortunately) my issue. So, I am using Graphviz 2.30 for
> windows and doxygen 1.8.6 for cygwin. The paths are different, in
> particular, the paths used by doxygen are absolute (/cygdrive/?) and
> graphviz expects something like ?C:/?. I don?t think that using backward
> slashes or forward slashes is an issue any more. The Windows gods seem to
> have given in to the inevitable and accepted forward slashes in paths.
>

Internally, Windows (and MS-DOS) has always accepted forward slashes in
paths. The problem is that CMD.EXE (and COMMAND.COM before it) uses forward
slash as an option introducer. As long as you can hide the slashes from
CMD.EXE, that won't be an issue.

CygWin vs Windows absolute path formats is a different issue. There are
works-around, but easiest to just get a Windows build of Doxygen from the
Doxygen website.


> Anyone know where I can get  a cygwin graphviz or a Windows doxygen?
>

The Doxygen website has Windows builds of Doxygen.

PS, I started programming at the age of 5, so I'm not as ancient as this
post might make me seem.

Re: [Doxygen-users] Unknown Error

[Arthur S. <asc...@at...>]

 

Well, I’ve given this some thought. Dmitri said that there are path issues
when doxygen is compiled for unix and graphviz is compiled for Windows. That
is (sigh and unfortunately) my issue. So, I am using Graphviz 2.30 for
windows and doxygen 1.8.6 for cygwin. The paths are different, in
particular, the paths used by doxygen are absolute (/cygdrive/…) and
graphviz expects something like ‘C:/’. I don’t think that using backward
slashes or forward slashes is an issue any more. The Windows gods seem to
have given in to the inevitable and accepted forward slashes in paths.

 

Anyone know where I can get  a cygwin graphviz or a Windows doxygen?

 

art

  _____  

From: Stefan Kraxberger [mailto:ste...@nx...] 
Sent: Friday, January 17, 2014 1:28 AM
To: asc...@at...; kjk...@ya...
Cc: dox...@li...
Subject: RE: [Doxygen-users] Unknown Error

 

Hi,

 

I had the same problem. It happened when the amount of files exceeds the
limit allowed by the OS (in my caseWindows). Because the DOT tool is
generating new files at some point it is unable to create a new file in the
folder due to this limitation and then you see this error. This was at least
the cause in my situation. You can config doxygen to generate subfolders and
then it will work again. 

 

Hope it helps,


Stefan

 

From: Arthur Schwarz [mailto:asc...@at...] 
Sent: Donnerstag, 16. Jänner 2014 18:18
To: 'Ken Kazinski'
Cc: dox...@li...
Subject: Re: [Doxygen-users] Unknown Error

 

I do have DOT installed and it does work. I do generate an output HTML file
with my documentation, but the file is incomplete. It does not contain all
of my classes in the inheritance graph (showing all of my classes) and some
of the individual classes do not have an inheritance graph when they should.
I believe that the files which have failed are all those created in the last
few months, but I’m not sure. In any case, I think the fault is with me, not
doxygen, but I don’t know how to proceed to find it. In a word, I’m stumped.

 

The eventual product will be public domain (if I finish it in my lifetime).
It’s available for anyone that wants to have a look. It consists of about
100 total files in a single directory, and about 18 – 19k lines of code with
maybe 300 pages of documentation (unedited) embedded in the files.

 

  _____  

From: Ken Kazinski [mailto:kjk...@ya...] 
Sent: Thursday, January 16, 2014 9:08 AM
To: Arthur Schwarz
Cc: dox...@li...
Subject: Re: [Doxygen-users] Unknown Error

 

Art,

 

It looks like DOT errors. Do you have Dot installed?  Is it in your path or
in the doxyfile?

Sent from my iPhone


On Jan 16, 2014, at 11:29, Arthur Schwarz <asc...@at...> wrote:

Win 7

Doxygen 1.8.6 (cygwin)

 

I have errors generated by Doxygen and don't know how to fix them. Before I
ran doxygen I deleted all generated subdirectories (rm -rf *). So execution
ran on a clean slate. The errors seem to be generated by interface programs
that Doxygen uses.

 

Thanks

art

 

Here is a sample of each error.

 

Error: dot: can't open
ReferenceManual/ReferenceManual/dd/d93/_slip_8_bison_8hpp__dep__incl.dot

 

error: Problems running dot: exit code=2, command='dot',
arguments='"ReferenceManual/latex/d8/d77/position_8hh__dep__incl.dot" -Tpdf
-o "ReferenceManual/latex/d8/d77/position_8hh__dep__incl.pdf"'

 

 

Error: dot: can't open ReferenceManual/latex/d0/d85/_slip_8h__dep__incl.dot

 

error: Problems running dot: exit code=2, command='dot',
arguments='"ReferenceManual/latex/d0/d85/_slip_8h__dep__incl.dot" -Tpdf -o
"ReferenceManual/latex/d0/d85/_slip_8h__dep__incl.pdf"'

 

 

Error: dot: can't open ReferenceManual/ReferenceManual/graph_legend.dot


error: Problems running dot: exit code=2, command='dot',
arguments='"ReferenceManual/ReferenceManual/graph_legend.dot" -Tpng -o
"ReferenceManual/ReferenceManual/graph_legend.png"'

----------------------------------------------------------------------------
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431
<http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktr
k> &iu=/4140/ostg.clktrk

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

Re: [Doxygen-users] Unknown Error

[Arthur S. <asc...@at...>]

Any idea what option to use to change subfolders? I’ve searched my doxyfile
for folders and used the doxywizard tool with little success.

 

I did make a ‘typo’ in my problem. It appears that no graphic information
appears. No inheritance class nor anything else. Sigh. I’m a dead dude.

 

art

 

  _____  

From: Stefan Kraxberger [mailto:ste...@nx...] 
Sent: Friday, January 17, 2014 1:28 AM
To: asc...@at...; kjk...@ya...
Cc: dox...@li...
Subject: RE: [Doxygen-users] Unknown Error

 

Hi,

 

I had the same problem. It happened when the amount of files exceeds the
limit allowed by the OS (in my caseWindows). Because the DOT tool is
generating new files at some point it is unable to create a new file in the
folder due to this limitation and then you see this error. This was at least
the cause in my situation. You can config doxygen to generate subfolders and
then it will work again. 

 

Hope it helps,


Stefan

 

From: Arthur Schwarz [mailto:asc...@at...] 
Sent: Donnerstag, 16. Jänner 2014 18:18
To: 'Ken Kazinski'
Cc: dox...@li...
Subject: Re: [Doxygen-users] Unknown Error

 

I do have DOT installed and it does work. I do generate an output HTML file
with my documentation, but the file is incomplete. It does not contain all
of my classes in the inheritance graph (showing all of my classes) and some
of the individual classes do not have an inheritance graph when they should.
I believe that the files which have failed are all those created in the last
few months, but I’m not sure. In any case, I think the fault is with me, not
doxygen, but I don’t know how to proceed to find it. In a word, I’m stumped.

 

The eventual product will be public domain (if I finish it in my lifetime).
It’s available for anyone that wants to have a look. It consists of about
100 total files in a single directory, and about 18 – 19k lines of code with
maybe 300 pages of documentation (unedited) embedded in the files.

 

  _____  

From: Ken Kazinski [mailto:kjk...@ya...] 
Sent: Thursday, January 16, 2014 9:08 AM
To: Arthur Schwarz
Cc: dox...@li...
Subject: Re: [Doxygen-users] Unknown Error

 

Art,

 

It looks like DOT errors. Do you have Dot installed?  Is it in your path or
in the doxyfile?

Sent from my iPhone


On Jan 16, 2014, at 11:29, Arthur Schwarz <asc...@at...> wrote:

Win 7

Doxygen 1.8.6 (cygwin)

 

I have errors generated by Doxygen and don't know how to fix them. Before I
ran doxygen I deleted all generated subdirectories (rm -rf *). So execution
ran on a clean slate. The errors seem to be generated by interface programs
that Doxygen uses.

 

Thanks

art

 

Here is a sample of each error.

 

Error: dot: can't open
ReferenceManual/ReferenceManual/dd/d93/_slip_8_bison_8hpp__dep__incl.dot

 

error: Problems running dot: exit code=2, command='dot',
arguments='"ReferenceManual/latex/d8/d77/position_8hh__dep__incl.dot" -Tpdf
-o "ReferenceManual/latex/d8/d77/position_8hh__dep__incl.pdf"'

 

 

Error: dot: can't open ReferenceManual/latex/d0/d85/_slip_8h__dep__incl.dot

 

error: Problems running dot: exit code=2, command='dot',
arguments='"ReferenceManual/latex/d0/d85/_slip_8h__dep__incl.dot" -Tpdf -o
"ReferenceManual/latex/d0/d85/_slip_8h__dep__incl.pdf"'

 

 

Error: dot: can't open ReferenceManual/ReferenceManual/graph_legend.dot


error: Problems running dot: exit code=2, command='dot',
arguments='"ReferenceManual/ReferenceManual/graph_legend.dot" -Tpng -o
"ReferenceManual/ReferenceManual/graph_legend.png"'

----------------------------------------------------------------------------
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431
<http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktr
k> &iu=/4140/ostg.clktrk

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

Re: [Doxygen-users] Unknown Error

[Stefan K. <ste...@nx...>]

Hi,

 

I had the same problem. It happened when the amount of files exceeds the
limit allowed by the OS (in my caseWindows). Because the DOT tool is
generating new files at some point it is unable to create a new file in the
folder due to this limitation and then you see this error. This was at least
the cause in my situation. You can config doxygen to generate subfolders and
then it will work again. 

 

Hope it helps,


Stefan

 

From: Arthur Schwarz [mailto:asc...@at...] 
Sent: Donnerstag, 16. Jänner 2014 18:18
To: 'Ken Kazinski'
Cc: dox...@li...
Subject: Re: [Doxygen-users] Unknown Error

 

I do have DOT installed and it does work. I do generate an output HTML file
with my documentation, but the file is incomplete. It does not contain all
of my classes in the inheritance graph (showing all of my classes) and some
of the individual classes do not have an inheritance graph when they should.
I believe that the files which have failed are all those created in the last
few months, but I’m not sure. In any case, I think the fault is with me, not
doxygen, but I don’t know how to proceed to find it. In a word, I’m stumped.

 

The eventual product will be public domain (if I finish it in my lifetime).
It’s available for anyone that wants to have a look. It consists of about
100 total files in a single directory, and about 18 – 19k lines of code with
maybe 300 pages of documentation (unedited) embedded in the files.

 

  _____  

From: Ken Kazinski [mailto:kjk...@ya...] 
Sent: Thursday, January 16, 2014 9:08 AM
To: Arthur Schwarz
Cc: dox...@li...
Subject: Re: [Doxygen-users] Unknown Error

 

Art,

 

It looks like DOT errors. Do you have Dot installed?  Is it in your path or
in the doxyfile?

Sent from my iPhone


On Jan 16, 2014, at 11:29, Arthur Schwarz <asc...@at...> wrote:

Win 7

Doxygen 1.8.6 (cygwin)

 

I have errors generated by Doxygen and don't know how to fix them. Before I
ran doxygen I deleted all generated subdirectories (rm -rf *). So execution
ran on a clean slate. The errors seem to be generated by interface programs
that Doxygen uses.

 

Thanks

art

 

Here is a sample of each error.

 

Error: dot: can't open
ReferenceManual/ReferenceManual/dd/d93/_slip_8_bison_8hpp__dep__incl.dot

 

error: Problems running dot: exit code=2, command='dot',
arguments='"ReferenceManual/latex/d8/d77/position_8hh__dep__incl.dot" -Tpdf
-o "ReferenceManual/latex/d8/d77/position_8hh__dep__incl.pdf"'

 

 

Error: dot: can't open ReferenceManual/latex/d0/d85/_slip_8h__dep__incl.dot

 

error: Problems running dot: exit code=2, command='dot',
arguments='"ReferenceManual/latex/d0/d85/_slip_8h__dep__incl.dot" -Tpdf -o
"ReferenceManual/latex/d0/d85/_slip_8h__dep__incl.pdf"'

 

 

Error: dot: can't open ReferenceManual/ReferenceManual/graph_legend.dot


error: Problems running dot: exit code=2, command='dot',
arguments='"ReferenceManual/ReferenceManual/graph_legend.dot" -Tpng -o
"ReferenceManual/ReferenceManual/graph_legend.png"'

----------------------------------------------------------------------------
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431
<http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktr
k> &iu=/4140/ostg.clktrk

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

Re: [Doxygen-users] Problem running configure on Ubuntu 13.10 (saucy) 64-bit

[Peter R. <p.r...@sh...>]

Hi Dimitri

Thanks for the prompt reply.

You are right, of course. I have obviously downloaded the pre-built 
linux binary by mistake on my saucy box but managed to click on the 
right link from precise. Really dumb mistake - sorry!

(All this explains why there was only an install target in the makefile!)

Best wishes,

Peter


On 16/01/14 20:13, Dimitri van Heesch wrote:
> Hi Peter,
>
> Seems like you have the minimal configure script that is bundled with the binary version
> of doxygen for Linux. For compilation you need the one that comes with the source package.
>
> Regards,
>    Dimitri
>
> On 16 Jan 2014, at 20:15 , Peter Rockett <p.r...@sh...> wrote:
>
>> Hi
>>
>> I am trying to build doxygen on Ubuntu 13.10 (saucy) 64-bit but I seem
>> to be having problems even getting past the configure step.
>>
>> First, running ./configure --help gives:
>>
>> Usage: ./configure [--help] [--prefix dir] [--install name]
>>
>> Options:
>>
>>    --help                Print this help
>>
>>    --prefix dir          Installation prefix directory
>>                          [default: /usr/local]
>>
>>    --install name        Use `name' as the name of the GNU install tool
>>                          [default: install]
>>
>> ... and that is it!
>>
>> When I try running ./configure I get:
>>
>>    Checking for GNU install tool... using /usr/bin/install
>>    Created Makefile from Makefile.in...
>>
>> ...and again, that's it! The makefile is suspiciously short, only 19
>> lines with an install target.
>>
>> I think I have all the prerequisites installed.
>>
>> I have also run the same on 32-bit Ubuntu 12.04 and it all works fine.
>> In particular, ./configure --help gives the full set of options, and the
>> makefile is good - it subsequently builds OK.
>>
>> Any help much appreciated.
>>
>> Peter
>>
>> ------------------------------------------------------------------------------
>> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
>> Learn Why More Businesses Are Choosing CenturyLink Cloud For
>> Critical Workloads, Development Environments & Everything In Between.
>> Get a Quote or Start a Free Trial Today.
>> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Doxygen-users mailing list
>> Dox...@li...
>> https://lists.sourceforge.net/lists/listinfo/doxygen-users

Re: [Doxygen-users] Unknown Error

[Dimitri v. H. <do...@gm...>]

Hi Arthur,

Please set DOT_CLEANUP to NO in the config file and run doxygen from the command line with the -d ExtCmd option.
Doxygen will then output the exact command with parameters it is trying to execute.

For a failing command, try to execute it directly from the command line. That may give some more insight on what is wrong
(e.g. maybe your version of dot doesn't have pdf output built in, or maybe you are mixing a windows build of dot with a Cygwin build of doxygen and dot cannot handle a cygwin-style path it is fed).

Regards,
  Dimitri

On 16 Jan 2014, at 17:29 , Arthur Schwarz <asc...@at...> wrote:

> Win 7
> Doxygen 1.8.6 (cygwin)
> 
> I have errors generated by Doxygen and don't know how to fix them. Before I ran doxygen I deleted all generated subdirectories (rm -rf *). So execution ran on a clean slate. The errors seem to be generated by interface programs that Doxygen uses.
> 
> Thanks
> art
> 
> Here is a sample of each error.
> 
> Error: dot: can't open ReferenceManual/ReferenceManual/dd/d93/_slip_8_bison_8hpp__dep__incl.dot
> 
> error: Problems running dot: exit code=2, command='dot', arguments='"ReferenceManual/latex/d8/d77/position_8hh__dep__incl.dot" -Tpdf -o "ReferenceManual/latex/d8/d77/position_8hh__dep__incl.pdf"'
> 
> 
> Error: dot: can't open ReferenceManual/latex/d0/d85/_slip_8h__dep__incl.dot
> 
> error: Problems running dot: exit code=2, command='dot', arguments='"ReferenceManual/latex/d0/d85/_slip_8h__dep__incl.dot" -Tpdf -o "ReferenceManual/latex/d0/d85/_slip_8h__dep__incl.pdf"'
> 
> 
> Error: dot: can't open ReferenceManual/ReferenceManual/graph_legend.dot
> 
> error: Problems running dot: exit code=2, command='dot', arguments='"ReferenceManual/ReferenceManual/graph_legend.dot" -Tpng -o "ReferenceManual/ReferenceManual/graph_legend.png"'
> 
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today. 
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk_______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users

Re: [Doxygen-users] Problem running configure on Ubuntu 13.10 (saucy) 64-bit

[Dimitri v. H. <do...@gm...>]

Hi Peter,

Seems like you have the minimal configure script that is bundled with the binary version
of doxygen for Linux. For compilation you need the one that comes with the source package.

Regards,
  Dimitri

On 16 Jan 2014, at 20:15 , Peter Rockett <p.r...@sh...> wrote:

> Hi
> 
> I am trying to build doxygen on Ubuntu 13.10 (saucy) 64-bit but I seem 
> to be having problems even getting past the configure step.
> 
> First, running ./configure --help gives:
> 
> Usage: ./configure [--help] [--prefix dir] [--install name]
> 
> Options:
> 
>   --help                Print this help
> 
>   --prefix dir          Installation prefix directory
>                         [default: /usr/local]
> 
>   --install name        Use `name' as the name of the GNU install tool
>                         [default: install]
> 
> ... and that is it!
> 
> When I try running ./configure I get:
> 
>   Checking for GNU install tool... using /usr/bin/install
>   Created Makefile from Makefile.in...
> 
> ...and again, that's it! The makefile is suspiciously short, only 19 
> lines with an install target.
> 
> I think I have all the prerequisites installed.
> 
> I have also run the same on 32-bit Ubuntu 12.04 and it all works fine. 
> In particular, ./configure --help gives the full set of options, and the 
> makefile is good - it subsequently builds OK.
> 
> Any help much appreciated.
> 
> Peter
> 
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today. 
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users

Re: [Doxygen-users] Problem running configure on Ubuntu 13.10 (saucy) 64-bit

[Albert <alb...@gm...>]

Peter,

This is indeed very short, also the output of the ./configure --help is a
bit strange and short.
Which version are you trying (versions numbers should be in the beginning
of the configure file)?

Albert


On Thu, Jan 16, 2014 at 8:15 PM, Peter Rockett <p.r...@sh...>wrote:

> Hi
>
> I am trying to build doxygen on Ubuntu 13.10 (saucy) 64-bit but I seem
> to be having problems even getting past the configure step.
>
> First, running ./configure --help gives:
>
> Usage: ./configure [--help] [--prefix dir] [--install name]
>
> Options:
>
>    --help                Print this help
>
>    --prefix dir          Installation prefix directory
>                          [default: /usr/local]
>
>    --install name        Use `name' as the name of the GNU install tool
>                          [default: install]
>
> ... and that is it!
>
> When I try running ./configure I get:
>
>    Checking for GNU install tool... using /usr/bin/install
>    Created Makefile from Makefile.in...
>
> ...and again, that's it! The makefile is suspiciously short, only 19
> lines with an install target.
>
> I think I have all the prerequisites installed.
>
> I have also run the same on 32-bit Ubuntu 12.04 and it all works fine.
> In particular, ./configure --help gives the full set of options, and the
> makefile is good - it subsequently builds OK.
>
> Any help much appreciated.
>
> Peter
>
>
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>

[Doxygen-users] Problem running configure on Ubuntu 13.10 (saucy) 64-bit

[Peter R. <p.r...@sh...>]

Hi

I am trying to build doxygen on Ubuntu 13.10 (saucy) 64-bit but I seem 
to be having problems even getting past the configure step.

First, running ./configure --help gives:

Usage: ./configure [--help] [--prefix dir] [--install name]

Options:

   --help                Print this help

   --prefix dir          Installation prefix directory
                         [default: /usr/local]

   --install name        Use `name' as the name of the GNU install tool
                         [default: install]

... and that is it!

When I try running ./configure I get:

   Checking for GNU install tool... using /usr/bin/install
   Created Makefile from Makefile.in...

...and again, that's it! The makefile is suspiciously short, only 19 
lines with an install target.

I think I have all the prerequisites installed.

I have also run the same on 32-bit Ubuntu 12.04 and it all works fine. 
In particular, ./configure --help gives the full set of options, and the 
makefile is good - it subsequently builds OK.

Any help much appreciated.

Peter

Re: [Doxygen-users] #include causes an error.

[Arthur S. <asc...@at...>]

Nope, but I will.

 

thanks

 

  _____  

From: Albert [mailto:alb...@gm...] 
Sent: Thursday, January 16, 2014 10:19 AM
To: Arthur Schwarz
Cc: dox...@li...
Subject: Re: [Doxygen-users] #include causes an error.

 

Art,

Did you have a look at \code, \verbatim, or try \# or `#include`

Albert

 

On Thu, Jan 16, 2014 at 5:32 PM, Arthur Schwarz <asc...@at...>
wrote:

In my documentation I have:

 

 * #include

 

repeated several times. On each occurrence I get:

 

   SlipRead.h:37: warning: explicit link request to 'include' could not be
resolved

 

Is there any way to escape the # or disable the error indication?

 

Thanks

art


----------------------------------------------------------------------------
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431
<http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktr
k> &iu=/4140/ostg.clktrk
_______________________________________________
Doxygen-users mailing list
Dox...@li...
https://lists.sourceforge.net/lists/listinfo/doxygen-users

 

Re: [Doxygen-users] #include causes an error.

[Albert <alb...@gm...>]

Art,

Did you have a look at \code, \verbatim, or try \# or `#include`

Albert


On Thu, Jan 16, 2014 at 5:32 PM, Arthur Schwarz <asc...@at...>wrote:

> In my documentation I have:
>
>  * #include
>
> repeated several times. On each occurrence I get:
>
>    SlipRead.h:37: warning: explicit link request to 'include' could not be
> resolved
>
> Is there any way to escape the # or disable the error indication?
>
> Thanks
> art
>
>
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>
>

Re: [Doxygen-users] Unknown Error

[Arthur S. <asc...@at...>]

I do have DOT installed and it does work. I do generate an output HTML file
with my documentation, but the file is incomplete. It does not contain all
of my classes in the inheritance graph (showing all of my classes) and some
of the individual classes do not have an inheritance graph when they should.
I believe that the files which have failed are all those created in the last
few months, but I'm not sure. In any case, I think the fault is with me, not
doxygen, but I don't know how to proceed to find it. In a word, I'm stumped.

 

The eventual product will be public domain (if I finish it in my lifetime).
It's available for anyone that wants to have a look. It consists of about
100 total files in a single directory, and about 18 - 19k lines of code with
maybe 300 pages of documentation (unedited) embedded in the files.

 

  _____  

From: Ken Kazinski [mailto:kjk...@ya...] 
Sent: Thursday, January 16, 2014 9:08 AM
To: Arthur Schwarz
Cc: dox...@li...
Subject: Re: [Doxygen-users] Unknown Error

 

Art,

 

It looks like DOT errors. Do you have Dot installed?  Is it in your path or
in the doxyfile?

Sent from my iPhone


On Jan 16, 2014, at 11:29, Arthur Schwarz <asc...@at...> wrote:

Win 7

Doxygen 1.8.6 (cygwin)

 

I have errors generated by Doxygen and don't know how to fix them. Before I
ran doxygen I deleted all generated subdirectories (rm -rf *). So execution
ran on a clean slate. The errors seem to be generated by interface programs
that Doxygen uses.

 

Thanks

art

 

Here is a sample of each error.

 

Error: dot: can't open
ReferenceManual/ReferenceManual/dd/d93/_slip_8_bison_8hpp__dep__incl.dot

 

error: Problems running dot: exit code=2, command='dot',
arguments='"ReferenceManual/latex/d8/d77/position_8hh__dep__incl.dot" -Tpdf
-o "ReferenceManual/latex/d8/d77/position_8hh__dep__incl.pdf"'

 

 

Error: dot: can't open ReferenceManual/latex/d0/d85/_slip_8h__dep__incl.dot

 

error: Problems running dot: exit code=2, command='dot',
arguments='"ReferenceManual/latex/d0/d85/_slip_8h__dep__incl.dot" -Tpdf -o
"ReferenceManual/latex/d0/d85/_slip_8h__dep__incl.pdf"'

 

 

Error: dot: can't open ReferenceManual/ReferenceManual/graph_legend.dot


error: Problems running dot: exit code=2, command='dot',
arguments='"ReferenceManual/ReferenceManual/graph_legend.dot" -Tpng -o
"ReferenceManual/ReferenceManual/graph_legend.png"'

----------------------------------------------------------------------------
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431
<http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktr
k> &iu=/4140/ostg.clktrk

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

Re: [Doxygen-users] Unknown Error

[Ken K. <kjk...@ya...>]

Art,

It looks like DOT errors. Do you have Dot installed?  Is it in your path or in the doxyfile?

Sent from my iPhone

> On Jan 16, 2014, at 11:29, Arthur Schwarz <asc...@at...> wrote:
> 
> Win 7
> Doxygen 1.8.6 (cygwin)
> 
> I have errors generated by Doxygen and don't know how to fix them. Before I ran doxygen I deleted all generated subdirectories (rm -rf *). So execution ran on a clean slate. The errors seem to be generated by interface programs that Doxygen uses.
> 
> Thanks
> art
> 
> Here is a sample of each error.
> 
> Error: dot: can't open ReferenceManual/ReferenceManual/dd/d93/_slip_8_bison_8hpp__dep__incl.dot
> 
> error: Problems running dot: exit code=2, command='dot', arguments='"ReferenceManual/latex/d8/d77/position_8hh__dep__incl.dot" -Tpdf -o "ReferenceManual/latex/d8/d77/position_8hh__dep__incl.pdf"'
> 
> 
> Error: dot: can't open ReferenceManual/latex/d0/d85/_slip_8h__dep__incl.dot
> 
> error: Problems running dot: exit code=2, command='dot', arguments='"ReferenceManual/latex/d0/d85/_slip_8h__dep__incl.dot" -Tpdf -o "ReferenceManual/latex/d0/d85/_slip_8h__dep__incl.pdf"'
> 
> 
> Error: dot: can't open ReferenceManual/ReferenceManual/graph_legend.dot
> 
> error: Problems running dot: exit code=2, command='dot', arguments='"ReferenceManual/ReferenceManual/graph_legend.dot" -Tpng -o "ReferenceManual/ReferenceManual/graph_legend.png"'
> 
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today. 
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users

[Doxygen-users] #include causes an error.

[Arthur S. <asc...@at...>]

In my documentation I have:

 * #include

repeated several times. On each occurrence I get:

   SlipRead.h:37: warning: explicit link request to 'include' could not be resolved

Is there any way to escape the # or disable the error indication?

Thanks
art

[Doxygen-users] Wrong line numbers for certain error messages

[Arthur S. <asc...@at...>]

For <\b> errors and "End of list marker" errors the line number is incorrect.Is there any way (in a future release) to output correct line numbers? By the way, what is an "End of list marker"? Is it </ul> or </li>?


The messages are:
SlipReader.h:1077: warning: found </b> tag without matching <b>
SlipSequencer.cpp:651: warning: End of list marker found without any preceding list items

1077 is 200+ lines after the end of file and 651 is about 1/3 into the file.


Thanks
art

[Doxygen-users] Unknown Error

[Arthur S. <asc...@at...>]

Win 7
Doxygen 1.8.6 (cygwin)


I have errors generated by Doxygen and don't know how to fix them. Before I ran doxygen I deleted all generated subdirectories (rm -rf *). So execution ran on a clean slate. The errors seem to be generated by interface programs that Doxygen uses.

Thanks
art

Here is a sample of each error.


Error: dot: can't open ReferenceManual/ReferenceManual/dd/d93/_slip_8_bison_8hpp__dep__incl.dot

error: Problems running dot: exit code=2, command='dot', arguments='"ReferenceManual/latex/d8/d77/position_8hh__dep__incl.dot" -Tpdf -o "ReferenceManual/latex/d8/d77/position_8hh__dep__incl.pdf"'


Error: dot: can't open ReferenceManual/latex/d0/d85/_slip_8h__dep__incl.dot

error: Problems running dot: exit code=2, command='dot', arguments='"ReferenceManual/latex/d0/d85/_slip_8h__dep__incl.dot" -Tpdf -o "ReferenceManual/latex/d0/d85/_slip_8h__dep__incl.pdf"'


Error: dot: can't open ReferenceManual/ReferenceManual/graph_legend.dot

error: Problems running dot: exit code=2, command='dot', arguments='"ReferenceManual/ReferenceManual/graph_legend.dot" -Tpng -o "ReferenceManual/ReferenceManual/graph_legend.png"'

[Doxygen-users] support explicit link to entities within current scope

[Peter A. B. <pa...@pa...>]

tl;dr: Propose that a prefixed hash (like #classname) express an 
explicit link without also changing the context to global scope.

Details:

The automatic link generation documentation describes how to reference 
documented entities based on their type; e.g. for a function foo one may 
use any of seven options including foo(). Words that are not entirely 
lower case and that match a class name are automatically linked unless 
prefixed by percent (%notaclass).

In the C++ style I'm using class names are all lower case.  Some of 
these appear in namespaces.  The bare forms of these names aren't 
recognized, and so links are not created.

Historically I've worked around this outside namespace using #classname, 
interpreting the hash as a general indication of "make this a link 
reference" (I've used this in C code to reference defines, for example, 
and it's sanctioned in the automatic link generation documentation for 
similar uses).

However, this approach doesn't work when the link target is inside the 
current namespace.  The only solution I've found is to explicitly 
specify the full namespace in each reference in the documentation, which 
is verbose and tedious.

It turns out that when src/docparser:handleLinkedWord() invokes 
resolveRef() the latter function unconditionally substitutes :: for # 
when forming the name that is resolved.  The change I propose is that it 
do this only for hash marks that appear internal to the name, and that 
it instead strip a leading hash mark from the name for the purposes of 
locating the reference. (Due to the way the code is structured, the hash 
mark remains present when checking for all-lower case tokens, so the 
link is generated using the appropriate context.)

I've submitted a pull request with the necessary patch as: 
https://github.com/doxygen/doxygen/pull/97

(I'd be happy to put all this into a bug report, but I can't find where 
those go now.  The SourceForge bug database appears to have disappeared 
with the project update, and github tickets aren't enabled.)

Below is the test input used to validate the change.

Peter

/** @file
  *
  * Reference no-hash tclass, hash #tclass, ns::nstclass, ns::NSTClass
  */

/** The class without namespace */
class tclass {
public:
   /** The member in #tclass
    *
    * Reference no-hash tclass, hash #tclass, ns::nstclass, ns::NSTClass
    */
   int member;
};

/** The capitalized class without namespace
  *
  * Reference no-hash tclass, hash #tclass, ns::nstclass, ns::NSTClass
  */
class TClass {
public:
   /** The parameter in TClass
    *
    * Reference no-hash tclass, hash #tclass, ns::nstclass, ns::NSTClass
    */
   int member;
};

/** A global function
  *
  * Reference no-hash tclass, hash #tclass, ns::nstclass, ns::NSTClass
  */
void ignoreme ();

/** The namespace */
namespace ns {

/** An override tclass in namespace
  * Reference no-hash tclass, hash #tclass, unqualified nstclass (hashed 
#nstclass) and NSTClass, qualified ns::nstclass, ns::NSTClass
  */
class tclass {
};

/** The namespaced class
  *
  * Reference no-hash tclass, hash #tclass, unqualified nstclass (hashed 
#nstclass) and NSTClass, qualified ns::nstclass, ns::NSTClass
  */
class nstclass {
public:
   /** The member in #nstclass
    *
    * Reference no-hash tclass, hash #tclass, unqualified nstclass 
(hashed #nstclass) and NSTClass, qualified ns::nstclass, ns::NSTClass
    */
   int member;
};

/** The namespaced capitalized class
  *
  * Reference no-hash tclass, hash #tclass, unqualified nstclass (hashed 
#nstclass) and NSTClass, qualified ns::nstclass, ns::NSTClass
  */
class NSTClass {
public:
   /** The member in NSTClass
    *
    * Reference no-hash tclass, hash #tclass, unqualified nstclass 
(hashed #nstclass) and NSTClass, qualified ns::nstclass, ns::NSTClass
    */
   int member;
};

/** A namespace function.
  *
  * Reference no-hash tclass, hash #tclass, unqualified nstclass (hashed 
#nstclass) and NSTClass, qualified ns::nstclass, ns::NSTClass
  */
void nsignoreme ();

} // ns

[Doxygen-users] Parsing of //*/

[Jano S. <jan...@gm...>]

Hi,

it seems that 1.8.6 broke parsing of the following comment type:

/*!

//*/

MS VC parses it properly - it ignores // and  */ ends the comment. I think
that 1.8.5 did it the same
way (though I'm not sure, I didn't check the generated documents).
1.8.4.did it that way for sure.

It causes that some documentation is not generated. With git master, this
additionally causes warning (/* without ending */ or something similar) (We
generate our docs in windows, I could only check git master in linux, so I
didn't generate all docs with gitmaster).

I will remove this construct from the sources, so it's not a problem for
me. I just wanted to let you know about this issue.

...don't ask me why is it there ;)

Thanks for the great program!

Jano

Re: [Doxygen-users] The lowercase problem when using the Doxygen with Fortran

[michael.lee.rilee <mi...@ri...>]

We're using Doxygen for  pFUnit <http://pfunit.sourceforge.net>  , a
unit-testing framework for Fortran.  For our coding convention, we
extensively use CamelCase.  Forcing the text to lowercase in both the URL
and the display text makes the documentation inconsistent with the code and
much harder to read.

We'd much prefer to have the displayed text (that also shows up in the
generated documentation) respect the coding convention in the source.  It
seems to me that the URL links could use any appropriately unique and
indexable naming scheme.  Such should support mixed-case languages as well.

At present, we're staying at 1.7.x to generate our docs until this is fixed.

Mike


Albert_1 wrote
> Dear Aziz,
> 
> In version 1.7.4 the links were not correct when having a subroutine
> getX and a call getx
> 
> Albert
> 
> On Sat, Sep 29, 2012 at 8:06 PM, aziz &lt;

> aziz.nantha@

> &gt; wrote:
>> Thank you Albert. But there is no problem in Doxygen version 1.7.4.
>> Currently, I use version 1.8.1.1.
>>
>> Aziz.
>>
>>
>>
>> On 9/29/12 10:48 AM, "Albert" &lt;

> albert.tests@

> &gt; wrote:
>>
>>>Hi Aziz,
>>>
>>>Fortran is a case insensitive language and therefor a lot of names
>>>etc. are converted to lowercase to make it possible to make hyperlinks
>>>etc.
>>>
>>>The only solution would be to convert the search strategy for
>>>hyperlinks etc, but you will have problems e.g. when having mixed
>>>language programming.
>>>
>>>At the moment there is no solution for this "problem"
>>>
>>>Albert
>>>





--
View this message in context: http://doxygen.10944.n7.nabble.com/The-lowercase-problem-when-using-the-Doxygen-with-Fortran-tp1243p6464.html
Sent from the Doxygen - Users mailing list archive at Nabble.com.

[Doxygen-users] Issue with 2 header files for one source file

[Stefan K. <ste...@nx...>]

Hi,

 

I have two different header files, one containing the public and on the
internal function prototypes. There are several functions in the "internal"
header file containing some documentation. In the source file there is some
additional documentation for the same functions. But the documentation from
the source file is ignored.

 

I also used \fn to explicitly mark the documentation in the header file to
assign it to the correct function.

 

The functions which have this issue are static. I have other static methods
with the same separation of the documentation (but only with one header and
one source file) where it works. EXTRACT_STATIC is therefore working
properly. If I remove the static keyword for the function it works.

 

What am I missing?

 

Best Regards,

 

Stefan Kraxberger

[Doxygen-users] Documenting property and it's get method with same name

[mitrich <pro...@ma...>]

I have Q_PROPERTY named "count" and method for this property, named "int
count()". When I'm trying to document "int count()" method, it's
documentation added to property documentation. Is it possible to document
"count" property and "int count()" method separately?

Best regards,

Mitrich



--
View this message in context: http://doxygen.10944.n7.nabble.com/Documenting-property-and-it-s-get-method-with-same-name-tp6462.html
Sent from the Doxygen - Users mailing list archive at Nabble.com.

Re: [Doxygen-users] How to generate an Appendix page

[Stefan H. <hei...@ho...>]

 

On Fri, Jan 10, 2014 at 3:14 AM,  <dox...@li...> wrote:


Date: Fri, 10 Jan 2014 09:08:44 +0100

From: Stefan Heiss <hei...@ho...>

Subject: [Doxygen-users] How to generate an Appendix page

To: "dox...@li..."

        <dox...@li...>

Message-ID: <COL...@ph...l>

Content-Type: text/plain; charset="iso-8859-1"



Is there an official way to generate an doxygen page and move it in the Appendix. I'm currently thinking about patching the refman.tex Output from doxygen in such a way that it will include an Appendix, and move some pages therein. Basically, that works with a few awk/grep/sed lines of code. However, it will just be a proprietary solution, and furthermore, just for LATEX.




However, I would Need it also for HTML Output, where I have no Idee how to do it there, yet. And, moreover, it has the further disadvantage, that with new doxygen Versions this Approach may Need to be adjusted over and over again.




So, I would like to know how other doxygen users are coming around this shortage?



Additionally, I would like to suggest a new doxygen command:

@appendixpage

which basically works similar to the @page command. However, the generated page will be put into an Appendix instead of the normal page place.

 I think you could do what you want by creating a custom "DoxygenLayout.xml". See the "Customizing the Output" section of the doxygen documentation.


I think adding the following might do what you want:

     <tab type="user" url="@ref appendix" title="Appendix"/>


Then create a "@page appendix Appendix" page and use "@subpage" inside that to organize your appendix pages.   Hi Ron, I've tried your proposal using the "DoxygenLayout.xml". For HTML Output this seems to work fine as Long as it is a normal @page generated page. However, html Output gets duplicated when it is a cross-referenced-list generated page. Moreover, for LATEX Output the <navindex></navindex> customisation seems to have no Impact. 
Is there a solution covering all possible Doxygen Outputs, or at least HTML and LATEX?If there isn't, a future doxygen improvement migth include an @appendixpage tag, or could possible considere the DoxygenLayout.xml/navindex also for the LATEX Output. -Stefan



------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Doxygen-users mailing list
Dox...@li...
https://lists.sourceforge.net/lists/listinfo/doxygen-users