public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Arnaud Charlet <charlet@adacore.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Tom de Vries <Tom_deVries@mentor.com>, gcc-patches@gcc.gnu.org
Subject: Re: [Ada] convert GNAT doc to sphinx
Date: Wed, 25 Feb 2015 15:50:00 -0000	[thread overview]
Message-ID: <20150225154753.GA26463@adacore.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1502251535230.12077@digraph.polyomino.org.uk>

> > I've added a -I gcc/gcc/ada/doc/gnat_ugn there, that's as far as my
> > knowledge goes for this script so I hope this is enough.
> 
> Well, since by default the find command deletes all files except those
> known to be documentation sources, you need at least to change it not to
> delete those particular files (and the actual RST sources of these
> manuals).

OK, I've applied the patch below, hopefully it should do the job.

> > I can help in transitioning the script to sphinx though, that would seem
> > more interesting/productive at this stage.
> 
> See the existing code to handle Sphinx documentation for the JIT.

That's a good reference. We'll need a more recent version of sphinx than
1.0 though (at least 1.2.2, or even better, 1.3b2 which is the version we use
at AdaCore).

Arno
--
--- update_web_docs_svn (revision 220961)
+++ update_web_docs_svn (working copy)
@@ -107,10 +107,8 @@
   svn -q export $SVNROOT/tags/$RELEASE gcc
 fi
 
-# Remove all unwanted files.  This is needed (a) to build the Ada
-# generator programs with the installed library, not the new one and
-# (b) to avoid packaging all the sources instead of only documentation
-# sources.
+# Remove all unwanted files.  This is needed to avoid packaging all the
+# sources instead of only documentation sources.
 # Note that we have to preserve gcc/jit/docs since the jit docs are
 # not .texi files (Makefile, .rst and .png), and the jit docs use
 # include directives to pull in content from jit/jit-common.h and
@@ -120,6 +118,7 @@
   -o -path gcc/gcc/doc/include/texinfo.tex \
   -o -path gcc/gcc/BASE-VER \
   -o -path gcc/gcc/DEV-PHASE \
+  -o -path "gcc/gcc/ada/doc/gnat_ugn/*.png" \
   -o -path "gcc/gcc/jit/docs/*" \
   -o -path "gcc/gcc/jit/jit-common.h" \
   -o -path "gcc/gcc/jit/notes.txt" \

  reply	other threads:[~2015-02-25 15:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20  9:26 Arnaud Charlet
2015-02-22 17:37 ` Tom de Vries
2015-02-22 18:30   ` Arnaud Charlet
2015-02-22 19:02     ` Tom de Vries
2015-02-22 19:35       ` Arnaud Charlet
2015-02-22 20:48         ` Tom de Vries
2015-02-23  2:28           ` Arnaud Charlet
2015-02-23  8:26             ` Tom de Vries
2015-02-25 12:02         ` Richard Biener
2015-02-25 11:05     ` Joseph Myers
2015-02-25 11:27       ` Arnaud Charlet
2015-02-25 11:35         ` Joseph Myers
2015-02-25 11:40           ` Arnaud Charlet
2015-02-25 15:43             ` Joseph Myers
2015-02-25 15:50               ` Arnaud Charlet [this message]
2015-02-25 16:00                 ` Joseph Myers
2015-02-26 17:18                 ` David Malcolm
2015-02-26 17:26                   ` Arnaud Charlet
2015-02-26 18:33                   ` Mike Stump
2015-03-03 10:42 ` Matthias Klose
2015-03-03 13:33   ` 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=20150225154753.GA26463@adacore.com \
    --to=charlet@adacore.com \
    --cc=Tom_deVries@mentor.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=joseph@codesourcery.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).