Re: [oe] [meta-python][PATCH 1/4] python_setuptools_build_meta_mesonpy.bbclass: New class

From: Ross Burton <Ross.Burton@arm.com>
To: "zboszor@gmail.com" <zboszor@gmail.com>
Cc: "openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] [meta-python][PATCH 1/4] python_setuptools_build_meta_mesonpy.bbclass: New class
Date: Wed, 15 Mar 2023 12:46:04 +0000	[thread overview]
Message-ID: <25DB9C8C-6830-4DBB-9B27-4FB04C393F38@arm.com> (raw)
In-Reply-To: <20230315080429.2722555-1-zboszor@gmail.com>

On 15 Mar 2023, at 08:04, Zoltan Boszormenyi via lists.openembedded.org <zboszor=gmail.com@lists.openembedded.org> wrote:
> 
> Some python modules (e.g. SciPy, scikit-image) use meson-python
> (a.k.a. mesonpy) in pyproject.toml:
> 
>    [build-system]
>    build-backend = 'mesonpy'
> 
> This class, together with python3-meson-python and its dependencies
> will allow building such modules.

So the pep517 build thing provides dependencies (which we ignore), build isolation (which we disable), and automatic use of the right tooling (which we have to specify manually).

So what does the meson-python integration bring?  Can we just run meson directly?

> +DEPENDS += "python3-setuptools-native python3-wheel-native ${@'' if d.getVar('PN') == 'python3-meson-python-native' else 'python3-meson-python-native’}"

FWIW, all the other pep517 classes have a “neat” depends without logic and expect the recipe (python3-meson-python-native in this case) to remove itself from the DEPENDS.

Ross