summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKhem Raj <raj.khem@gmail.com>2022-03-04 00:00:02 -0800
committerKhem Raj <raj.khem@gmail.com>2022-03-09 07:37:03 -0800
commitbc8241129c8b9b32e6e81dbf444c80c86a74e53b (patch)
tree8776bb176dbcd058db1e1284eeeeec6a45dc0412
parente88e596cc678dcfb6f6a355c2f240b2b6d7164fb (diff)
downloadmeta-openembedded-bc8241129c8b9b32e6e81dbf444c80c86a74e53b.tar.gz
python3-crc32c: set target platform via setup.cfg
Do not poke at build system for finding platform platform is target specific and when cross compiling it should be detected differently, in this case lets pass it via environment so that it can be set in recipe Looks like we're not the first to need to specify the target platform [1] when building this package. According to upstream, we can just update setup.cfg instead of patching setup.py. [1] https://github.com/ICRAR/crc32c/pull/10 Signed-off-by: Justin Bronder <jsbronder@cold-front.org> Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Trevor Gamblin <trevor.gamblin@windriver.com>
-rw-r--r--meta-python/recipes-devtools/python/python3-crc32c_2.2.post0.bb6
1 files changed, 6 insertions, 0 deletions
diff --git a/meta-python/recipes-devtools/python/python3-crc32c_2.2.post0.bb b/meta-python/recipes-devtools/python/python3-crc32c_2.2.post0.bb
index f58760761a..4f6a3aba99 100644
--- a/meta-python/recipes-devtools/python/python3-crc32c_2.2.post0.bb
+++ b/meta-python/recipes-devtools/python/python3-crc32c_2.2.post0.bb
@@ -13,4 +13,10 @@ SRC_URI[sha256sum] = "3d058e7a5e37e4985d1a7ad4cb702bca56b490daa658d4851377d13ead
13 13
14inherit pypi setuptools3 14inherit pypi setuptools3
15 15
16do_compile:prepend() {
17 if ! grep 'platform =' setup.cfg; then
18 printf "[build_ext]\nplatform = ${TARGET_ARCH}" >> setup.cfg
19 fi
20}
21
16RDEPENDS:${PN} += "python3-core" 22RDEPENDS:${PN} += "python3-core"