[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fd1372a9fb57a1372db5b3c0992a929f90183f83@intel.com>
Date: Tue, 29 Jul 2025 13:45:26 +0300
From: Jani Nikula <jani.nikula@...el.com>
To: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
Cc: Jonathan Corbet <corbet@....net>, Laurent Pinchart
<laurent.pinchart@...asonboard.com>, Linux Doc Mailing List
<linux-doc@...r.kernel.org>, linux-kernel@...r.kernel.org,
workflows@...r.kernel.org, Akira Yokosawa <akiyks@...il.com>
Subject: Re: [PATCH v2 3/2] docs: changes: better document Python needs
On Mon, 28 Jul 2025, Mauro Carvalho Chehab <mchehab+huawei@...nel.org> wrote:
> Considering the above, for me it seems that the bus already departed:
> there are several cases where Python is required during build time.
FWIW, if it was up to me, I'd make Python 3+ a non-optional build
dependency. I'd also forget about any Python 2 backward compat stuff.
I would find it very useful for code/header generation during build
time, instead of having to resort to C hostprogs. Similar to what MSM is
doing.
That said, I know there's going to be people vehemently opposed.
> So, adding a "depends on TOOL_PYTHON" doesn't seem to be trivial.
Agreed. Forget about that idea.
BR,
Jani.
--
Jani Nikula, Intel
Powered by blists - more mailing lists