[Doxygen-users] Including a .tag file for a library which itself includes a .tag file can provoke duplicate anchor warnings

I have three libraries - libA, libB and libC. libA has a .dox file, which contains the following anchors: \section First_Section First Section \subsection First_Subsection First Subsection libB includes the tag file for libA as follows: @TAGFILES = $(DOXY_OUTPUT)/../libA/libA.tag=

[Doxygen-users] Documented symbol `enum ABC NamespaceA::NamespaceB::XYZ' was not declared or defined

In doxygen, I am getting the following warning: Documented symbol `enum DDD NamespaceA::NamespaceB::XYZ' was not declared or defined. The enum in question is not even documented in doxygen so I don't know why the message above is showing up. Note that the enum is outside a class. namespace Namesp

[Doxygen-users] Warning message documented symbol enum was not declared or defined

In doxygen, I am getting the following warning: Documented symbol `enum DDD NamespaceA::NamespaceB::XYZ' was not declared or defined. The enum in question is not even documented in doxygen so I don't know why the message above is showing up. Note that the enum is outside a class. namespace Namesp

Re: [Doxygen-users] Namespace members behaviour in 1.8.13

Updating this with some more detailed information after further investigation: I am using Doxygen 1.8.13. Previously I was using Doxygen 1.8.10 With Doxygen 1.8.10, when I generated documentation for a library using a file from another library, a "Namespace Members" page was generated in the f

Re: [Doxygen-users] What is the reason for no alphabetical organisation of namespace members in certain libraries

To reply to my own question... This is caused by the number of namespace members. When there are not many, the list of members are not organised under the alphabetical letter with which the namespace member begins, however, when there are a lot of namespace members, these are organised under the a

[Doxygen-users] What is the reason for no alphabetical organisation of namespace members in certain libraries

In the namespace members page, why do some libraries generate lists of members organised alphabetically (i.e. when you click on "Namespaces", then "Namespace Members", then "All", there is a list of namespace members beginning with "a" under the title "a", then those with "b" under the title "b" et

[Doxygen-users] Namespace members behaviour in 1.8.13

I am using Doxygen 1.8.13. Previously I was using Doxygen 1.8.10 I am generating the documentation for a library libA, which, in has as its @INPUT tag only the following: @INPUT = ../libB/AFile.h \ docs/Overview.html AFile.h contains lots of includes of header files from other librarie

[Doxygen-users] namespace members varying behaviour on Doxygen 1.8.10

I generate doxygen documentation in Linux and Windows. However, there is a difference in the "Namespace Members" section between the resulting generated documentation. In the generated Linux documentation: - In the "Namespace Members" section, in the "All" tab, when I click on the letter "a", the

Re: [Doxygen-users] Additional underscore character added in links to included files 1.8.12

I have added an example to the bug report. -- View this message in context: http://doxygen.10944.n7.nabble.com/Additional-underscore-character-added-in-links-to-included-files-1-8-12-tp7734p7736.html Sent from the Doxygen - Users mailing list archive at Nabble.com.

[Doxygen-users] Additional underscore character added in links to included files 1.8.12

Hi, In 1.8.10, whenever there was a line as follows in a source file: include "folderA/fileX.h" the link was constructed as follows: href="../folderA/fileX_8h.html" However, since I upgraded to 1.8.12, the link changes, and becomes: href="../folderA/fileX__8h.html" An additional underscore is ad

[Doxygen-users] Internal inconsistency scope for class not found with .tag file

Doxygen 1.8.10 Library A uses a .tag file from Library B When I generate the documentation for Library A, I get the following type of warning: LibraryB/LibraryB.tags:1: warning: Internal inconsistency: scope for class namespaceX::namespaceY::ClassX::SubclassX::StructX not found! Note that when I g

[Doxygen-users] How to do a Typedef tag for a forward declared macro

Typedef tag for a forward declared macro does not work Doxygen 1.8.10 The following properties are set in the Doxyfile ENABLE_PREPROCESSING = YES MACRO_EXPANSION= YES EXPAND_ONLY_PREDEF = YES EXPAND_AS_DEFINED = FWD_DECL_SHD_PTR In a test.dox.cpp file, I have the following:

[Doxygen-users] Changing order of modules without using INPUT tag

Hi, I have three .dox files which define groups, as follows ModuleA.dox /*! \defgroup Module_A Module A */ ModuleB.dox /*! \defgroup Module_B Module B \ingroup Module_A */ ModuleC.dox /*! \defgroup Module_C Module C \ingroup Module_A */ Generating the documentation, the modules are listed a

Re: [Doxygen-users] Doxygen does not generate documentation from html pages

Hi Albert, I did search the forums, without success - I was perhaps being too specific about my search term, checking for "html" related answers only. However, I did not check the FAQ, the one you mention answers my question. Thanks. -- View this message in context: http://doxygen.10944.n7.nabb

[Doxygen-users] Doxygen does not generate documentation from html pages

Doxygen 1.8.10. I generate documentation from a mix of .h files and .html files. I was using Doxygen 1.8.7 and the documentation was generated correctly from these sources. However, I have just installed 1.8.10 and see that the .html files I reference in my INPUT tag do not generate anything in th

[Doxygen-users] Confusion between documentation of function and inner class

Doxygen 1.8.7 In a class, I have a function within which an inner class is declared. //*! This is a test class */ class TestClass { /*! \brief A function which does something /* \param param_A this is the first parameter of doSomething function /* \param param_B this is the second parameter of

Re: [Doxygen-users] The details of a function template are not accessible in generated documentation

Hi Albert, Did you try to generate the documentation with the file I supplied above and did it work for you after you documented the namespace? Because, even when I document the namespace, I have the same problem. I have submitted the issue on bugzilla. Diarmuid -- View this message in context:

[Doxygen-users] The details of a function template are not accessible in generated documentation

Doxygen 1.8.7 I am generating documentation for the following file (don't ask me what the file is for, I don't know, I'm not the programmer..): /*! * \file TestHelpMe.h * \brief Here is the brief text. * \details Here are the details */ namespace NAMESPACE_X { /*! \brief Here is the brief

Re: [Doxygen-users] Warning message when documenting overloaded functions.

No, if I omit the \fn I still get the warning message -- View this message in context: http://doxygen.10944.n7.nabble.com/Warning-message-when-documenting-overloaded-functions-tp7145p7150.html Sent from the Doxygen - Users mailing list archive at Nabble.com. ---

[Doxygen-users] Warning message when documenting overloaded functions.

I am getting a warning message when documenting overloaded functions. I have an implementation class and a header class. The header class declares two virtual functions, the second of which overloads the first. ClassA.h /virtual void doSomething(int i); virtual void doSomething(int i,int j);/

[Doxygen-users] How to create a page which does not appear anywhere in left hand menu

I have a library for which I am generating doxygen documentation. There is a module (module_A) in that library which contains a description of various details in relation to this module (on generated page group_moduleA.html). I want to add several pages to give additional details about that module,

[Doxygen-users] Mysterious singleton in .tag file causes warnings

Hi, In our system, we have a namespace ABC, which refers to std classes such as List, Deque etc I generate a .tag file in the library TestLib, which uses some of these classes. When I generated that .tag file with 1.8.7, I saw the following in the .tag file: ABC::Deque

[Doxygen-users] Is it possible to remove a nav item without corresponding tree item being removed?

I would like to remove certain of the top navigation links, but preserve those links in the tree index on the left hand side of the generated documentation. Is this possible? In the DoxygenLayout.xml file, there is no way to do this - once I change a nav item, setting visible to "no", the item is

Re: [Doxygen-users] TAGFILES not working consistently in 1.8.7 (RHEL6)

I notice the same warning message, but in slightly different circumstances. Basically, it occurs when library A includes a tag file to library B where both libraries have been generated using 1.8.7 on Red Hat 5. Where both libraries are generated using Red Hat 6 (1.8.7), I do not see this warning m

Re: [Doxygen-users] TAGFILES not working consistently in 1.8.7 (RHEL6)

Sorry, my mistake. I see the problem with Red Hat 6 generated documentation too. However, I don't see what the practical effect of it is. All my references appear to be functioning nonetheless. -- View this message in context: http://doxygen.10944.n7.nabble.com/TAGFILES-not-working-consistently

Re: [Doxygen-users] Forward declaration of typedef results in warning

CRO etc.) so the problem can be reproduced? Albert On Wed, Mar 12, 2014 at 12:09 PM, didje <[hidden email]> wrote: Forward declaration of typedef results in warning: Warning: documented symbol TypeDef_A_ptr was not declared or defined. Example (Note: the macro below forward declares a t

[Doxygen-users] Forward declaration of typedef results in warning

Forward declaration of typedef results in warning: Warning: documented symbol TypeDef_A_ptr was not declared or defined. Example (Note: the macro below forward declares a typedef called "TypeDef_A_ptr") ClassA.h FORWARD_DECLARE_MACRO(TypeDef_A) ClassA.cpp /* \typedef typedef TypeDef_A_ptr *

[Doxygen-users] enum value of "NONE" is not understood by Doxygen.

In this example: AClass.h enum AnEnum { NONE=0, A_VALUE, B_VALUE }; AClass.cpp /*! \enum AnEnum * \brief Various useful values */ /*! \var A_VALUE * \brief THe value of A */ /*! \var B_VALUE * \brief THe value of B */ /*! \var NONE * \brief A value of zero */ Doxygen gives me the war

Re: [Doxygen-users] Namespace page not generated

Posted on bugzilla Bug 725201 -- View this message in context: http://doxygen.10944.n7.nabble.com/Namespace-page-not-generated-tp6497p6514.html Sent from the Doxygen - Users mailing list archive at Nabble.com. -- Flow

[Doxygen-users] FULL_PATH_NAMES does not prepend path names to files

I have two libraries libA and libB. libA contains a file Action.h libB contains a file action.h I want to generate doxygen documentation in the same output directory for both libraries. This directory is to be used in Windows, for which action.html and Action.html are unfortunately considered t

Re: [Doxygen-users] Namespace page not generated

The library where this problem occurs (Library A) includes a tagfile from another library (Library B) which contains an identically named namespace ("ABC"). When I remove the tagfile from the makefile.doxygen of library A, then the namespace page "ABC" is indeed generated. However, the problem is t

[Doxygen-users] Namespace page not generated

I have a number of namespaces in a library. When I generate the documentation for this library and look at the "Classes" section and click on "Class List", I see the list of namespaces in the library, as well as a description of each namespace. However, for some of these namespaces, no namespace p

Re: [Doxygen-users] \copydoc warning - target of \copydoc command not found

I discovered the solution to this problem. I set following properties in the doxyfile to YES and, hey presto, copydoc statements found the inner classes: EXTRACT_ALL = YES EXTRACT_PRIVATE = YES EXTRACT_STATIC= YES I think EXTRACT_STATIC was not necessary to fix this, but I

Re: [Doxygen-users] \copydoc warning - target of \copydoc command not found

Here is an exchange of mails I had on the above problem, which did not unfortunately, resolve it: Hi Arthur I tried removing the outer class specification, but unfortunately that did not work, as you thought. Well, that's not quite true - bizarrely it worked for a method with a return type of void

[Doxygen-users] \copydoc warning - target of \copydoc command not found

I have hundreds (almost one thousand!) of \copydoc statements which are producing the following warning message. Warning: target testClassX::innerClassX::getYes() of \copydoc command not found Here is the situation. There is a C++ class, called testClassX.cpp Here are its contents: // Start testC

[Doxygen-users] \copydoc warning message for inner class: target of \copydoc not found

I have hundreds (almost one thousand!) of \copydoc statements which are producing the following warning message. Warning: target testClassX::innerClassX::getYes() of \copydoc command not found Here is the situation. There is a C++ class, called testClassX.cpp Here are its contents: // Start testC

Re: [Doxygen-users] Namespace seems to be imported from referenced .tag file

Not sure how to edit my original post, so here is a better statement of the problem. I created two projects - TestProject1 and TestProject2 TestProject1 Contains 1 header file, as follows: XBO.h /*! \brief XBO is boring*/ namespace XBO { /*! \brief XBONestedNS is al

Re: [Doxygen-users] What version of RedHat for 1.8.4 and 1.8.3

Thanks Dimitri, I do not know which RedHat was used to compile 1.8.4. I am investigating and will post back here when I have found out. -- View this message in context: http://doxygen.10944.n7.nabble.com/What-version-of-RedHat-for-1-8-4-and-1-8-3-tp6180p6200.html Sent from the Doxygen - Users m

[Doxygen-users] What version of RedHat for 1.8.4 and 1.8.3

I have a doxygen installation of 1.8.4. When I use it with Red Hat 6, it generates the doc correctly. However, when I use it with Red Hat 5, it fails, producing the following error message: FATAL: kernel too old 4974 Segmentation fault Doxygen run failed Is Doxygen 1.8.4 incompatible with Red

[Doxygen-users] Namespace seems to be imported from referenced .tag file

I am using Doxygen 1.8.4. I see the following problem which did not happen with my previous Doxygen version - 1.7.1.2 I have two libraries. LibraryA contains classes belonging to namespace nm1. LibraryB contains classes belonging to namespace nm2 Tagfiles are generated for LibraryA (A.tag) and Li

[Doxygen-users] Does dot not work with gif files?

I am testing Doxygen 1.8.3 using modifications to our existing Doxygen.template file. For the DOT_IMAGE_FORMAT tag, I tried "gif" In the description for that tag (as generated by running doxygen -u from the 1.8.3 sources) is the following: /"The DOT_IMAGE_FORMAT tag can be used to set the image for

[Doxygen-users] No uniquely matching class member found for template

Doxygen 1.7.1.2 I'm getting the following warning (and lots more like them) Reading ClassX.h:99: warning: no uniquely matching class member found for template < TTemplateX > void NS::ClassX< TTemplateX >::functionX(std::istream &(*ab)(std::istream &)) Possible candidates: void NS::ClassX<

[Doxygen-users] warning: no uniquely matching class member found for template

In class IClass.h is the following code: template void IClass::funcX(std::istream& (*xy)(std::istream&)) { _parser->funcX (xy); } Doxygen produces the following output upon parsing it: warning: no uniquely matching class member found for template < TClass > Doxygen then s

[Doxygen-users] warning: documented function 'XXXX' was not declared or defined.

I see lots of warning messages in Doxygen saying: warning: documented function '' was not declared or defined. (where is the name of the function) All the functions causing this problem are preceded by _ or ~ I am not a C++ programmer, so I'm not sure what that signifies in programming