Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jeremy Bennett <jeremy.bennett@embecosm.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb@sourceware.org
Subject: Re: Documentation generated from sources proposal
Date: Tue, 13 Oct 2009 08:23:00 -0000	[thread overview]
Message-ID: <1255422217.4479.47.camel@thomas> (raw)
In-Reply-To: <83tyy4igm2.fsf@gnu.org>

On Mon, 2009-10-12 at 20:58 +0200, Eli Zaretskii wrote:
> > Date: Mon, 12 Oct 2009 18:14:24 +0200
> > From: Jan Kratochvil <jan.kratochvil@redhat.com>
> > 
> > May the GDB project start using some tool to format documentation from the
> > sources?  One could move the appropriate parts of gdb/doc/gdbint.texinfo into
> > gdb/*.c along the patches being submitted, keeping in gdb/doc/gdbint.texinfo
> > only the abstract parts in the future.
> 
> Assuming the license problem is resolved, I'll support this, provided
> that someone steps forward to do the initial job of moving the
> up-to-date parts of gdbint to the sources and developing the
> infrastructure for processing comments into Texinfo.

I support this approach - we use it in house all the time. Once the
legal side is sorted out, I'm quite happy to contribute by migrating the
relevant parts of gdbint to the sources.

One suggestion: gtk-doc is not that general purpose. Doxygen (as
recommended by the gtk-doc website) might prove a more flexible
alternative.

The one caveat is that neither of these programs can generate Texinfo,
so generating .info files will be hard (all the other output formats,
including man pages can be generated directly, at least by Doxygen). In
principle it could be done (gtk-doc->docbook->texinfo->info or
doxygen->XML->texinfo->info), but who knows what the output might end up
like!

ATB,


Jeremy

-- 
Tel:      +44 (1590) 610184
Cell:     +44 (7970) 676050
SkypeID: jeremybennett
Email:   jeremy.bennett@embecosm.com
Web:     www.embecosm.com


  reply	other threads:[~2009-10-13  8:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-12 16:14 Jan Kratochvil
2009-10-12 17:12 ` Tom Tromey
2009-10-12 17:16   ` Jan Kratochvil
2009-10-12 18:00     ` Daniel Jacobowitz
2009-10-12 18:07       ` Jan Kratochvil
2009-10-12 18:13         ` Daniel Jacobowitz
2009-10-12 18:20           ` Jan Kratochvil
2009-10-12 18:26             ` Tom Tromey
2009-10-12 18:30               ` Jan Kratochvil
2009-10-12 18:54   ` Eli Zaretskii
2009-10-12 19:10     ` Daniel Jacobowitz
2009-10-12 19:25     ` Tom Tromey
2009-10-12 20:23       ` Eli Zaretskii
2009-10-12 18:57 ` Eli Zaretskii
2009-10-13  8:23   ` Jeremy Bennett [this message]
2009-10-13 18:16     ` Eli Zaretskii
2009-10-13 19:13       ` Jan Kratochvil
2009-10-13 19:18         ` Eli Zaretskii
2009-10-27 10:07 ` Mark Kettenis

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=1255422217.4479.47.camel@thomas \
    --to=jeremy.bennett@embecosm.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    /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