From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org, David Betz <david.betz@domain.hid>
Subject: Re: [Xenomai-help] Native API manual in PDF format?
Date: Sun, 08 Oct 2006 20:00:32 +0200 [thread overview]
Message-ID: <45293CC0.8040204@domain.hid> (raw)
In-Reply-To: <17705.13155.675021.10130@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]
Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
> > David Betz wrote:
> > > Is there a PDF version of the Native API manual available? I'd like to
> > > be able to print a copy for reference.
> >
> > You can generate your own version: Set "GENERATE_LATEX = YES" in
> > doc/doxygen/Doxygen.in, build the documentation (don't forget to enable
> > it on configure), go to doc/doxygen/latex in your build directory and
> > run "make". The result is refman.pdf, a >500 pages monster (2.5M) that
> > looks rather unhandy to me. Maybe one can tune things and drop out
> > parts, you may want to play a bit with doxygen.
>
> I split the 500 pages monster into four parts; nucleus, native skin,
> rtdm skin and posix skin. I temporarily put them at the address:
> http://download.gna.org/xenomai/doxygen/
>
> If nobody dislikes them, they could be commited in the repository.
>
That would also mean we are going to keep them in sync with new release,
i.e. you can generate them automatically? Then I'm all for it! I just
want to avoid the RTAI effect: documentation all over the place, but
mostly decades old, useless, and -even worse- confusing.
Hmm, and I wonder why you were able to compress a PDF that much. I
thought PDF can do this fairly well on its own.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2006-10-08 18:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-20 14:00 [Xenomai-help] Native API manual in PDF format? David Betz
2006-09-21 19:14 ` Jan Kiszka
2006-10-08 17:20 ` Gilles Chanteperdrix
2006-10-08 18:00 ` Jan Kiszka [this message]
2006-10-08 18:42 ` Gilles Chanteperdrix
2006-10-08 18:55 ` Gilles Chanteperdrix
2006-10-08 19:25 ` Jan Kiszka
[not found] ` <452A17F1.9070803@domain.hid>
2006-10-09 10:24 ` Jan Kiszka
2006-10-09 19:33 ` Bruno Rouchouse
-- strict thread matches above, loose matches on Subject: below --
2006-10-09 10:51 Marcelo Coelho
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=45293CC0.8040204@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=david.betz@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.