doxygen-users — List for users of doxygen

[Doxygen-users] Globar var with c'tor args seen as function

[Barnes, P. D. <bar...@ll...>]

Hello Folks,

I’ve got a global variable initialized with c’tor arguments:
    int globalVar(1);

Doxygen gives a warning: return type is not documented, which I can’t figure out how to fix.

My Doxyfile differs from the default only one significant item:

$ doxygen -x Doxyfile
# Difference with default Doxyfile 1.14.0
WARN_NO_PARAMDOC       = yes
INPUT                  = src

Any help would be greatly appreciated.
Peter
_____________________________________________________________

Dr. Peter D. Barnes, Jr.   (he,him)                         CASC Division, B451 R2035
Lawrence Livermore National Laboratory          Computation Directorate
7000 East Avenue, L-561                                       email:  pdb...@ll...<mailto:pdb...@ll...>
P. O. Box 808                                                           Voice:  (925) 422-3384
Livermore, California 94550

[Doxygen-users] build doxygen from source without python (OpenBSD system)?

[Doug M. <dou...@ya...>]

I am trying to compile doxygen,
on a system with OpenBSD amd64
in order to document projects in C.

OpenBSD does not have python in the basic build.
(It also does not have CMake, but there is a prebuild package for that that is small,
with only a handful of additional dependencies.) 

Is there any way to build/compile doxygen without having python installed?
In the doxygen/src directory, I see a handful of .py files.
Is there any way that those are not necessary?

Re: [Doxygen-users] doxygen recent versioning

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

Hi Jasper,

Doxygen now better follows the semantic versioning scheme.

For version x.y.z: 
- x is incremented only for major changes that break backward compatibility (none planned at the moment). 
- y is incremented for normal backwards compatible updates (large or small) and 
- z is for urgent fixes.

Before 1.10.0, the version scheme was basically 1.x.y (and occasionally 1.x.y.z was used for urgent fixes).

The idea is that .z increments can be made for urgent bugfixes on older releases and released as a branch (not yet needed/used).

We did 1415 commits and changed 569 files since 1.9.8, but if you are happy with the features of 1.9.8 there is no need to upgrade of course ;-)

Regards,
  Dimitri

> On 12 Aug 2024, at 16:20, JVerelst--- via Doxygen-users <dox...@li...> wrote:
> 
> 
> 
> Hello,
>  
> I noticed that the last 3 releases of doxygen have all gotten a bump in the middle version number (1.10.0, 1.11.0, 1.12.0).
> It seems like a break with tradition of incrementing this relatively rarely and then various increments of the patch version number. E.g. the last one before that was 1.9.8.
>  
> I’m interested to know what changed here. Did the definition on when to increment which number change? Or is the way versioning is determined still the same and these are all big updates?
> Reason I ask is doxygen upgrades are always some effort for us so seeing these 3 increments of middle number makes me cautious about attempting the next one (we’re currently on 1.9.8.).
>  
> Jasper Verelst
> 
> Jasper Verelst
> Software Expert, Product Development
> 
>  +32 3 350 17 27
>  +32 498 01 65 96
> jve...@om... <mailto:jve...@om...>
> 
> 
>  <https://web-eur.cvent.com/event/c9ec4781-913b-42e2-9b1d-4581db75a95f/summary?RefId=website>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  
> IMPORTANT NOTICE
> 
> The information in this e-mail and any attachments is intended for the addressee only. The contents do not represent the opinion of OM Partners n.v. or any of its affiliates except to the extent that it relates to their official business. If you receive this in error, please contact the sender and delete the material from any computer.
> 
> 
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li... <mailto:Dox...@li...>
> https://lists.sourceforge.net/lists/listinfo/doxygen-users

Re: [Doxygen-users] doxygen recent versioning

[Liviu I. <il...@li...>]

Hi,

I would add a related question: does doxygen follow the SemVer rules?

Thank you,

Liviu

[Doxygen-users] doxygen recent versioning

[<JVe...@om...>]

Hello,

I noticed that the last 3 releases of doxygen have all gotten a bump in the middle version number (1.10.0, 1.11.0, 1.12.0).
It seems like a break with tradition of incrementing this relatively rarely and then various increments of the patch version number. E.g. the last one before that was 1.9.8.

I’m interested to know what changed here. Did the definition on when to increment which number change? Or is the way versioning is determined still the same and these are all big updates?
Reason I ask is doxygen upgrades are always some effort for us so seeing these 3 increments of middle number makes me cautious about attempting the next one (we’re currently on 1.9.8.).

Jasper Verelst

Jasper Verelst
Software Expert, Product Development

[phonenumber] +32 3 350 17 27

[mobilenumber] +32 498 01 65 96

jve...@om...
[https://omp.com/Static/img/Disclaimer/Mailsignature_Singapore.png]<https://web-eur.cvent.com/event/c9ec4781-913b-42e2-9b1d-4581db75a95f/summary?RefId=website>


IMPORTANT NOTICE
The information in this e-mail and any attachments is intended for the addressee only. The contents do not represent the opinion of OM Partners n.v. or any of its affiliates except to the extent that it relates to their official business. If you receive this in error, please contact the sender and delete the material from any computer.

[Doxygen-users] Package list missing on Java

[Andrew J. L. <dr...@me...>]

This is so obvious I assume it is a configuration error on my part.

Documentation is being generated from the package-info.java files, but the package list on generated HTML is empty. You can get to the package documentation by clicking on the breadcrumbs in the annotated classes. The links in the class hierarchy are also live and go to the correct page. Same behavior with and without a \package declaration in the javadoc text.

The package list in the LATEX/PDF version is correct!?

Re: [Doxygen-users] infinite loop from Doxygen-generated .tex

[Georg-Johann L. <av...@gj...>]

Am 03.06.24 um 19:10 schrieb Peter Schöll:
> Hi, Johann
> 
> ever tried to "close" your HTML tags, i.e. <TH> by </TH> and <TD> by </TD>?
> Sometimes I noticed problems with generated documentation disappearing
> when balancing HTML tags.
> 
> Good luck
>      Peter

No effect.  And is I understand, that are actually Doxygen tags.
The Doxygen-generated HTML has balanced tags, so Doxygen can
handle that and understands it correctly.

I even tried v1.12 from current master, and it still generates
broken .tex files (amongst many other issues that make v1.12
and also v1.11 unusable).

The current issue seems to be related to wrong rowspan / colspan
handling.

Johann

Re: [Doxygen-users] infinite loop from Doxygen-generated .tex

[Peter S. <pe...@gm...>]

Hi, Johann

ever tried to "close" your HTML tags, i.e. <TH> by </TH> and <TD> by </TD>?
Sometimes I noticed problems with generated documentation disappearing
when balancing HTML tags.

Good luck
	Peter

Am 02.06.2024 um 19:39 schrieb Georg-Johann Lay:
> Hi, I am having considerable problems with Doxygen v1.9.1
>
> In one of the (many) .dox files, there is this table an the
> end of this mail.  It generates HTML okay, but the PDF header
> is broken.
>
> But the very problem is that somehow, this generates tex code
> that will enter an infinite loop in a later table, and then
> the PDF generation aborts.
>
>
> Image of HTML table: https://i.sstatic.net/l7owTt9F.png
>
> Image of PDF table: https://i.sstatic.net/LJcecbdr.png
>
> This looks like a genuine Doxygen issue in some of its
> LaTeX environments, and perhaps the code below is enough
> to reproduce the issue.  I cross-checked the col/row counts
> several times and cannot find a problem in the source.
>
> Regards,
>
> Johann
>
>
>
> <table>
> <caption>Output Sections and Memory Regions</caption>
> <tr>
>    <th rowspan="2">Output<br>Section
>    <th rowspan="2">Purpose
>    <th colspan="2">Memory Region
> </tr>
> <tr>
>    <th>LMA
>    <th>VMA
> </tr>
> <tr>
>    <td><tt>\ref sec_dot_text ".text"</tt>
>    <td>Executable code, data in progmem
>    <td colspan="2"><center>text</center>
> </tr>
> <tr>
>    <td><tt>\ref sec_dot_data ".data"</tt>
>    <td>Non-zero data in static storage
>    <td>text
>    <td>data
> </tr>
> <tr>
>    <td><tt>\ref sec_dot_bss ".bss"</tt>
>    <td>Zero data in static storage
>    <td>---
>    <td>data
> </tr>
> <tr>
>    <td><tt>\ref sec_dot_noinit ".noinit"</tt>
>    <td>Non-initialized data in static storage
>    <td>---
>    <td>data
> </tr>
> <tr>
>    <td><tt>\ref sec_dot_rodata ".rodata"</tt><sup>1</sup>
>    <td>Read-only data in static storage
>    <td>text
>    <td>LMA + offset<sup>3</sup>
> </tr>
> <tr>
>    <td><tt>\ref sec_dot_rodata ".rodata"</tt><sup>2</sup>
>    <td>Read-only data in static storage
>    <td>0x8000 * <code>__flmap</code><sup>4</sup>
>    <td>rodata
> </tr>
> <tr>
>    <td><tt>\ref sec_dot_eeprom ".eeprom"</tt>
>    <td>Data in EEPROM
>    <td rowspan="5">Note<sup>5</sup>
>    <td>eeprom
> </tr>
> <tr>
>    <td><tt>\ref sec_dot_fuse ".fuse"</tt>
>    <td>Fuse bytes
>    <td>fuse
> </tr>
> <tr>
>    <td><tt>\ref sec_dot_fuse ".lock"</tt>
>    <td>Lock bytes
>    <td>lock
> </tr>
> <tr>
>    <td><tt>\ref sec_dot_fuse ".signature"</tt>
>    <td>Signature bytes
>    <td>signature
> </tr>
> <tr>
>    <td>
>    <td>User signature bytes
>    <td>user_signatures
> </tr>
> </table>
>
>
>
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users

[Doxygen-users] infinite loop from Doxygen-generated .tex

[Georg-Johann L. <av...@gj...>]

Hi, I am having considerable problems with Doxygen v1.9.1

In one of the (many) .dox files, there is this table an the
end of this mail.  It generates HTML okay, but the PDF header
is broken.

But the very problem is that somehow, this generates tex code
that will enter an infinite loop in a later table, and then
the PDF generation aborts.


Image of HTML table: https://i.sstatic.net/l7owTt9F.png

Image of PDF table: https://i.sstatic.net/LJcecbdr.png

This looks like a genuine Doxygen issue in some of its
LaTeX environments, and perhaps the code below is enough
to reproduce the issue.  I cross-checked the col/row counts
several times and cannot find a problem in the source.

Regards,

Johann



<table>
<caption>Output Sections and Memory Regions</caption>
<tr>
   <th rowspan="2">Output<br>Section
   <th rowspan="2">Purpose
   <th colspan="2">Memory Region
</tr>
<tr>
   <th>LMA
   <th>VMA
</tr>
<tr>
   <td><tt>\ref sec_dot_text ".text"</tt>
   <td>Executable code, data in progmem
   <td colspan="2"><center>text</center>
</tr>
<tr>
   <td><tt>\ref sec_dot_data ".data"</tt>
   <td>Non-zero data in static storage
   <td>text
   <td>data
</tr>
<tr>
   <td><tt>\ref sec_dot_bss ".bss"</tt>
   <td>Zero data in static storage
   <td>---
   <td>data
</tr>
<tr>
   <td><tt>\ref sec_dot_noinit ".noinit"</tt>
   <td>Non-initialized data in static storage
   <td>---
   <td>data
</tr>
<tr>
   <td><tt>\ref sec_dot_rodata ".rodata"</tt><sup>1</sup>
   <td>Read-only data in static storage
   <td>text
   <td>LMA + offset<sup>3</sup>
</tr>
<tr>
   <td><tt>\ref sec_dot_rodata ".rodata"</tt><sup>2</sup>
   <td>Read-only data in static storage
   <td>0x8000 * <code>__flmap</code><sup>4</sup>
   <td>rodata
</tr>
<tr>
   <td><tt>\ref sec_dot_eeprom ".eeprom"</tt>
   <td>Data in EEPROM
   <td rowspan="5">Note<sup>5</sup>
   <td>eeprom
</tr>
<tr>
   <td><tt>\ref sec_dot_fuse ".fuse"</tt>
   <td>Fuse bytes
   <td>fuse
</tr>
<tr>
   <td><tt>\ref sec_dot_fuse ".lock"</tt>
   <td>Lock bytes
   <td>lock
</tr>
<tr>
   <td><tt>\ref sec_dot_fuse ".signature"</tt>
   <td>Signature bytes
   <td>signature
</tr>
<tr>
   <td>
   <td>User signature bytes
   <td>user_signatures
</tr>
</table>

Re: [Doxygen-users] dot problems.

[Peter S. <pe...@gm...>]

Hi Woodrow

ever tried to run the given command manually in a command window to see
error messages?
("c:\Graphviz 2.44.1\bin\dot.exe"
"C:/neo_doxygen/rtf/dc/db2/system_8h_a5e8391114a0cf91ac20002be25e3d352_cgraph.dot"
-Tpng -o
"C:/neo_doxygen/rtf/dc/db2/system_8h_a5e8391114a0cf91ac20002be25e3d352_cgraph.png")

Perhaps using a PFCS-compatible (e.g.
https://www.ibm.com/docs/en/zvm/7.2?topic=files-naming) path to dot.exe
(at least w/o spaces) may help.

Good luck
	Peter

Am 15.05.2024 um 20:31 schrieb Woodrow Baker:
> I have graphvis installed on c:\graphviz 2.44.1 on my windows 10 machine.
> I have a very large program that I have set  up to generate call graphs etc.
> I am running doxygen gui 1.10.0
>
> after fixing things like
> @Summary   changing it to    @brief, it runs o.k.  But is not generating
> the call graph, and caller graph files.
>
> I am getting tons of errors like this:  It seems to succeed on some of
> the tries, but one cannot determine which they are, for example
> 1520/1603  doesn't tell me what file it actually worked on.
> How can I troubleshoot this and get it working.
>
> C:/neo_doxygen/rtf/dc/db2/system_8h_a5e8391114a0cf91ac20002be25e3d352_cgraph.dot:1: error: Problems running dot: exit code=1, command='c:\Graphviz 2.44.1\bin\dot.exe', arguments='"C:/neo_doxygen/rtf/dc/db2/system_8h_a5e8391114a0cf91ac20002be25e3d352_cgraph.dot" -Tpng -o "C:/neo_doxygen/rtf/dc/db2/system_8h_a5e8391114a0cf91ac20002be25e3d352_cgraph.png"'
>
> C:/neo_doxygen/rtf/dc/da3/protos_8h_ae84c5a5d042e6c34281dad6a376831de_cgraph.dot:1: error: Problems running dot: exit code=1, command='c:\Graphviz 2.44.1\bin\dot.exe', arguments='"C:/neo_doxygen/rtf/dc/da3/protos_8h_ae84c5a5d042e6c34281dad6a376831de_cgraph.dot" -Tpng -o "C:/neo_doxygen/rtf/dc/da3/protos_8h_ae84c5a5d042e6c34281dad6a376831de_cgraph.png"'
>
> Running dot for graph 1530/1603
>
> Running dot for graph 1531/1603
>
> C:/neo_doxygen/rtf/dc/db2/system_8h_a5e8391114a0cf91ac20002be25e3d352_icgraph.dot:1: error: Problems running dot: exit code=1, command='c:\Graphviz 2.44.1\bin\dot.exe', arguments='"C:/neo_doxygen/rtf/dc/db2/system_8h_a5e8391114a0cf91ac20002be25e3d352_icgraph.dot" -Tpng -o "C:/neo_doxygen/rtf/dc/db2/system_8h_a5e8391114a0cf91ac20002be25e3d352_icgraph.png"'
>
> Running dot for graph 1532/1603
>
>
> It is generating these for the html files as well
>
> C:/neo_doxygen/html/d7/de8/uart2_8h_a1dd9496e7641b301859d3cab9a9f24a5_icgraph.dot:1: error: Problems running dot: exit code=1, command='c:\Graphviz 2.44.1\bin\dot.exe', arguments='"C:/neo_doxygen/html/d7/de8/uart2_8h_a1dd9496e7641b301859d3cab9a9f24a5_icgraph.dot" -Tpng -o "C:/neo_doxygen/html/d7/de8/uart2_8h_a1dd9496e7641b301859d3cab9a9f24a5_icgraph.png"'
>
> C:/neo_doxygen/html/d7/de8/uart2_8h_a1c7f32800f7e5955bc04306b2686a0d7_icgraph.dot:1: error: Problems running dot: exit code=1, command='c:\Graphviz 2.44.1\bin\dot.exe', arguments='"C:/neo_doxygen/html/d7/de8/uart2_8h_a1c7f32800f7e5955bc04306b2686a0d7_icgraph.dot" -Tpng -o "C:/neo_doxygen/html/d7/de8/uart2_8h_a1c7f32800f7e5955bc04306b2686a0d7_icgraph.png"'
>
> Running dot for graph 245/1603
>
> Running dot for graph 246/1603
>
>
> In the first case, there is a .dot file and it seems legit.:
>
> digraph "SYSTEM_Initialize"
> {
>   // LATEX_PDF_SIZE
>    bgcolor="transparent";
>    edge
> [fontname=Helvetica,fontsize=10,labelfontname=Helvetica,labelfontsize=10];
>    node [fontname=Helvetica,fontsize=10,shape=box,height=0.2,width=0.4];
>    rankdir="LR";
>    Node1
> [id="Node000001",label="SYSTEM_Initialize",height=0.2,width=0.4,color="gray40", fillcolor="grey60", style="filled", fontcolor="black",tooltip=" "];
>    Node1 -> Node2
> [id="edge81_Node000001_Node000002",color="steelblue1",style="solid",tooltip=" "];
>    Node2
> [id="Node000002",label="ADC1_Initialize",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$dc/d7a/adc1_8c.html#ad272fc3ade4d66bfb9580444418b97ee",tooltip=" "];
>    Node2 -> Node3
> [id="edge82_Node000002_Node000003",color="steelblue1",style="solid",tooltip=" "];
>    Node3
> [id="Node000003",label="ADC1_CallBack",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$da/dce/adc1_8h.html#a2dd0de98b9bdf0f554cce920e2487ed0",tooltip=" "];
>    Node2 -> Node4
> [id="edge83_Node000002_Node000004",color="steelblue1",style="solid",tooltip=" "];
>    Node4
> [id="Node000004",label="ADC1_SetInterruptHandler",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$dc/d7a/adc1_8c.html#aa3f14d4bbd3cb34caef174a49703b2a8",tooltip=" "];
>    Node1 -> Node5
> [id="edge84_Node000001_Node000005",color="steelblue1",style="solid",tooltip=" "];
>    Node5
> [id="Node000005",label="CLC1_Initialize",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$d0/d2d/clc1_8c.html#aaa42a5ba0915a962cd75964a4dcde3b4",tooltip="This is the generated driver implementation file for the CLC1 driver using PIC24 / dsPIC33 / PIC32MM ..."];
>    Node5 -> Node6
> [id="edge85_Node000005_Node000006",color="steelblue1",style="solid",tooltip=" "];
>    Node6
> [id="Node000006",label="CLC1_Enable",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$d4/d5f/clc1_8h.html#a7c85f3e09616a9a2855839d4b45c0e43",tooltip=" "];
>    Node1 -> Node7
> [id="edge86_Node000001_Node000007",color="steelblue1",style="solid",tooltip=" "];
>    Node7
> [id="Node000007",label="CLOCK_Initialize",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$dc/d54/clock_8c.html#a98390d19c7087c52765eab23eb8ded96",tooltip=": This is the clock.c file generated using PIC24 / dsPIC33 / PIC32MM MCUs"];
>    Node1 -> Node8
> [id="edge87_Node000001_Node000008",color="steelblue1",style="solid",tooltip=" "];
>    Node8
> [id="Node000008",label="CMP1_Initialize",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$d6/db1/cmp1_8c.html#a84bc24b25eabe4579b0322971bd1d86a",tooltip="This is the generated driver implementation file for the CMP1 driver using PIC24 / dsPIC33 / PIC32MM ..."];
>    Node8 -> Node9
> [id="edge88_Node000008_Node000009",color="steelblue1",style="solid",tooltip=" "];
>    Node9
> [id="Node000009",label="CMP1_Enable",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$d2/db0/cmp1_8h.html#a4a9393fadfdc41ef5638880abf1f3eb3",tooltip=" "];
>    Node1 -> Node10
> [id="edge89_Node000001_Node000010",color="steelblue1",style="solid",tooltip=" "];
>    Node10
> [id="Node000010",label="CMP2_Initialize",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$d6/d8e/cmp2_8c.html#a6e9b9e6aa4b7a2aad99d146769cd740a",tooltip="This is the generated driver implementation file for the CMP2 driver using PIC24 / dsPIC33 / PIC32MM ..."];
>    Node10 -> Node11
> [id="edge90_Node000010_Node000011",color="steelblue1",style="solid",tooltip=" "];
>    Node11
> [id="Node000011",label="CMP2_Enable",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$dc/dfa/cmp2_8h.html#aece4cdcc731b1066b0a5a12f2c47d8e6",tooltip=" "];
>    Node1 -> Node12
> [id="edge91_Node000001_Node000012",color="steelblue1",style="solid",tooltip=" "];
>    Node12
> [id="Node000012",label="CVR_Initialize",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$d1/db7/cvr_8c.html#a40bd2a23d2d263c1ad1450f8b3181264",tooltip="This is the generated driver implementation file for the CVR driver using PIC24 / dsPIC33 / PIC32MM M..."];
>    Node1 -> Node13
> [id="edge92_Node000001_Node000013",color="steelblue1",style="solid",tooltip=" "];
>    Node13
> [id="Node000013",label="EXT_INT_Initialize",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$d5/d41/ext__int_8c.html#a6c40d2f45ec674f28815ad65b2c753d5",tooltip=" "];
>    Node1 -> Node14
> [id="edge93_Node000001_Node000014",color="steelblue1",style="solid",tooltip=" "];
>    Node14
> [id="Node000014",label="I2C_init",height=0.2,width=0.4,color="grey40",
> fillcolor="white",
> style="filled",URL="$db/d27/i2c1_8c.html#a9ff51ddf1d325776fef90cce0223772b",tooltip=" "];
>    Node1 -> Node15
> [id="edge94_Node000001_Node000015",color="steelblue1",style="solid",tooltip=" "];
>    Node15
> [id="Node000015",label="INTERRUPT_Initialize",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$d3/d20/interrupt__manager_8c.html#a5c526129ee879458dff6755f5768a6e3",tooltip=": This is the generated driver implementation file for setting up the interrupts using PIC24 / dsPIC3..."];
>    Node1 -> Node16
> [id="edge95_Node000001_Node000016",color="steelblue1",style="solid",tooltip=" "];
>    Node16
> [id="Node000016",label="MCCP1_TMR_Initialize",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$dc/dd1/mccp1__tmr_8c.html#a4ee49d8bb6961fd491f457d4f0d4c81f",tooltip=" "];
>    Node1 -> Node17
> [id="edge96_Node000001_Node000017",color="steelblue1",style="solid",tooltip=" "];
>    Node17
> [id="Node000017",label="MCCP2_TMR_Initialize",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$d6/dc3/mccp2__tmr_8c.html#aecd12e02ba178846b9d726acdbeb1e7c",tooltip=" "];
>    Node1 -> Node18
> [id="edge97_Node000001_Node000018",color="steelblue1",style="solid",tooltip=" "];
>    Node18
> [id="Node000018",label="PIN_MANAGER_Initialize",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$d4/dda/pin__manager_8c.html#a50357774183a136d9490f64ad0d5c6cb",tooltip=" "];
>    Node1 -> Node19
> [id="edge98_Node000001_Node000019",color="steelblue1",style="solid",tooltip=" "];
>    Node19
> [id="Node000019",label="SCCP4_TMR_Initialize",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$d3/d37/sccp4__tmr_8c.html#a55ad8d76072fdf40154726ca7c9605e8",tooltip=" "];
>    Node1 -> Node20
> [id="edge99_Node000001_Node000020",color="steelblue1",style="solid",tooltip=" "];
>    Node20
> [id="Node000020",label="SCCP5_CAPTURE_Initialize",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$da/d5f/sccp5__capture_8c.html#a065c3e5fd8493b0859e316be1cd6f659",tooltip="This is the generated header file for the SCCP5 driver using PIC24 / dsPIC33 / PIC32MM MCUs."];
>    Node1 -> Node21
> [id="edge100_Node000001_Node000021",color="steelblue1",style="solid",tooltip=" "];
>    Node21
> [id="Node000021",label="SCCP6_TMR_Initialize",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$db/d1b/sccp6__tmr_8c.html#aa2123eeb91b168b265fb9d6eef27c60b",tooltip=" "];
>    Node1 -> Node22
> [id="edge101_Node000001_Node000022",color="steelblue1",style="solid",tooltip=" "];
>    Node22
> [id="Node000022",label="SPI1_Initialize",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$d4/dde/spi1_8h.html#a0607cad7a6b302950091fea719146a54",tooltip=" "];
>    Node1 -> Node23
> [id="edge102_Node000001_Node000023",color="steelblue1",style="solid",tooltip=" "];
>    Node23
> [id="Node000023",label="TMR1_Initialize",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$d1/d3c/tmr1_8c.html#aeca9435d024c8eeada966c9dffbb8427",tooltip=" "];
>    Node1 -> Node24
> [id="edge103_Node000001_Node000024",color="steelblue1",style="solid",tooltip=" "];
>    Node24
> [id="Node000024",label="TMR1_Start",height=0.2,width=0.4,color="grey40",
> fillcolor="white",
> style="filled",URL="$d1/d3c/tmr1_8c.html#afed3745413684e23104d29539be4f2e5",tooltip=" "];
>    Node1 -> Node25
> [id="edge104_Node000001_Node000025",color="steelblue1",style="solid",tooltip=" "];
>    Node25
> [id="Node000025",label="TMR2_Initialize",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$dd/da3/tmr2_8c.html#a46c13c9255379e99c10240229a145d37",tooltip=" "];
>    Node1 -> Node26
> [id="edge105_Node000001_Node000026",color="steelblue1",style="solid",tooltip=" "];
>    Node26
> [id="Node000026",label="TMR3_Initialize",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$d3/dd6/tmr3_8c.html#a02e03864926c3b54ddfe281ba823f2ed",tooltip=" "];
>    Node1 -> Node27
> [id="edge106_Node000001_Node000027",color="steelblue1",style="solid",tooltip=" "];
>    Node27
> [id="Node000027",label="TMR4_Initialize",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$d0/d45/tmr4_8c.html#a9d06de36998e68680af819a51c02715b",tooltip=" "];
>    Node1 -> Node28
> [id="edge107_Node000001_Node000028",color="steelblue1",style="solid",tooltip=" "];
>    Node28
> [id="Node000028",label="UART1_Initialize",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$d1/de8/uart1_8c.html#a10757505060dc7bf0fe148c5363eae08",tooltip=" "];
>    Node28 -> Node29
> [id="edge108_Node000028_Node000029",color="steelblue1",style="solid",tooltip=" "];
>    Node29
> [id="Node000029",label="UART1_Receive_CallBack",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$de/d9e/uart1_8h.html#a6f9531a262fcf20e717451d4176fbaac",tooltip=" "];
>    Node28 -> Node30
> [id="edge109_Node000028_Node000030",color="steelblue1",style="solid",tooltip=" "];
>    Node30
> [id="Node000030",label="UART1_SetRxInterruptHandler",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$d1/de8/uart1_8c.html#ada9cfd0a8099b051306ff18cea19a165",tooltip=" "];
>    Node30 -> Node29
> [id="edge110_Node000030_Node000029",color="steelblue1",style="solid",tooltip=" "];
>    Node28 -> Node31
> [id="edge111_Node000028_Node000031",color="steelblue1",style="solid",tooltip=" "];
>    Node31
> [id="Node000031",label="UART1_SetTxInterruptHandler",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$d1/de8/uart1_8c.html#aae82bc4b606e9f317ced09e030c3ed2a",tooltip=" "];
>    Node31 -> Node32
> [id="edge112_Node000031_Node000032",color="steelblue1",style="solid",tooltip=" "];
>    Node32
> [id="Node000032",label="UART1_Transmit_CallBack",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$de/d9e/uart1_8h.html#ac9c13d037043af27f19a5dbb9987c5ad",tooltip=" "];
>    Node28 -> Node32
> [id="edge113_Node000028_Node000032",color="steelblue1",style="solid",tooltip=" "];
>    Node1 -> Node33
> [id="edge114_Node000001_Node000033",color="steelblue1",style="solid",tooltip=" "];
>    Node33
> [id="Node000033",label="UART2_Initialize",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$d9/de3/uart2_8c.html#a1c7f32800f7e5955bc04306b2686a0d7",tooltip=" "];
>    Node33 -> Node34
> [id="edge115_Node000033_Node000034",color="steelblue1",style="solid",tooltip=" "];
>    Node34
> [id="Node000034",label="UART2_Receive_CallBack",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$d7/de8/uart2_8h.html#a744360a1066b7d86ffc19fe7f1948eee",tooltip=" "];
>    Node33 -> Node35
> [id="edge116_Node000033_Node000035",color="steelblue1",style="solid",tooltip=" "];
>    Node35
> [id="Node000035",label="UART2_SetRxInterruptHandler",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$d9/de3/uart2_8c.html#a1668b0cf18a2d12b03a004fc398442b7",tooltip=" "];
>    Node35 -> Node34
> [id="edge117_Node000035_Node000034",color="steelblue1",style="solid",tooltip=" "];
>    Node33 -> Node36
> [id="edge118_Node000033_Node000036",color="steelblue1",style="solid",tooltip=" "];
>    Node36
> [id="Node000036",label="UART2_SetTxInterruptHandler",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$d9/de3/uart2_8c.html#a741b3f9d648836d5c6be99408a85c625",tooltip=" "];
>    Node36 -> Node37
> [id="edge119_Node000036_Node000037",color="steelblue1",style="solid",tooltip=" "];
>    Node37
> [id="Node000037",label="UART2_Transmit_CallBack",height=0.2,width=0.4,color="grey40", fillcolor="white", style="filled",URL="$d7/de8/uart2_8h.html#a1dd9496e7641b301859d3cab9a9f24a5",tooltip=" "];
>    Node33 -> Node37
> [id="edge120_Node000033_Node000037",color="steelblue1",style="solid",tooltip=" "];
> }
>
>
>
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users

[Doxygen-users] dot problems.

[Woodrow B. <kn...@re...>]

I have graphvis installed on c:\graphviz 2.44.1 on my windows 10 machine.
I have a very large program that I have set  up to generate call graphs etc.
I am running doxygen gui 1.10.0

after fixing things like
@Summary   changing it to    @brief, it runs o.k.  But is not generating
the call graph, and caller graph files.

I am getting tons of errors like this:  It seems to succeed on some of the
tries, but one cannot determine which they are, for example 1520/1603
doesn't tell me what file it actually worked on.
How can I troubleshoot this and get it working.

C:/neo_doxygen/rtf/dc/db2/system_8h_a5e8391114a0cf91ac20002be25e3d352_cgraph.dot:1:
error: Problems running dot: exit code=1, command='c:\Graphviz
2.44.1\bin\dot.exe',
arguments='"C:/neo_doxygen/rtf/dc/db2/system_8h_a5e8391114a0cf91ac20002be25e3d352_cgraph.dot"
-Tpng -o
"C:/neo_doxygen/rtf/dc/db2/system_8h_a5e8391114a0cf91ac20002be25e3d352_cgraph.png"'

C:/neo_doxygen/rtf/dc/da3/protos_8h_ae84c5a5d042e6c34281dad6a376831de_cgraph.dot:1:
error: Problems running dot: exit code=1, command='c:\Graphviz
2.44.1\bin\dot.exe',
arguments='"C:/neo_doxygen/rtf/dc/da3/protos_8h_ae84c5a5d042e6c34281dad6a376831de_cgraph.dot"
-Tpng -o
"C:/neo_doxygen/rtf/dc/da3/protos_8h_ae84c5a5d042e6c34281dad6a376831de_cgraph.png"'

Running dot for graph 1530/1603

Running dot for graph 1531/1603

C:/neo_doxygen/rtf/dc/db2/system_8h_a5e8391114a0cf91ac20002be25e3d352_icgraph.dot:1:
error: Problems running dot: exit code=1, command='c:\Graphviz
2.44.1\bin\dot.exe',
arguments='"C:/neo_doxygen/rtf/dc/db2/system_8h_a5e8391114a0cf91ac20002be25e3d352_icgraph.dot"
-Tpng -o
"C:/neo_doxygen/rtf/dc/db2/system_8h_a5e8391114a0cf91ac20002be25e3d352_icgraph.png"'

Running dot for graph 1532/1603


It is generating these for the html files as well

C:/neo_doxygen/html/d7/de8/uart2_8h_a1dd9496e7641b301859d3cab9a9f24a5_icgraph.dot:1:
error: Problems running dot: exit code=1, command='c:\Graphviz
2.44.1\bin\dot.exe',
arguments='"C:/neo_doxygen/html/d7/de8/uart2_8h_a1dd9496e7641b301859d3cab9a9f24a5_icgraph.dot"
-Tpng -o
"C:/neo_doxygen/html/d7/de8/uart2_8h_a1dd9496e7641b301859d3cab9a9f24a5_icgraph.png"'

C:/neo_doxygen/html/d7/de8/uart2_8h_a1c7f32800f7e5955bc04306b2686a0d7_icgraph.dot:1:
error: Problems running dot: exit code=1, command='c:\Graphviz
2.44.1\bin\dot.exe',
arguments='"C:/neo_doxygen/html/d7/de8/uart2_8h_a1c7f32800f7e5955bc04306b2686a0d7_icgraph.dot"
-Tpng -o
"C:/neo_doxygen/html/d7/de8/uart2_8h_a1c7f32800f7e5955bc04306b2686a0d7_icgraph.png"'

Running dot for graph 245/1603

Running dot for graph 246/1603


In the first case, there is a .dot file and it seems legit.:

digraph "SYSTEM_Initialize"
{
 // LATEX_PDF_SIZE
  bgcolor="transparent";
  edge
[fontname=Helvetica,fontsize=10,labelfontname=Helvetica,labelfontsize=10];
  node [fontname=Helvetica,fontsize=10,shape=box,height=0.2,width=0.4];
  rankdir="LR";
  Node1
[id="Node000001",label="SYSTEM_Initialize",height=0.2,width=0.4,color="gray40",
fillcolor="grey60", style="filled", fontcolor="black",tooltip=" "];
  Node1 -> Node2
[id="edge81_Node000001_Node000002",color="steelblue1",style="solid",tooltip="
"];
  Node2
[id="Node000002",label="ADC1_Initialize",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$dc/d7a/adc1_8c.html#ad272fc3ade4d66bfb9580444418b97ee",tooltip="
"];
  Node2 -> Node3
[id="edge82_Node000002_Node000003",color="steelblue1",style="solid",tooltip="
"];
  Node3
[id="Node000003",label="ADC1_CallBack",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$da/dce/adc1_8h.html#a2dd0de98b9bdf0f554cce920e2487ed0",tooltip="
"];
  Node2 -> Node4
[id="edge83_Node000002_Node000004",color="steelblue1",style="solid",tooltip="
"];
  Node4
[id="Node000004",label="ADC1_SetInterruptHandler",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$dc/d7a/adc1_8c.html#aa3f14d4bbd3cb34caef174a49703b2a8",tooltip="
"];
  Node1 -> Node5
[id="edge84_Node000001_Node000005",color="steelblue1",style="solid",tooltip="
"];
  Node5
[id="Node000005",label="CLC1_Initialize",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$d0/d2d/clc1_8c.html#aaa42a5ba0915a962cd75964a4dcde3b4",tooltip="This
is the generated driver implementation file for the CLC1 driver using PIC24
/ dsPIC33 / PIC32MM ..."];
  Node5 -> Node6
[id="edge85_Node000005_Node000006",color="steelblue1",style="solid",tooltip="
"];
  Node6
[id="Node000006",label="CLC1_Enable",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$d4/d5f/clc1_8h.html#a7c85f3e09616a9a2855839d4b45c0e43",tooltip="
"];
  Node1 -> Node7
[id="edge86_Node000001_Node000007",color="steelblue1",style="solid",tooltip="
"];
  Node7
[id="Node000007",label="CLOCK_Initialize",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$dc/d54/clock_8c.html#a98390d19c7087c52765eab23eb8ded96",tooltip=":
This is the clock.c file generated using PIC24 / dsPIC33 / PIC32MM MCUs"];
  Node1 -> Node8
[id="edge87_Node000001_Node000008",color="steelblue1",style="solid",tooltip="
"];
  Node8
[id="Node000008",label="CMP1_Initialize",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$d6/db1/cmp1_8c.html#a84bc24b25eabe4579b0322971bd1d86a",tooltip="This
is the generated driver implementation file for the CMP1 driver using PIC24
/ dsPIC33 / PIC32MM ..."];
  Node8 -> Node9
[id="edge88_Node000008_Node000009",color="steelblue1",style="solid",tooltip="
"];
  Node9
[id="Node000009",label="CMP1_Enable",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$d2/db0/cmp1_8h.html#a4a9393fadfdc41ef5638880abf1f3eb3",tooltip="
"];
  Node1 -> Node10
[id="edge89_Node000001_Node000010",color="steelblue1",style="solid",tooltip="
"];
  Node10
[id="Node000010",label="CMP2_Initialize",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$d6/d8e/cmp2_8c.html#a6e9b9e6aa4b7a2aad99d146769cd740a",tooltip="This
is the generated driver implementation file for the CMP2 driver using PIC24
/ dsPIC33 / PIC32MM ..."];
  Node10 -> Node11
[id="edge90_Node000010_Node000011",color="steelblue1",style="solid",tooltip="
"];
  Node11
[id="Node000011",label="CMP2_Enable",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$dc/dfa/cmp2_8h.html#aece4cdcc731b1066b0a5a12f2c47d8e6",tooltip="
"];
  Node1 -> Node12
[id="edge91_Node000001_Node000012",color="steelblue1",style="solid",tooltip="
"];
  Node12
[id="Node000012",label="CVR_Initialize",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$d1/db7/cvr_8c.html#a40bd2a23d2d263c1ad1450f8b3181264",tooltip="This
is the generated driver implementation file for the CVR driver using PIC24
/ dsPIC33 / PIC32MM M..."];
  Node1 -> Node13
[id="edge92_Node000001_Node000013",color="steelblue1",style="solid",tooltip="
"];
  Node13
[id="Node000013",label="EXT_INT_Initialize",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$d5/d41/ext__int_8c.html#a6c40d2f45ec674f28815ad65b2c753d5",tooltip="
"];
  Node1 -> Node14
[id="edge93_Node000001_Node000014",color="steelblue1",style="solid",tooltip="
"];
  Node14
[id="Node000014",label="I2C_init",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$db/d27/i2c1_8c.html#a9ff51ddf1d325776fef90cce0223772b",tooltip="
"];
  Node1 -> Node15
[id="edge94_Node000001_Node000015",color="steelblue1",style="solid",tooltip="
"];
  Node15
[id="Node000015",label="INTERRUPT_Initialize",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$d3/d20/interrupt__manager_8c.html#a5c526129ee879458dff6755f5768a6e3",tooltip=":
This is the generated driver implementation file for setting up the
interrupts using PIC24 / dsPIC3..."];
  Node1 -> Node16
[id="edge95_Node000001_Node000016",color="steelblue1",style="solid",tooltip="
"];
  Node16
[id="Node000016",label="MCCP1_TMR_Initialize",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$dc/dd1/mccp1__tmr_8c.html#a4ee49d8bb6961fd491f457d4f0d4c81f",tooltip="
"];
  Node1 -> Node17
[id="edge96_Node000001_Node000017",color="steelblue1",style="solid",tooltip="
"];
  Node17
[id="Node000017",label="MCCP2_TMR_Initialize",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$d6/dc3/mccp2__tmr_8c.html#aecd12e02ba178846b9d726acdbeb1e7c",tooltip="
"];
  Node1 -> Node18
[id="edge97_Node000001_Node000018",color="steelblue1",style="solid",tooltip="
"];
  Node18
[id="Node000018",label="PIN_MANAGER_Initialize",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$d4/dda/pin__manager_8c.html#a50357774183a136d9490f64ad0d5c6cb",tooltip="
"];
  Node1 -> Node19
[id="edge98_Node000001_Node000019",color="steelblue1",style="solid",tooltip="
"];
  Node19
[id="Node000019",label="SCCP4_TMR_Initialize",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$d3/d37/sccp4__tmr_8c.html#a55ad8d76072fdf40154726ca7c9605e8",tooltip="
"];
  Node1 -> Node20
[id="edge99_Node000001_Node000020",color="steelblue1",style="solid",tooltip="
"];
  Node20
[id="Node000020",label="SCCP5_CAPTURE_Initialize",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$da/d5f/sccp5__capture_8c.html#a065c3e5fd8493b0859e316be1cd6f659",tooltip="This
is the generated header file for the SCCP5 driver using PIC24 / dsPIC33 /
PIC32MM MCUs."];
  Node1 -> Node21
[id="edge100_Node000001_Node000021",color="steelblue1",style="solid",tooltip="
"];
  Node21
[id="Node000021",label="SCCP6_TMR_Initialize",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$db/d1b/sccp6__tmr_8c.html#aa2123eeb91b168b265fb9d6eef27c60b",tooltip="
"];
  Node1 -> Node22
[id="edge101_Node000001_Node000022",color="steelblue1",style="solid",tooltip="
"];
  Node22
[id="Node000022",label="SPI1_Initialize",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$d4/dde/spi1_8h.html#a0607cad7a6b302950091fea719146a54",tooltip="
"];
  Node1 -> Node23
[id="edge102_Node000001_Node000023",color="steelblue1",style="solid",tooltip="
"];
  Node23
[id="Node000023",label="TMR1_Initialize",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$d1/d3c/tmr1_8c.html#aeca9435d024c8eeada966c9dffbb8427",tooltip="
"];
  Node1 -> Node24
[id="edge103_Node000001_Node000024",color="steelblue1",style="solid",tooltip="
"];
  Node24
[id="Node000024",label="TMR1_Start",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$d1/d3c/tmr1_8c.html#afed3745413684e23104d29539be4f2e5",tooltip="
"];
  Node1 -> Node25
[id="edge104_Node000001_Node000025",color="steelblue1",style="solid",tooltip="
"];
  Node25
[id="Node000025",label="TMR2_Initialize",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$dd/da3/tmr2_8c.html#a46c13c9255379e99c10240229a145d37",tooltip="
"];
  Node1 -> Node26
[id="edge105_Node000001_Node000026",color="steelblue1",style="solid",tooltip="
"];
  Node26
[id="Node000026",label="TMR3_Initialize",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$d3/dd6/tmr3_8c.html#a02e03864926c3b54ddfe281ba823f2ed",tooltip="
"];
  Node1 -> Node27
[id="edge106_Node000001_Node000027",color="steelblue1",style="solid",tooltip="
"];
  Node27
[id="Node000027",label="TMR4_Initialize",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$d0/d45/tmr4_8c.html#a9d06de36998e68680af819a51c02715b",tooltip="
"];
  Node1 -> Node28
[id="edge107_Node000001_Node000028",color="steelblue1",style="solid",tooltip="
"];
  Node28
[id="Node000028",label="UART1_Initialize",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$d1/de8/uart1_8c.html#a10757505060dc7bf0fe148c5363eae08",tooltip="
"];
  Node28 -> Node29
[id="edge108_Node000028_Node000029",color="steelblue1",style="solid",tooltip="
"];
  Node29
[id="Node000029",label="UART1_Receive_CallBack",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$de/d9e/uart1_8h.html#a6f9531a262fcf20e717451d4176fbaac",tooltip="
"];
  Node28 -> Node30
[id="edge109_Node000028_Node000030",color="steelblue1",style="solid",tooltip="
"];
  Node30
[id="Node000030",label="UART1_SetRxInterruptHandler",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$d1/de8/uart1_8c.html#ada9cfd0a8099b051306ff18cea19a165",tooltip="
"];
  Node30 -> Node29
[id="edge110_Node000030_Node000029",color="steelblue1",style="solid",tooltip="
"];
  Node28 -> Node31
[id="edge111_Node000028_Node000031",color="steelblue1",style="solid",tooltip="
"];
  Node31
[id="Node000031",label="UART1_SetTxInterruptHandler",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$d1/de8/uart1_8c.html#aae82bc4b606e9f317ced09e030c3ed2a",tooltip="
"];
  Node31 -> Node32
[id="edge112_Node000031_Node000032",color="steelblue1",style="solid",tooltip="
"];
  Node32
[id="Node000032",label="UART1_Transmit_CallBack",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$de/d9e/uart1_8h.html#ac9c13d037043af27f19a5dbb9987c5ad",tooltip="
"];
  Node28 -> Node32
[id="edge113_Node000028_Node000032",color="steelblue1",style="solid",tooltip="
"];
  Node1 -> Node33
[id="edge114_Node000001_Node000033",color="steelblue1",style="solid",tooltip="
"];
  Node33
[id="Node000033",label="UART2_Initialize",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$d9/de3/uart2_8c.html#a1c7f32800f7e5955bc04306b2686a0d7",tooltip="
"];
  Node33 -> Node34
[id="edge115_Node000033_Node000034",color="steelblue1",style="solid",tooltip="
"];
  Node34
[id="Node000034",label="UART2_Receive_CallBack",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$d7/de8/uart2_8h.html#a744360a1066b7d86ffc19fe7f1948eee",tooltip="
"];
  Node33 -> Node35
[id="edge116_Node000033_Node000035",color="steelblue1",style="solid",tooltip="
"];
  Node35
[id="Node000035",label="UART2_SetRxInterruptHandler",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$d9/de3/uart2_8c.html#a1668b0cf18a2d12b03a004fc398442b7",tooltip="
"];
  Node35 -> Node34
[id="edge117_Node000035_Node000034",color="steelblue1",style="solid",tooltip="
"];
  Node33 -> Node36
[id="edge118_Node000033_Node000036",color="steelblue1",style="solid",tooltip="
"];
  Node36
[id="Node000036",label="UART2_SetTxInterruptHandler",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$d9/de3/uart2_8c.html#a741b3f9d648836d5c6be99408a85c625",tooltip="
"];
  Node36 -> Node37
[id="edge119_Node000036_Node000037",color="steelblue1",style="solid",tooltip="
"];
  Node37
[id="Node000037",label="UART2_Transmit_CallBack",height=0.2,width=0.4,color="grey40",
fillcolor="white",
style="filled",URL="$d7/de8/uart2_8h.html#a1dd9496e7641b301859d3cab9a9f24a5",tooltip="
"];
  Node33 -> Node37
[id="edge120_Node000033_Node000037",color="steelblue1",style="solid",tooltip="
"];
}

Re: [Doxygen-users] Support for PL/SQL ?

[Woodrow B. <kn...@re...>]

Microchip is emitting bogus headers.
@Example
@Param
etc.
Change doxgen so that it will do a to lower on anything after the @  so
that it will change @Example to @example before processing.
This way @Example will work the same as @example and not throw an
unrecognized command error



On Sun, Dec 17, 2023 at 4:09 AM Esteban Zimanyi <est...@gm...>
wrote:

> Dear all
>
> There has been many requests for supporting SQL in doxygen
> https://sourceforge.net/p/doxygen/mailman/search/?q=sql
> I haven't found whether this is available.
>
> MobilityDB is an extension of PostgreSQL for mobility data
> https://github.com/estebanzimanyi/MobilityDB
> The source code is composed of BOTH SQL definitions, e.g.,
>
> https://github.com/estebanzimanyi/MobilityDB/blob/master/mobilitydb/sql/general/032_temporal_boxops.in.sql
> and the corresponding C functions, e.g.,
>
> https://github.com/estebanzimanyi/MobilityDB/blob/master/mobilitydb/src/general/temporal_boxops.c
> Linking the two SQL and C worlds in doxygen would be really GREAT for
> synchronizing the evolution of both components.
>
> Many thanks for your advice
>
> ------------------------------------------------------------
> Prof. Esteban Zimanyi
> Department of Computer & Decision Engineering  (CoDE) CP 165/15
> Universite Libre de Bruxelles
> Avenue F. D. Roosevelt 50
> B-1050 Brussels, Belgium
> fax: + 32.2.650.47.13
> tel: + 32.2.650.31.85
> e-mail: est...@ul...
> Internet: http://cs.ulb.ac.be/members/esteban/
> ------------------------------------------------------------
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>

[Doxygen-users] Support for PL/SQL ?

[Esteban Z. <est...@gm...>]

Dear all

There has been many requests for supporting SQL in doxygen
https://sourceforge.net/p/doxygen/mailman/search/?q=sql
I haven't found whether this is available.

MobilityDB is an extension of PostgreSQL for mobility data
https://github.com/estebanzimanyi/MobilityDB
The source code is composed of BOTH SQL definitions, e.g.,
https://github.com/estebanzimanyi/MobilityDB/blob/master/mobilitydb/sql/general/032_temporal_boxops.in.sql
and the corresponding C functions, e.g.,
https://github.com/estebanzimanyi/MobilityDB/blob/master/mobilitydb/src/general/temporal_boxops.c
Linking the two SQL and C worlds in doxygen would be really GREAT for
synchronizing the evolution of both components.

Many thanks for your advice

------------------------------------------------------------
Prof. Esteban Zimanyi
Department of Computer & Decision Engineering  (CoDE) CP 165/15
Universite Libre de Bruxelles
Avenue F. D. Roosevelt 50
B-1050 Brussels, Belgium
fax: + 32.2.650.47.13
tel: + 32.2.650.31.85
e-mail: est...@ul...
Internet: http://cs.ulb.ac.be/members/esteban/
------------------------------------------------------------

[Doxygen-users] Output style

[Jens K. <pau...@gm...>]

Hi. It is possible to Générale XML from Sourcecode. But, can I use a Layout File instand Output XML and preprocess the data informations to Set the style? 

Re: [Doxygen-users] Including DITAA diagrams into the documentation

[flap <fb...@oh...>]

Hi Peter,

Am Samstag, 2. Dezember 2023, 14:44:49 CET schrieb Peter Schöll:
> it seems that you set DOT_IMAGE_FORMAT to "svg" in the doxygen
> configuration file.
> Is that right?

Yes, it is set to "svg". Works perfectly for all the other embedded platuml 
images. That's why I asked for a specific name overwrite.

Cheers
Jürgen

Re: [Doxygen-users] Including DITAA diagrams into the documentation

[Peter S. <pe...@gm...>]

Hi Jürgen,

it seems that you set DOT_IMAGE_FORMAT to "svg" in the doxygen
configuration file.
Is that right?

Have a nice weekend
	Peter

Am 02.12.2023 um 13:21 schrieb flap:
> Hi list,
>
> I'm using doxygen to generate my documentation including platuml images.
> platuml uses SVG file formats and it works fine. The generated HTML code
> always uses filenames with the .svg extension.
>
> When I create DITAA images, plantuml only supports PNG files for this kind of
> diagrams. The generated HTML code still uses a filename with .svg extension
> and this will fail in the browser, since it expects an SVG image, but finds a
> PNG file.
>
> I tried to overwrite the filename with this example, but it still doesn't
> work.
>
> @startuml {example.png} "ditaa example"
> ditaa
> +--------+   +-------+    +-------+
> |        +---+ ditaa +--> |       |
> |  Text  |   +-------+    |Diagram|
> |Dokument|   |!Magie!|    |       |
> |     {d}|   |       |    |       |
> +---+----+   +-------+    +-------+
>      :                         ^
>      |    Ein Haufen Arbeit    |
>      +-------------------------+
> @enduml
>
> It generates a PNG file with the name "example.svg" instead.
>
> Is there some trick to force a specific filename for plantuml in these cases
> to get a correct html file?
>
> Cheers
> Jürgen
>
>
>
>
>
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users

[Doxygen-users] Including DITAA diagrams into the documentation

[flap <fb...@oh...>]

Hi list,

I'm using doxygen to generate my documentation including platuml images.
platuml uses SVG file formats and it works fine. The generated HTML code 
always uses filenames with the .svg extension.

When I create DITAA images, plantuml only supports PNG files for this kind of 
diagrams. The generated HTML code still uses a filename with .svg extension 
and this will fail in the browser, since it expects an SVG image, but finds a 
PNG file.

I tried to overwrite the filename with this example, but it still doesn't 
work.

@startuml {example.png} "ditaa example"
ditaa
+--------+   +-------+    +-------+
|        +---+ ditaa +--> |       |
|  Text  |   +-------+    |Diagram|
|Dokument|   |!Magie!|    |       |
|     {d}|   |       |    |       |
+---+----+   +-------+    +-------+
    :                         ^
    |    Ein Haufen Arbeit    |
    +-------------------------+
@enduml

It generates a PNG file with the name "example.svg" instead.

Is there some trick to force a specific filename for plantuml in these cases 
to get a correct html file?

Cheers
Jürgen

[Doxygen-users] Layout - Argumentlist in a seperate lline

[Jens K. <pau...@gm...>]

Hello,
how can I "layout" the given form to:

// this is the goal:
// (to avoid many left space):

template<typename T = DWORD>
std::string windows::ERROR_TOO_MANY_DESCRIPTORS
     ( std::function< void(std::any)> func = nullptr,
       std::any                       args = nullptr
     )

This is the current (origin) form:

template<typename T = DWORD>
std::string windows::ERROR_TOO_MANY_DESCRIPTORS 	( 	std::function< 
void(std::any)> 	/func/ = |nullptr|,

	
	std::any 	/args/ = |nullptr|

	) 	


-- 
Diese E-Mail wurde von Avast-Antivirussoftware auf Viren geprüft.
www.avast.com

[Doxygen-users] change Layout

[Jens K. <pau...@gm...>]

Hello,
my current settings of Doxygen 1.9.6 produce this form:

Functions
     DWORD ERROR_ACCESS_DENIED ()

template<template< typename > class T>
   std::string ERROR_ACCESS_DENIED ()
         DWORD ERROR_ACCESS_DENIED ()

is it possible, to split "template<template< typename > class T>" item,
to seperate group ?
So, DWORD ERROR_ACCESS_DENIED() inline item are don't displayed with
template stuff ?

Like this form:

template<template< typename > class T> std::string ERROR_ACCESS_DENIED ()
template<template< typename > class T> std::string ERROR_ADAP_HWD_ERR ()

and:
inline DWORD ERROR_ACCESS_DENIED ()
inline DWORD ERROR_ADAP_HWD_ERR ()

Thanks for helping
paule32

-- 
Diese E-Mail wurde von Avast-Antivirussoftware auf Viren geprüft.
www.avast.com

[Doxygen-users] change Layout outpuit

[Jens K. <pau...@gm...>]

<!DOCTYPE html>
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <font face="monospace">Hello,<br>
      my current settings of Doxygen 1.9.6 produce this form:<br>
      <br>
      Functions<br>
          DWORD ERROR_ACCESS_DENIED ()<br>
      <br>
      template&lt;template&lt; typename &gt; class T&gt;<br>
        std::string ERROR_ACCESS_DENIED ()<br>
              DWORD ERROR_ACCESS_DENIED ()<br>
      <br>
      is it possible, to split "template&lt;template&lt; typename &gt;
      class T&gt;" item,<br>
      to seperate group ?<br>
      So, DWORD ERROR_ACCESS_DENIED() inline item are don't displayed
      with<br>
      template stuff ?<br>
      <br>
      Like this form:<br>
      <br>
    </font><font face="monospace">template&lt;template&lt; typename &gt;
      class T&gt; std::string ERROR_ACCESS_DENIED ()<br>
    </font><font face="monospace">template&lt;template&lt; typename &gt;
      class T&gt; std::string ERROR_ADAP_HWD_ERR ()<br>
      <br>
      and:<br>
      inline </font><font face="monospace">DWORD ERROR_ACCESS_DENIED ()<br>
    </font><font face="monospace">inline DWORD ERROR_ADAP_HWD_ERR ()</font><br>
    <font face="monospace"><br>
      Thanks for helping<br>
      paule32</font>
  <div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br /><table style="border-top: 1px solid #D3D4DE;"><tr><td style="width: 55px; padding-top: 13px;"><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient" target="_blank"><img src="https://s-install.avcdn.net/ipm/preview/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif" alt="" width="46" height="29" style="width: 46px; height: 29px;"/></a></td><td style="width: 470px; padding-top: 12px; color: #41424e; font-size: 13px; font-family: Arial, Helvetica, sans-serif; line-height: 18px;">Virenfrei.<a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient" target="_blank" style="color: #4453ea;">www.avast.com</a></td></tr></table><a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"> </a></div></body>
</html>

[Doxygen-users] display INLINE label on right side of html

[Jens K. <pau...@gm...>]

<!DOCTYPE html>
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <font face="monospace">Hello,<br>
      my current settings of Doxygen 1.9.6 produce this form:<br>
      <br>
      Functions<br>
          DWORD ERROR_ACCESS_DENIED ()<br>
      <br>
      template&lt;template&lt; typename &gt; class T&gt;<br>
        std::string ERROR_ACCESS_DENIED ()<br>
              DWORD ERROR_ACCESS_DENIED ()<br>
      <br>
      is it possible, to split "template&lt;template&lt; typename &gt;
      class T&gt;" item,<br>
      to seperate group ?<br>
      So, DWORD ERROR_ACCESS_DENIED() inline item are don't displayed
      with<br>
      template stuff ?<br>
      <br>
      Like this form:<br>
      <br>
    </font><font face="monospace">template&lt;template&lt; typename &gt;
      class T&gt; std::string ERROR_ACCESS_DENIED ()<br>
    </font><font face="monospace">template&lt;template&lt; typename &gt;
      class T&gt; std::string ERROR_ADAP_HWD_ERR ()<br>
      <br>
      and:<br>
      inline </font><font face="monospace">DWORD ERROR_ACCESS_DENIED ()<br>
    </font><font face="monospace">inline DWORD ERROR_ADAP_HWD_ERR ()</font><br>
    <font face="monospace"><br>
      Thanks for helping<br>
      paule32<br>
    </font><font face="monospace"><br>
    </font>
    <table>
      <tbody>
        <tr class="memitem:a567cc3ff4813cfc7c4c1afe516452b7c">
          <td class="memItemLeft" valign="top" align="right"><br>
          </td>
        </tr>
      </tbody>
    </table>
  <div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br /><table style="border-top: 1px solid #D3D4DE;"><tr><td style="width: 55px; padding-top: 13px;"><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient" target="_blank"><img src="https://s-install.avcdn.net/ipm/preview/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif" alt="" width="46" height="29" style="width: 46px; height: 29px;"/></a></td><td style="width: 470px; padding-top: 12px; color: #41424e; font-size: 13px; font-family: Arial, Helvetica, sans-serif; line-height: 18px;">Virenfrei.<a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient" target="_blank" style="color: #4453ea;">www.avast.com</a></td></tr></table><a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"> </a></div></body>
</html>

[Doxygen-users] Creating hierarchical documentation

[Randy Y. <Ra...@as...>]

We are using doxygen for general project documentation (i.e., not for
code). We are standardized on using markdown (.md) files.

I would like to partition the documentation into separate files, but
have them show up in a hierarchy in the TOC pane on the left and as a
continuous document in the output.

For example, let's say I have a standard mainpage.md file, but then I
want to create a glossary in a separate file called glossary.md:

# Glossary {#glossary}

- TBD: To Be Determined

- n/a: Not Available

etc.

When I add this file to mainpage.md like this

@subpage glossary

doxygen nicely provides "Glossary" to the TOC pane, as I desire, but
instead of actually including the markdown in the output, it includes a
_link_ to the page; you must click on the link to see the page.


How do I partition documents and get doxygen to 1) include the file in
the TOC, and 2) get the content of the included file directly into the
output rather than just a link? I also want to nest this under multiple
hierarchies.

--Randy





This message contains confidential information. If you are not the intended recipient, notify the sender immediately and delete this e-mail from your system. You should always check e-mail for viruses. Sender does not accept liability for any viruses that may be inadvertently transmitted.

[Doxygen-users] VSDoxyHighlighter: Highlighting/autocomplete for Visual Studio

[<Se...@t-...>]

Hi everyone,

since Visual Studio (not VS Code!) never provided built-in syntax 
highlighting of Doxygen commands in C++ comments and previous extensions 
were no longer maintained, I wrote one: VSDoxyHighlighter is open source 
and available for Visual Studio 2022 on github 
(https://github.com/Sedeniono/VSDoxyHighlighter) as well as the VS 
marketplace 
(https://marketplace.visualstudio.com/items?itemName=Sedenion.VSDoxyHighlighter). 
See these two pages for some images.

The extension not only comes with syntax highlighting but also offers 
autocomplete of commands while you type them, and quick info tooltips 
when hovering with the mouse over commands. It supports all "special" 
commands of the current Doxygen 1.9.8 and has some (rudimentary) 
markdown support. I ensured that the performance impact of the syntax 
highlighting is minimal; I use it in files containing more than 20000 
lines of code without problems. I have also not received any problem 
reports in the several months that the extension is available, so it is 
pretty stable.

Re: [Doxygen-users] Hello

[Simon D. <sim...@te...>]

Hi, do you have any questions or problems?
________________________________
From: Amn Ojee Uw <amn...@gm...>
Sent: Saturday, September 23, 2023 12:12:36 AM
To: dox...@li... <dox...@li...>
Subject: [Doxygen-users] Hello

Nu-B here.
Thank you for accepting me.



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

[Doxygen-users] Hello

[Amn O. Uw <amn...@gm...>]

Nu-B here.
Thank you for accepting me.