From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: ROSSIER Daniel <Daniel.Rossier@domain.hid>,
xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] broken docs
Date: Mon, 30 Jan 2006 13:59:12 +0100 [thread overview]
Message-ID: <43DE0DA0.2050307@domain.hid> (raw)
In-Reply-To: <17374.2360.273205.998312@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1808 bytes --]
Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
> > ROSSIER Daniel wrote:
> > > Dear Xenomai workers,
> > >
> > > Would it be possible to have an updated API documentation for Xenomai
> > > 2.0.x ? (I mean with formal parameters in function prototypes)
> > >
> > > I tried to regenerate it with make generate-doc, but it seems that a
> > > SVN working dir is required.
>
> make generate-doc is needed for maintenance only. If you want to
> generate doxygen documentation, simply add --enable-dox-doc to Xenomai
> configure command line.
>
> > >
> > > It would be great.
> >
> > I just had a "quick" look at the status of the documentation in
> > SVN-trunk (2.1). Unfortunately, doxygen is a terrible tool (to express
> > it politely) when it comes to tracking down bugs in your formatting.
> > Something is broken in all modules except RTDM, and although I spent *a
> > lot* of time in getting RTDM correctly formatted, I cannot tell what's
> > wrong with the rest. This will require some looooong evenings of
> > continuous patching the docs, recompiling, and checking the result. Any
> > volunteers - I'm lacking the time? :-/
>
> Looking at the difference between RTDM documentation blocks and the
> other modules is that the other modules use the "fn" tag. Removing the
> "fn" tag from other modules documentation blocks seems to solve the
> issue.
>
Indeed, works. Amazingly blind I was.
Anyway, it still needs some work to remove that stuff (I wonder what the
"correct" usage of @fn is...) and to wrap functions without bodies via
"#ifdef DOXYGEN_CPP" like RTDM does. At this chance, I would also
suggest to replace all \tag by @tag for the sake of a unified style (and
who knows what side effects mixing up both may have).
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2006-01-30 12:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-30 10:55 [Xenomai-core] broken docs ROSSIER Daniel
2006-01-30 12:17 ` Jan Kiszka
2006-01-30 12:40 ` Gilles Chanteperdrix
2006-01-30 12:59 ` Jan Kiszka [this message]
2006-02-04 12:24 ` Jan Kiszka
2006-02-05 13:06 ` Gilles Chanteperdrix
-- strict thread matches above, loose matches on Subject: below --
2006-01-18 19:03 Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43DE0DA0.2050307@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=Daniel.Rossier@domain.hid \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.