From: Luca Boccassi <bluca@debian.org>
To: Thomas Monjalon <thomas@monjalon.net>, bruce.richardson@intel.com
Cc: dev@dpdk.org, Timothy Redaelli <tredaelli@redhat.com>
Subject: Re: [PATCH v3] doc: support building HTML guides with meson
Date: Mon, 29 Oct 2018 10:01:08 +0000 [thread overview]
Message-ID: <1540807268.29722.1.camel@debian.org> (raw)
In-Reply-To: <1919106.6oOIkQuhtx@xps>
On Sat, 2018-10-27 at 23:54 +0200, Thomas Monjalon wrote:
> 20/09/2018 15:51, Timothy Redaelli:
> > On Thu, 20 Sep 2018 14:22:08 +0100
> > Luca Boccassi <bluca@debian.org> wrote:
> >
> > > From: Bruce Richardson <bruce.richardson@intel.com>
> > >
> > > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> > > Signed-off-by: Luca Boccassi <bluca@debian.org>
> >
> > Tested on Fedora 28 (sphinx 1.7.5) and RHEL 7.5 (sphinx 1.1.3)
> >
> > Tested-by: Timothy Redaelli <tredaelli@redhat.com>
>
> Applied, thanks
>
> In the build directory, docs are in
> - doc/api/api/
> - doc/guides/guides/
> Why having the last level of (redundant) directory?
Quirks due to the intersection of Meson and Sphinx/Doxygen and theirs
respective quirks - it needs to be a new directory, and it needs to be
called "guides/api" as that's what gets installed via ninja install.
Yes it's not the prettiest in the build tree - suggestions to improve
it are most welcome of course
--
Kind regards,
Luca Boccassi
prev parent reply other threads:[~2018-10-29 10:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 16:13 [PATCH] doc: support building HTML guides with meson Bruce Richardson
2018-09-11 20:36 ` Luca Boccassi
2018-09-11 21:47 ` Luca Boccassi
2018-09-12 9:36 ` Bruce Richardson
2018-09-12 9:48 ` Luca Boccassi
2018-09-12 10:13 ` Bruce Richardson
2018-09-12 12:08 ` Luca Boccassi
2018-09-19 13:48 ` [PATCH v2] " Luca Boccassi
2018-09-20 13:19 ` Timothy Redaelli
2018-09-20 13:22 ` [PATCH v3] " Luca Boccassi
2018-09-20 13:51 ` Timothy Redaelli
2018-10-27 21:54 ` Thomas Monjalon
2018-10-29 10:01 ` Luca Boccassi [this message]
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=1540807268.29722.1.camel@debian.org \
--to=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
--cc=tredaelli@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.