public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: Arnaud Charlet <charlet@adacore.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH, ADA, DOC] PR 15479: Crossrefs and links
Date: Tue, 18 Mar 2008 21:55:00 -0000	[thread overview]
Message-ID: <20080318214745.GG2094@ins.uni-bonn.de> (raw)
In-Reply-To: <20080318075330.GC82298@adacore.com>

* Arnaud Charlet wrote on Tue, Mar 18, 2008 at 08:53:30AM CET:
> 
> > | language version.  (Please refer to @ref{Compiling Different Versions of
> > | Ada,,, gnat_ugn_^unw^vms^, @value{EDITION} User's Guide}, for details on
> > 
> > Do you know a better way?
> 
> Yes, I do: instead, we can modify the makefile to generate/rename the gnat_ugn
> to always the same name: gnat_ugn.info (or gnat_ugn.html, ...), so that
> there is no need to conditionalize references to this document in gnat_rm.texi

OK.  This still leaves a few questions open:

Should it still be possible to build the VMS version of the User's Guide
as well as the UNW version using xgnatugn, but both should now have the
same name?  Or should just the UNW version be renamed to gnat_ugn.info?
Should it still be possible with xgnatugn to generate an UNW version
with the gnat_ugn_unw name?

Asking here because I assume that there is some build process external
to GCC which generates the VMS version (the code in gcc/ada/Make-lang.in
doesn't do this now) and maybe wants to have a parallel installation of
the User's Guides for different systems.  It would really help if you
could point me to such an external build process if any, because
otherwise I am back to guessing about what is desired without knowing
the side conditions.

I assume maintainer-scripts/update_web_docs_svn should be adjusted to
generate gnat_ugn only, and install that, right?  Also I assume that
this change will make this patch less suitable for the 4.3 branch?

Thanks,
Ralf

  reply	other threads:[~2008-03-18 21:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-15 14:12 Ralf Wildenhues
2008-03-16 18:32 ` Arnaud Charlet
2008-03-16 22:08   ` Ralf Wildenhues
2008-03-17  9:47     ` Arnaud Charlet
2008-03-17 20:56       ` Ralf Wildenhues
2008-03-18  9:05         ` Arnaud Charlet
2008-03-18 21:55           ` Ralf Wildenhues [this message]
2008-03-18 22:05             ` Arnaud Charlet
2008-03-18 22:27               ` Ralf Wildenhues
2008-03-19  8:44                 ` Arnaud Charlet
2008-03-20 19:58                   ` Ralf Wildenhues
2008-03-21 11:38                     ` Arnaud Charlet

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=20080318214745.GG2094@ins.uni-bonn.de \
    --to=ralf.wildenhues@gmx.de \
    --cc=charlet@adacore.com \
    --cc=gcc-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).