The Qt SDK toolchain pulls in python via packagegroup-cross-canadian-${MACHINE}
and ships it. But the python is missing many modules and is rather incomplete.The environment-setup-* script configures the PATH variable to point into it's own sysroot first, it means the python from the SDK is used as well when the environment is configured. It actually does make sense to use the python from the SDK, since the SDK should provide the tools needed to build additional software. The problem is, the python in the SDK image is stripped to a bare minimum of modules, which prevents some software from being built with the SDK as is. Add the same python modules as the buildtools-tarball.bb adds to make the python shipped with the SDK complete via nativesdk-packagegroup-python. Signed-off-by: Marek Vasut <[email protected]> --- meta/recipes-qt/meta/meta-toolchain-qt.inc | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/meta/recipes-qt/meta/meta-toolchain-qt.inc b/meta/recipes-qt/meta/meta-toolchain-qt.inc index 6b162bd..b8b9c78 100644 --- a/meta/recipes-qt/meta/meta-toolchain-qt.inc +++ b/meta/recipes-qt/meta/meta-toolchain-qt.inc @@ -1,4 +1,8 @@ -TOOLCHAIN_HOST_TASK = "nativesdk-packagegroup-${QTNAME}-toolchain-host packagegroup-cross-canadian-${MACHINE}" +TOOLCHAIN_HOST_TASK = " \ + nativesdk-packagegroup-${QTNAME}-toolchain-host \ + packagegroup-cross-canadian-${MACHINE} \ + nativesdk-packagegroup-python \ + " TOOLCHAIN_TARGET_TASK = "packagegroup-${QTNAME}-toolchain-target" TOOLCHAIN_OUTPUTNAME = "${SDK_NAME}-toolchain-${QTNAME}-${DISTRO_VERSION}" -- 2.0.0 -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
