mirror of
https://github.com/thead-yocto-mirror/meta-qt5
synced 2026-09-03 20:54:37 +02:00
7e72e9166f
The branch called 5.10.1 no longer exists at code.qt.io repos. The corresponding v5.10.1 qt tags still exist (at least on those repos that originally got tagged during the release), and they are available on the 5.11 branch. Thus we can keep Qt source at 5.10.1 commits, but use 5.11 branch to check out those specific commits. This could be a bit confusing, making it look like 5.11 is the current default version for recipes, so for now there is a comment in qt5-git.inc trying to clarify the situation. A couple of repos that already were lacking 5.10.1 branch no longer need to override QT_MODULE_BRANCH, since their chosen commits are also available on 5.11 branch. Signed-off-by: S. Lockwood-Childs <sjl@vctlabs.com>
This layer depends on: URI: git://github.com/openembedded/oe-core.git branch: master revision: HEAD When building stuff like qtdeclarative, qtquick, qtwebkit, make sure that you have required PACKAGECONFIG options enabled in qtbase build, see qtbase.inc for detail. Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-qt5]' in the subject' When sending single patches, please using something like: git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix='meta-qt5][PATCH' Change option '-1' to '-n' for n number of patches in series You are encouraged to fork the mirror on github[1] to share your patches. This is preferred for patch sets consisting of more than one patch. Other services like gitlab, repo.or.cz or self hosted setups are of course accepted as well, 'git fetch <remote>' works the same on all of them. We recommend github because it is free, easy to use, has been proven to be reliable and has a really good web GUI. 1. https://github.com/meta-qt5/meta-qt5/ meta-qt5 has Yocto Project Compatible status since 2013: https://www.yoctoproject.org/product/meta-qt5 Main layer maintainers: Martin 'JaMa' Jansa <martin.jansa@gmail.com> Otavio Salvador <otavio@ossystems.com.br>