Fix the order of inherited classes, so the nanobuild python module
actually gets built.
Also, put the cmake files into the correct location, i.e.
${libdir}/cmake/nanobind
instead of
${base_libdir}/cmake/python3-nanobind
onnx 1.20.0rc1 uses nanobind and during its build it detects the
presence of the python module, and wants to use the nanobind cmake
module, both of which fail.
Signed-off-by: Zoltán Böszörményi <[email protected]>
---
.../recipes-devtools/python/python3-nanobind_2.9.2.bb | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/meta-python/recipes-devtools/python/python3-nanobind_2.9.2.bb
b/meta-python/recipes-devtools/python/python3-nanobind_2.9.2.bb
index 85105fd196..cfbe9cea66 100644
--- a/meta-python/recipes-devtools/python/python3-nanobind_2.9.2.bb
+++ b/meta-python/recipes-devtools/python/python3-nanobind_2.9.2.bb
@@ -6,19 +6,20 @@ LIC_FILES_CHKSUM =
"file://LICENSE;md5=7646f9ee25e49eaf53f89a10665c568c"
SRC_URI[sha256sum] =
"e7608472de99d375759814cab3e2c94aba3f9ec80e62cfef8ced495ca5c27d6e"
-inherit pypi python_setuptools_build_meta cmake lib_package
+inherit pypi cmake python_setuptools_build_meta
EXTRA_OECMAKE += "-DNB_TEST=OFF"
DEPENDS += "\
+ python3-cmake-native \
python3-scikit-build-native \
python3-scikit-build-core-native \
ninja-native \
"
do_install:append() {
- install -d ${D}${base_libdir}/cmake/${PN}
- install -m 0644 ${S}/cmake/* ${D}${base_libdir}/cmake/${PN}/
+ install -d ${D}${libdir}/cmake/${PYPI_PACKAGE}
+ install -m 0644 ${S}/cmake/* ${D}${libdir}/cmake/${PYPI_PACKAGE}/
}
FILES:${PN} += "${prefix_native}/* ${prefix_native}/${PN}/*
${base_libdir}/cmake/*"
--
2.51.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#121529):
https://lists.openembedded.org/g/openembedded-devel/message/121529
Mute This Topic: https://lists.openembedded.org/mt/116253743/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
