public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Arnaud Charlet <charlet@adacore.com>
To: David Malcolm <dmalcolm@redhat.com>
Cc: Joseph Myers <joseph@codesourcery.com>,
	Tom de Vries <Tom_deVries@mentor.com>,
	gcc-patches@gcc.gnu.org,	Arnaud Charlet <charlet@adacore.com>
Subject: Re: [Ada] convert GNAT doc to sphinx
Date: Thu, 26 Feb 2015 17:26:00 -0000	[thread overview]
Message-ID: <20150226171755.GB19466@adacore.com> (raw)
In-Reply-To: <1424970457.8624.56.camel@surprise>

Thanks for your feedback, very useful!

> How are you testing this?  When getting the jit docs to work I had to
> hack up the script somewhat to be able to test it on a development box
> (e.g. to cut back "MANUALS" to just libcpp to speed up testing).

That's a good question. Truth is that so far I'm not since I do not know
how to test it :-) That's why I wanted to minimize my changes and was asking
for help, since testing these changes is not very practical/easy.

> Don't you also need to preserve the Makefile at this stage, and indeed
> the .rst files?

When we'll switch the script to using sphinx for GNAT docs, yes.

For now the temporary state is that we're still building docs from the
.texi files (now generated by sphinx). Certainly not ideal but it more or
less does the job.

> To get sphinx-generated HTML for the jit onto the gcc website, I needed
> to patch the script in three places:
>   * the part above,
>   * to add an invocation of the Makefile, and
>   * to implement the copying up from the build location to the install
> location (since the jit docs have nested subdirectories, plus .js
> and .css files provided by sphinx).

Makes sense.

> Hope this is helpful

It definitely is!

Arno

  reply	other threads:[~2015-02-26 17:19 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
2015-02-25 16:00                 ` Joseph Myers
2015-02-26 17:18                 ` David Malcolm
2015-02-26 17:26                   ` Arnaud Charlet [this message]
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=20150226171755.GB19466@adacore.com \
    --to=charlet@adacore.com \
    --cc=Tom_deVries@mentor.com \
    --cc=dmalcolm@redhat.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).