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 <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
DEPENDS += "python3-setuptools-native python3-wheel-native"
+# Where to execute the build process from
+PEP517_SOURCE_PATH ?= "${S}"
+
setuptools_build_meta_do_configure () {
:
}
# TODO: ideally this uses pypa/build
setuptools_build_meta_do_compile () {
+ cd ${PEP517_SOURCE_PATH}
nativepython3 -c "from setuptools import build_meta; build_meta.build_wheel('${PIP_INSTALL_DIST_PATH}')"
}
do_compile[cleandirs] += "${PIP_INSTALL_DIST_PATH}"