[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72nhrQsUcxm-1bsBEaGVbRgmAC=mVxrQ+A7TLcVuOer9oQ@mail.gmail.com>
Date: Mon, 24 Nov 2025 02:51:40 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
Cc: Carlos Bilbao <carlos.bilbao@...nel.org>,
Linux Doc Mailing List <linux-doc@...r.kernel.org>, Jonathan Corbet <corbet@....net>,
Mauro Carvalho Chehab <mchehab@...nel.org>, linux-kernel@...r.kernel.org,
Miguel Ojeda <ojeda@...nel.org>
Subject: Re: [PATCH 0/1] fix rustdoc build detection
On Fri, Nov 21, 2025 at 10:41 AM Mauro Carvalho Chehab
<mchehab+huawei@...nel.org> wrote:
>
> I'm not talking about stop using rustdoc. I'm talking about using
> it to output on a format that Sphinx can understand, and let Sphinx
> do the final output, solving cross-references.
By stop using `rustdoc` I meant its "normal" (HTML) output, i.e. the
webpage with all its features and so on.
The JSON support is unstable so far:
https://github.com/rust-lang/rust/issues/76578
And even then, I imagine it will always still require a kernel config,
so that isn't an advantage either.
Thus trying to mimic what `rustdoc` does is probably going to be a lot
of work to maintain, to likely get a worse result than what `rustdoc`
already does.
Something that would work without a config could be way more
interesting for us to integrate into Sphinx.
Thanks!
Cheers,
Miguel
Powered by blists - more mailing lists