I run doxygen with my configuration .dat file. I set: ALIASES += unique_id="\par UNIQUE ID\n". and get the the xml output contains: <simplesect kind="par"><title>UNIQUE ID</title><para>test_case1</para></simplesect> But some my team member from different country need to change the configuration file to: ALIASES += unique_id="\par UNIQUE ID^^" to get the same xml output. For my side, if I use "^^" I will not get the xml result like above. It's just: <simplesect kind="par"><title>UNIQUE ID^^ test_case1</title><para></para></simplesect>....
Hi, I would like to include a Doxyfile to my project (to generate the documentation) but I am afraid that it might affect the code license due to the GNU GPL v2 license of Doxygen. Has anybody considered this before? starbucks menu price philippinesThe example Doxyfile in the Github repository mentions also the GPL in the header. Hi, I would like to include a Doxyfile to my project (to generate the documentation) but I am afraid that it might affect the code license due to the GNU GPL v2 license...
Hi, I would like to include a Doxyfile to my project (to generate the documentation) but I am afraid that it might affect the code license due to the GNU GPL v2 license of Doxygen. Has anybody considered this before? https://menuland.ph/starbucks-menu-price-in-philippines/The example Doxyfile in the Github repository mentions also the GPL in the header. Hi, I would like to include a Doxyfile to my project (to generate the documentation) but I am afraid that it might affect the code license due to...
Hi, I am having the following problem with doxygen (1.11.0) and Latex (MiKTeX-pdfTeX 4.19 (MiKTeX 24.4): I am trying to document C++ source, a minimal version to reproduce the problem is //---------------------------------------------------------------------------- /// @file doxytestnamespace.cc /// @brief minimal doxygen test file to reproduce namespace errors // /*! \namespace NAMESPACETEST \brief sample namespace test Sample namespace test */ namespace NAMESPACETEST { const double SAMPLE_VAR=48.12;...
Hi, I would like to include a Doxyfile to my project (to generate the documentation) but I am afraid that it might affect the code license due to the GNU GPL v2 license of Doxygen. Has anybody considered this before? The example Doxyfile in the Github repository mentions also the GPL in the header.
Hi, We are using Doxygen v1.9.2 for one of our projects build in C programming. We are facing issues with few static functions in our project as doxygen throwing warnings by pointing to those static function declarations. The above behavour is not common for all static functions used in our project. It is limited to very few static functions. Generally we update documentation at function definitions but warning pointing to function declaration. Below is the one sample warning: warning: Member < function...
Yes, use. GENERATE_XML then you can parse the XML to extract the info you need. The Extensions page describes several XML processing examples already built such as Doxygen.NET
22.11.2023 16:24:19 Marko Filipovic mark-o@users.sourceforge.net: Hi, I'm using doxygen to generate the xml detailed documentation of the functions for projects in C and Python. I found in-body comments really usefull in C code, because with them is possible to describe code in details, and later process xml when needed. I would like to ask if this option is also available for the Python code? And if it is, how can it be achived. Whichever configuration I have tried, or comments style, comments after...
Hi, I'm using doxygen to generate the xml detailed documentation of the functions for projects in C and Python. I found in-body comments really usefull in C code, because with them is possible to describe code in details, and later process xml when needed. I would like to ask if this option is also available for the Python code? And if it is, how can it be achived. Whichever configuration I have tried, or comments style, comments after the first line of "in-function" code are not reported in xml...
I've created a Collaboration Diagram by adding the argument "GENERATE_HTML = YES". Also important to note that my code contains doxygen groups. The diagram I received is attached here. The diagram describes the relations between the doxygen groups I created. It contains a purple dashed line without an arrow, this option does not exist in the doxygen documentation, the most similar option is a purple dashed line with an arrow, which is according to doxygen documentation: A purple dashed arrow indicated...
I've created a Collaboration Diagram by adding the argument "GENERATE_HTML = YES". Also important to note that my code contains doxygen groups. The diagram I received is attached here. The diagram describes the relation between the doxygen groups I created. It contains a purple dashed line without an arrow, this option does not exist in the doxygen documentation, the most similar option is a purple dashed line with an arrow, which is according to doxygen documentation: A purple dashed arrow indicated...
I've created a Collaboration Diagram Using by adding the argument "GENERATE_HTML = YES". Also important to note that my code contains doxygen groups. The diagram I received is attached here. The diagram describes the relation between the doxygen groups I created. It contains a purple dashed line without an arrow, this option does not exist in the doxygen documentation, the most similar option is a purple dashed line with an arrow, which is according to doxygen documentation: A purple dashed arrow...
I've created a Collaboration Diagram Using by adding the argument "GENERATE_HTML = YES". Also important to note that my code contains doxygen groups. The diagram I received is attached here. The diagram describes the relation between the doxygen groups I created. It contains a purple dashed line without an arrow, this option does not exist in the doxygen documentation, the most similar option is a purple dashed line with an arrow, which is according to doxygen documentation: A purple dashed arrow...
I've created a Collaboration Diagram Using by adding the argument "GENERATE_HTML = YES". Also important to note that my code contains doxygen groups. The diagram I recieved is attached here. The diagram describes the relation between the doxygen groups I created. It contains a purple dashed line without an arrow, this option does not exist in the doxygen documentation, the most similar option is a purple dashed line with an arrow, which is according to doxygen documentation: A purple dashed arrow...
I've created a Collaboration Diagram Using by adding the argument "GENERATE_HTML = YES". The diagram I recieved is attached here. It contains a purple dashed line without an arrow, this option does not exist in the doxygen documentation, the closest is a purple dashed line with an arrow, which is according to doxygen documentation: A purple dashed arrow indicated a "usage" relation, the edge of the arrow is labeled with the variable(s) responsible for the relation. Class A uses class B, if class...
I've created a Collaboration Diagram Using by adding the argument "GENERATE_HTML = YES". The diagram I recieved is attached here. It contains a purple dashed line without an arrow, this option does not exist in the doxygen documentation, the closest is a purple dashed line with an arrow, which is according to doxygen documentation: A purple dashed arrow indicated a "usage" relation, the edge of the arrow is labeled with the variable(s) responsible for the relation. Class A uses class B, if class...
I've created a Collaboration Diagram Using by adding the argument "GENERATE_HTML = YES". The diagram I recieved is attached here. It contains a purple dashed line without an arrow, this option does not exist in the doxygen documentation, the closest is a purple dashed line with an arrow, which is according to doxygen documentation: A purple dashed arrow indicated a "usage" relation, the edge of the arrow is labeled with the variable(s) responsible for the relation. Class A uses class B, if class...