5e18973196
* there are couple things people need to provide to even parse meta-qt5 dunfell branch with older than dunfell release of oe-core so I don't want to mark it as compatible, people who understand how to provide these missing bits will know how to override LAYERSERIES_COMPAT_qt5-layer from their own layer (which needs to be parsed before meta-qt5 layer - I suggest to use something like separate meta-qt5-compat layer) the required work arounds (these are the examples to build dunfell branch from zeus: 1) mime-xdg.bbclass, e.g.:e57440cb972) gstreamer1.0-plugins-good PACKAGECONFIG:75fd06799b3) meta-python2:57f3f6f20b4) features_check.bbclass:fb3e94ba4aSigned-off-by: Martin Jansa <Martin.Jansa@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