From: Stephane Wirtel <stephane.wirtel@belgacom.net>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Stephane Wirtel <stephane.wirtel@belgacom.net>,
Martin Waitz <tali@admingilde.org>,
Pekka Enberg <penberg@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Documentation] Use doxygen or another tool to generate a documentation ?
Date: Sun, 21 Aug 2005 14:28:19 +0200 [thread overview]
Message-ID: <20050821122819.GA31784@localhost.localdomain> (raw)
In-Reply-To: <20050820173706.GA11079@mars.ravnborg.org>
Le Saturday 20 August 2005 a 19:08, Sam Ravnborg ecrivait:
> On Sat, Aug 20, 2005 at 11:19:41AM +0200, Stephane Wirtel wrote:
> > Le Saturday 20 August 2005 a 09:08, Sam Ravnborg ecrivait:
> > > >
> > > > Ok, with scripts/kernel-doc, I can produce some html files containing
> > > > the functions' documentation.
> > > >
> > > > make pdfdocs or others targets don't work :|
> > >
> > > You probarly need some additional packages.
> > > But it's not easy to help you with no log of what happened.
> > Yes, sorry,
> >
> > Kernel : 2.6.12 from the git repository of Linus.
> >
> > In make_docs.log.tar.bz2, you can find log files from make htmldocs,
> > make psdocs and make pdfdocs.
>
> From your log-files I could not see what went wrong. It seems to be
> error in the generated files.
> Maybe Martin can help - Martin?
No news from Martin,
Sam, Could you generate the documentation in PDF format, and send me ?
Thanks,
Stephane
--
Stephane Wirtel <stephane.wirtel@belgacom.net>
<stephane.wirtel@gmail.com>
next prev parent reply other threads:[~2005-08-21 12:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 21:34 [Documentation] Use doxygen or another tool to generate a documentation ? Stephane Wirtel
2005-08-19 21:46 ` Pekka Enberg
2005-08-19 23:23 ` Stephane Wirtel
2005-08-20 7:41 ` Sam Ravnborg
2005-08-20 9:19 ` Stephane Wirtel
2005-08-20 17:37 ` Sam Ravnborg
2005-08-21 12:28 ` Stephane Wirtel [this message]
2005-08-21 15:12 ` Martin Waitz
2005-08-21 18:32 ` Stephane Wirtel
2005-08-22 7:45 ` Martin Waitz
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=20050821122819.GA31784@localhost.localdomain \
--to=stephane.wirtel@belgacom.net \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@gmail.com \
--cc=sam@ravnborg.org \
--cc=tali@admingilde.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox