Hi,
I am new to usage of Doxygen, Sphinx and Breathe.
My requirement is to generate a html file per directory, which contains
source files written in C language.
To illustrate:
dir1
- file1.h
- file1.c
dir2
- file2.h
- file2.c
...
I used Doxygen to generate xml files, which looks ok.(fi
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
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
> From: Florian Lindner
> Date: 15.07.2014 10:56
>
> Hello,
>
> I have a lot of comments like that:
>
>/**
> * @brief Limit of iterations during one timestep.
> */
>int _maxIterations;
>
> which makes it three lines of code for one line of comment. What is the best
> way to achieve
Hi Florian.
>From your link I can tell that for example
int _maxIterations; ///< Limit of iterations during one timestep.
Should work.
Just scroll a bit down for a lot of alternatives regarding 2 liners and 1
liners and choose the one that you like most.
Kind regards,
Stefan.
-Original Messa
Hello Dimitri,
Thanks for your quick reply.
On 14.07.2014, at 20:29, Dimitri van Heesch wrote:
> Hi Torsten,
>
> Seems like a symbol definition has itself as container, which is not good
> (and not possible normally).
> Can you enable the commented out code in Definition::qualifiedName()?
> T
Hello,
I have a lot of comments like that:
/**
* @brief Limit of iterations during one timestep.
*/
int _maxIterations;
which makes it three lines of code for one line of comment. What is the best
way to achieve the same commentary with one line of code?
At http://www.stack.nl/~dimit
