e551f7b301
* there are few newer commits since the SRCREV used in this recipe it might be useful if someone is still using this (I don't, so I'll just fix the build failure with gcc-13 and cleanup the .patch files): $ git log --oneline 10cd6a106..origin/5.212 ac8ebc6c3 (origin/5.212) Enable QML tests 5a99e5d4c Import QtWebKit commit 5d89eef9bc689abb59ef799b445c35b1e322b3f1 685ed792f Import QtWebKit commit 143b469188bde226d5e70cff5f01699b8a29d865 8967b4f87 Import QtWebKit commit 6faf5d547055321f0d518fe83766499cac5d8664 08eaf858c Import QtWebKit commit cf37bc44f798d3c5a26d17086ada92688b9bfe6d 412e257d0 Workaround for Windows Store python3.exe e16357a52 Import QtWebKit commit f966d667c14ddcfe983f4a31fc80a1edbb6ada10 Signed-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