So I have a doxygen layout XML file that I'm using for the sole
purpose of just adding a tab group with some tabs under it. I don't
care about the rest of it. Most importantly, when I upgrade Doxygen in
the future, I want the rest of the stuff to generate default like it
normally does as if the lay
Would still love some advice on this if possible.
On Thu, Jun 29, 2017 at 3:16 PM, Robert Dailey wrote:
> I have integrated Doxygen documentation generation into CMake via tag
> files. Each dependency on a library introduces a tag file dependency.
> So far all of this is going great; bu
I have integrated Doxygen documentation generation into CMake via tag
files. Each dependency on a library introduces a tag file dependency.
So far all of this is going great; but there's no "central" landing
page that connects everything together.
What would be the best way to manage a central / m
tem.
>
> -- Philip Grenon
>
> -Original Message-
> From: Robert Dailey [mailto:rcdailey.li...@gmail.com]
> Sent: Tuesday, September 30, 2014 1:42 PM
> To: Doxygen
> Subject: [Doxygen-users] Bug with markdown for numbered lists?
>
> I have the following Doxygen doc
I have the following Doxygen documentation block in C++:
http://pastebin.com/9jBZtV9q
As you can see, I use consecutive 1's to number my lists
programmatically (I want Doxygen to do the numbers for me). When I use
this format, however, the formatting for the numbered lists does not
work. Instead,
that determines if there is any "meaningful" content
in a namespace before parsing it out.
Great work!
On Tue, Apr 8, 2014 at 1:53 PM, Dimitri van Heesch wrote:
>
> On 08 Apr 2014, at 15:33 , Robert Dailey wrote:
>
>> In my code I have a couple of forward declarations o
In my code I have a couple of forward declarations of classes in other
distant, unrelated namespaces:
namespace foo
{
class bar;
}
These get parsed out by Doxygen (v1.8.6) and appear empty in the HTML
output. Is there a way that Doxygen can be "smart" enough to ignore a
namespace if there isn
I like the style that the official Doxygen documentation uses. Can
someone provide directions on how to extract it and use it for my own
personally generated documentation? I tried just copying the CSS but
there are also some content files it needs, but I'd have to keep those
locally and change the
or this problem?
>
> Albert
>
>
>
>
> On Thu, Sep 12, 2013 at 8:16 PM, Robert Dailey
> wrote:
>>
>> Hey Albert thanks for looking into this. I'm using version 1.8.5 on
>> Windows. I have attached a sample for you, slightly different from
>> what
I find difficulty in both automatic link generation *and* @copydoc
when it comes to 'const' overloaded member methods. Example:
class foo
{
public:
Object* getObject();
Object const* getObject() const;
};
I have JAVADOC_AUTOBRIEF enabled. My documentation for the class above is:
class foo
{
I have the following:
namespace foo {
class Attachment {
public:
std::string& data();
std::string const& data() const;
void data( std::string& data );
};
}
I'm trying to link to it automatically via some simple documentation in a list:
/**
* Does the following:
* - Item 1
* - Item
I have the following:
namespace foo {
/// Document this constant
static SomeType const NO_VALUE = 0;
class MyClass {
public:
/**
* Talk about NO_VALUE here
*/
void some_function( SomeType val = NO_VALUE ) {}
};
} // end namespace
some_function() uses the globally defined const
No one knows? :(
On Mon, Apr 29, 2013 at 4:14 PM, Robert Dailey wrote:
> I have 2 files that I am writing documentation in. In file 1, I have
> defined a reference link:
>
> [reflink]: @ref secreflink "reflink"
>
> In file 1, when I do [reflink] it works just fine. H
I have 2 files that I am writing documentation in. In file 1, I have
defined a reference link:
[reflink]: @ref secreflink "reflink"
In file 1, when I do [reflink] it works just fine. However, in file 2
if I try to use [reflink] it is not parsed. Seems like reference links
can only be used within
I have documentation I'd like to write for some functions in my CMake
scripts. Does doxygen support parsing documentation from cmake
scripts? If not, is it easy to add support? How would I do that?
--
Precog is a next-gene
I found out the problem. This has to do with JAVADOC_AUTOBRIEF. I have
filed a bug here:
https://bugzilla.gnome.org/show_bug.cgi?id=697233
On Tue, Apr 2, 2013 at 1:06 PM, Robert Dailey wrote:
> I'm seeing that the "Generating" text that gets printed for each
> sca
I'm seeing that the "Generating" text that gets printed for each
scanned source file gets interrupted when a warning appears in that
file. Here is some example output:
1>Generating code for file viewnote.cpp...
1>Generating code for file viewnote.h...
1>Generating file documentation...
1>Generatin
17 matches
Mail list logo
