f30c4ba364
Am working on recipes for kdevelop and musescore. These require native help tools - at least because cmake configs reference them. * Have tried other - patch-less - ways to achieve this without success * Tested multiple combinations with and without clang in PACKAGECONFIG * gcc/clang toolchain with expected result: For clang set, native tools are build for clang misssing tools are not build. * Target build remained unchanged because it was buildung help tools with clang in PACKAGECONFIG * Tried also to add the patch to nativesdk but help tools were not build. Stopped further investigation - that is not a use case for me - sorry Note for clang-toolchain users (confused me a bit - now it's obvious): For qttools-native clang has to be set explicitly in PACKAGECONFIG, otherwise native help tools are not build (same as behaviour as before). Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
Qt5 OpenEmbedded/Yocto Project layer
This layer depends on:
URI: https://github.com/openembedded/openembedded-core (branch: master)
When building stuff like qtdeclarative, qtquick, qtwebkit, make
sure that you have required PACKAGECONFIG options enabled in qtbase
build, see qtbase recipe for detail.
Some recipes like qtwebengine would need 32bit multilib compiler on build
host, especially when target to be built is 32bit, e.g. arm since it builds
v8 engine which requires $CC -m32 to work, so ensure that host compiler
can generate 32bit code, on archlinux distributions this would be
pacman -S lib32-gcc-libs lib32-glibc
Contributing
Please submit any patches against the meta-qt5 layer by using the
GitHub pull-request feature. Fork the repo, make a branch, do the
work, rebase from upstream, create the pull request, yada-yada.
Maintainers
- Martin 'JaMa' Jansa martin.jansa@gmail.com
- Otavio Salvador otavio@ossystems.com.br
Yocto Project Compatible
meta-qt5 has Yocto Project Compatible status since 2013. Check it at: https://www.yoctoproject.org/product/meta-qt5