From: Kent Gibson <warthog618@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: linux-gpio@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [libgpiod][PATCH] doc: fix sphinx config for rtd
Date: Sat, 6 Jul 2024 10:54:56 +0800 [thread overview]
Message-ID: <20240706025456.GA13007@rigel> (raw)
In-Reply-To: <172016528819.6599.11422057058966562764.b4-ty@linaro.org>
On Fri, Jul 05, 2024 at 09:41:31AM +0200, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>
>
> On Fri, 05 Jul 2024 10:17:50 +0800, Kent Gibson wrote:
> > Generating the latest documentation on readthedocs is broken as the
> > index.html generated by Doxygen is now being overwritten by one
> > generated by Sphinx.
> >
> > Make Sphinx generate a differently named root page that does not
> > conflict with the index.html generated by Doxygen.
> >
> > [...]
>
> Applied, thanks!
>
> [1/1] doc: fix sphinx config for rtd
> commit: 824c1f39347c2ef46919dfc45e8247441b908827
>
Btw, I ran across this while updating RTD to v2.1 - their default build
config has changed since I last updated, so that didn't go as smoothly
as I had anticipated (the plan was to switch the branch the generation
uses from my fork to your github repo, but now that can wait til v2.2).
I am also looking at reworking the documentation to use Sphinx/Breathe
to generate the html from the xml that Doxygen generates, and
incorporting documentation for the Python bindings, but looking is
about as far as I've gotten so far.
Not sure what to do about the Rust bindings. I was assuming I could
just link to docs.rs, but the build there[1] is broken.
Can we fix that?
Cheers,
Kent.
[1] https://docs.rs/crate/libgpiod/latest
next prev parent reply other threads:[~2024-07-06 2:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 2:17 [libgpiod][PATCH] doc: fix sphinx config for rtd Kent Gibson
2024-07-05 7:41 ` Bartosz Golaszewski
2024-07-06 2:54 ` Kent Gibson [this message]
2024-07-08 11:48 ` Bartosz Golaszewski
2024-07-08 12:43 ` Kent Gibson
2024-07-08 13:50 ` Bartosz Golaszewski
2024-07-08 15:15 ` Kent Gibson
2024-07-08 15:19 ` Bartosz Golaszewski
2024-07-08 15:29 ` Kent Gibson
2024-07-09 9:34 ` Kent Gibson
2024-07-09 15:48 ` Bartosz Golaszewski
2024-07-10 1:48 ` Kent Gibson
2024-07-10 7:55 ` Bartosz Golaszewski
2024-07-09 8:22 ` Viresh Kumar
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=20240706025456.GA13007@rigel \
--to=warthog618@gmail.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linux-gpio@vger.kernel.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