public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephane Wirtel <stephane.wirtel@belgacom.net>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Stephane Wirtel <stephane.wirtel@belgacom.net>,
	Pekka Enberg <penberg@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [Documentation] Use doxygen or another tool to generate a documentation ?
Date: Sat, 20 Aug 2005 11:19:41 +0200	[thread overview]
Message-ID: <20050820091941.GA15936@localhost.localdomain> (raw)
In-Reply-To: <20050820074106.GA15162@mars.ravnborg.org>

[-- Attachment #1: Type: text/plain, Size: 626 bytes --]

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.

Thanks, 

			Stephane



-- 
Stephane Wirtel <stephane.wirtel@belgacom.net>
                <stephane.wirtel@gmail.com>



[-- Attachment #2: make_docs.log.tar.bz2 --]
[-- Type: application/octet-stream, Size: 3152 bytes --]

  reply	other threads:[~2005-08-20  9:20 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 [this message]
2005-08-20 17:37         ` Sam Ravnborg
2005-08-21 12:28           ` Stephane Wirtel
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=20050820091941.GA15936@localhost.localdomain \
    --to=stephane.wirtel@belgacom.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@gmail.com \
    --cc=sam@ravnborg.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