packages can use find_package(PythonInterp REQUIRED) find_package(PythonLibs REQUIRED)
while we control PYTHON pointing to native py3 the libs and include directories will then point to build host version, which can result in unexpected combination and if we are lucky we get errors if its quite different e.g. py2 libs/includes and py3 executable This variable can be then used to export PYTHON_LIBRARY and PYTHON_INCLUDE_DIR so that above find_packages can work correctly Signed-off-by: Khem Raj <[email protected]> --- meta/conf/distro/include/tcmode-default.inc | 3 +++ meta/recipes-devtools/python/python3_3.7.4.bb | 1 - 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/meta/conf/distro/include/tcmode-default.inc b/meta/conf/distro/include/tcmode-default.inc index 5c28386c4f..bcc5a14d4a 100644 --- a/meta/conf/distro/include/tcmode-default.inc +++ b/meta/conf/distro/include/tcmode-default.inc @@ -30,6 +30,9 @@ GOVERSION ?= "1.12%" # llvm version being used, so always bump it with llvm recipe version bump LLVMVERSION ?= "8.0.1" +# This should be bumped when python3 recipe's MIN_VER is bumped e.g. 3.7 -> 3.8 +PYTHON_BINABI = "3.7m" + PREFERRED_VERSION_gcc ?= "${GCCVERSION}" PREFERRED_VERSION_gcc-cross-${TARGET_ARCH} ?= "${GCCVERSION}" PREFERRED_VERSION_gcc-cross-initial-${TARGET_ARCH} ?= "${GCCVERSION}" diff --git a/meta/recipes-devtools/python/python3_3.7.4.bb b/meta/recipes-devtools/python/python3_3.7.4.bb index 80c9b2919e..b2014e2bcf 100644 --- a/meta/recipes-devtools/python/python3_3.7.4.bb +++ b/meta/recipes-devtools/python/python3_3.7.4.bb @@ -47,7 +47,6 @@ UPSTREAM_CHECK_REGEX = "[Pp]ython-(?P<pver>\d+(\.\d+)+).tar" CVE_PRODUCT = "python" PYTHON_MAJMIN = "3.7" -PYTHON_BINABI = "${PYTHON_MAJMIN}m" S = "${WORKDIR}/Python-${PV}" -- 2.23.0 -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
