unparsed line #yocto
|
Kevin Kettinger
Hello,
after including the meta-qt5 and meta-boot2qt layer from https://code.qt.io/cgit/yocto, and adding them to my bblayers.conf, bitbake breaks directly while parsing the recipes: --------------------------------------------- ERROR: ParseError at /home/yocto/projects/faseroptik-dunfell/build/../layers/meta-qt5/classes/cmake_qt5.bbclass:4: unparsed line: 'DEPENDS:prepend = "${QTBASEDEPENDS} "' | ETA: --:--:-- Summary: There was 1 ERROR message shown, returning a non-zero exit code. --------------------------------------------- If i restart bitbake, the offending file changes now and then, but just for completion, here is the file: --------------------------------------------- inherit cmake inherit qmake5_paths DEPENDS:prepend = "${QTBASEDEPENDS} " QTBASEDEPENDS = "qtbase qtbase-native" QTBASEDEPENDS:class-native = "qtbase-native" QTBASEDEPENDS:class-nativesdk = "nativesdk-qtbase qtbase-native" EXTRA_OECMAKE:prepend = " \ -DOE_QMAKE_PATH_PREFIX=${OE_QMAKE_PATH_PREFIX} \ -DOE_QMAKE_PATH_HEADERS=${OE_QMAKE_PATH_HEADERS} \ -DOE_QMAKE_PATH_LIBS=${OE_QMAKE_PATH_LIBS} \ -DOE_QMAKE_PATH_ARCHDATA=${OE_QMAKE_PATH_ARCHDATA} \ -DOE_QMAKE_PATH_DATA=${OE_QMAKE_PATH_DATA} \ -DOE_QMAKE_PATH_BINS=${OE_QMAKE_PATH_BINS} \ -DOE_QMAKE_PATH_LIBEXECS=${OE_QMAKE_PATH_LIBEXECS} \ -DOE_QMAKE_PATH_PLUGINS=${OE_QMAKE_PATH_PLUGINS} \ -DOE_QMAKE_PATH_QML=${OE_QMAKE_PATH_QML} \ -DOE_QMAKE_PATH_TRANSLATIONS=${OE_QMAKE_PATH_TRANSLATIONS} \ -DOE_QMAKE_PATH_DOCS=${OE_QMAKE_PATH_DOCS} \ -DOE_QMAKE_PATH_SETTINGS=${OE_QMAKE_PATH_SETTINGS} \ -DOE_QMAKE_PATH_EXAMPLES=${OE_QMAKE_PATH_EXAMPLES} \ -DOE_QMAKE_PATH_TESTS=${OE_QMAKE_PATH_TESTS} \ -DOE_QMAKE_PATH_HOST_PREFIX=${OE_QMAKE_PATH_HOST_PREFIX} \ -DOE_QMAKE_PATH_HOST_BINS=${OE_QMAKE_PATH_HOST_BINS} \ -DOE_QMAKE_PATH_HOST_DATA=${OE_QMAKE_PATH_HOST_DATA} \ -DOE_QMAKE_PATH_HOST_LIBS=${OE_QMAKE_PATH_HOST_LIBS} \ -DOE_QMAKE_PATH_EXTERNAL_HOST_BINS=${OE_QMAKE_PATH_EXTERNAL_HOST_BINS} \ -DOE_QMAKE_PATH_QT_HEADERS=${OE_QMAKE_PATH_QT_HEADERS} \ -DOE_QMAKE_PATH_QT_ARCHDATA=${OE_QMAKE_PATH_QT_ARCHDATA} \ -DOE_QMAKE_PATH_QT_DATA=${OE_QMAKE_PATH_QT_DATA} \ -DOE_QMAKE_PATH_QT_BINS=${OE_QMAKE_PATH_QT_BINS} \ -DOE_QMAKE_PATH_QT_TRANSLATIONS=${OE_QMAKE_PATH_QT_TRANSLATIONS} \ -DOE_QMAKE_PATH_QT_DOCS=${OE_QMAKE_PATH_QT_DOCS} \ -DOE_QMAKE_PATH_QT_SETTINGS=${OE_QMAKE_PATH_QT_SETTINGS} \ -DOE_QMAKE_PATH_QT_EXAMPLES=${OE_QMAKE_PATH_QT_EXAMPLES} \ -DOE_QMAKE_PATH_QT_TESTS=${OE_QMAKE_PATH_QT_TESTS} \ " --------------------------------------------- The exact same layer with the exact same commit & files is working fine on the original boot2qt environment, but not on my environment. My bblayers.conf looks like this: --------------------------------------------- LCONF_VERSION = "7" BBPATH = "${TOPDIR}" BBFILES ?= "" BBLAYERS ?= " \ ${TOPDIR}/../layers/meta-toradex-nxp \ ${TOPDIR}/../layers/meta-freescale \ ${TOPDIR}/../layers/meta-freescale-3rdparty \ ${TOPDIR}/../layers/meta-toradex-tegra \ ${TOPDIR}/../layers/meta-toradex-bsp-common \ ${TOPDIR}/../layers/meta-openembedded/meta-oe \ ${TOPDIR}/../layers/meta-openembedded/meta-filesystems \ ${TOPDIR}/../layers/meta-openembedded/meta-gnome \ ${TOPDIR}/../layers/meta-openembedded/meta-xfce \ ${TOPDIR}/../layers/meta-openembedded/meta-initramfs \ ${TOPDIR}/../layers/meta-openembedded/meta-networking \ ${TOPDIR}/../layers/meta-openembedded/meta-multimedia \ ${TOPDIR}/../layers/meta-openembedded/meta-python \ ${TOPDIR}/../layers/meta-freescale-distro \ ${TOPDIR}/../layers/meta-toradex-demos \ ${TOPDIR}/../layers/meta-boot2qt/meta-boot2qt \ ${TOPDIR}/../layers/meta-boot2qt/meta-boot2qt-distro \ ${TOPDIR}/../layers/meta-qt5 \ ${TOPDIR}/../layers/meta-toradex-distro \ ${TOPDIR}/../layers/meta-yocto/meta-poky \ ${TOPDIR}/../layers/openembedded-core/meta \ ${TOPDIR}/../layers/meta-mender/meta-mender-core \ ${TOPDIR}/../layers/meta-mender-community/meta-mender-toradex-nxp \ ${TOPDIR}/../layers/meta-mender/meta-mender-demo \ " --------------------------------------------- On the working boot2qt environment poky 3.1.11 is used, i'm using poky 3.1.8. Is there anything i can do to track this issue down? bitbake -v doesn't report more infos. I appreciate any help here, thank you. Best regards, Kevin
|
|
|