The PEP517[1] pyproject.toml doesn't have to be located at the top-level of the source tree (for example, in recipes with multiple components), so add a variable PEP517_SOURCE_PATH to set where the file is.
In the future there should be a pep517.bbclass to centralise the common logic, but for now this can be defined in each of the relevant classes. [1] https://www.python.org/dev/peps/pep-0517/ Signed-off-by: Ross Burton <[email protected]> --- meta/classes/flit_core.bbclass | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/meta/classes/flit_core.bbclass b/meta/classes/flit_core.bbclass index 3481bb5089..7b578967a9 100644 --- a/meta/classes/flit_core.bbclass +++ b/meta/classes/flit_core.bbclass @@ -6,8 +6,12 @@ flit_core_do_configure () { : } +# Where to execute the build process from +PEP517_SOURCE_PATH ?= "${S}" + # TODO: ideally this uses pypa/build flit_core_do_compile () { + cd ${PEP517_SOURCE_PATH} nativepython3 -mflit_core.wheel --outdir ${PIP_INSTALL_DIST_PATH} } do_compile[cleandirs] += "${PIP_INSTALL_DIST_PATH}" -- 2.25.1
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#162923): https://lists.openembedded.org/g/openembedded-core/message/162923 Mute This Topic: https://lists.openembedded.org/mt/89637947/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
