From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Mike Stump <mrs@apple.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: HTML docs
Date: Thu, 10 Apr 2003 09:11:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.53.0304101003090.30296@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <361CCD9C-6AF4-11D7-8AD9-003065A77310@apple.com>
On Wed, 9 Apr 2003, Mike Stump wrote:
> Can we add a convenience target to the makefile to generate end user
> html docs?
Obviously you need to add (and document) a Make-lang.in hook to do this in
front end directories. I'd say that the target also needs to be available
at toplevel (with support added in the fastjar directory as well) so using
the target does genuinely build generate HTML from all the Texinfo manuals
that "make dvi" generates DVI from.
I'd like configure support for optionally installing the HTML manuals
(under $prefix/share/doc/gcc or similar) but that can be a separate patch
and I don't know whether a --docdir or similar configure option was ever
agreed on for Autoconf.
This patch builds in HTML/cpp-$(version) etc. which breaks links between
the manuals, which expect the directories to be called just "gcc", "cpp",
etc.; any versioned directory needs to be at a higher level above all the
manuals.
--
Joseph S. Myers
jsm28@cam.ac.uk
next prev parent reply other threads:[~2003-04-10 9:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-10 1:31 Mike Stump
2003-04-10 9:11 ` Joseph S. Myers [this message]
2003-04-11 0:34 ` Mike Stump
2003-04-11 16:33 ` Joseph S. Myers
2003-04-11 22:31 ` Mike Stump
2003-04-11 22:52 ` Joseph S. Myers
2003-04-11 23:39 ` Mike Stump
[not found] <20020813155330.GA6618@compsoc.man.ac.uk>
[not found] ` <20020813160008.GA6652@compsoc.man.ac.uk>
2002-08-13 9:31 ` documentation.html patch Phil Edwards
[not found] ` <20020815122950.GA81561@compsoc.man.ac.uk>
[not found] ` <20020815111953.56f4ef0d.bkoz@redhat.com>
2002-08-15 13:23 ` HTML docs Phil Edwards
[not found] ` <20020819120624.GA10651@compsoc.man.ac.uk>
2002-08-19 17:48 ` Phil Edwards
2002-08-20 10:57 ` Janis Johnson
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=Pine.LNX.4.53.0304101003090.30296@kern.srcf.societies.cam.ac.uk \
--to=jsm28@cam.ac.uk \
--cc=gcc-patches@gcc.gnu.org \
--cc=mrs@apple.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).