mirror of
https://github.com/thead-yocto-mirror/meta-qt5
synced 2026-09-07 06:34:39 +02:00
22c431e7a1
* Gitorious disabled the git:// protocol, breaking fetches. * Also, this service is scheduled to stop in May 2015, so move to code.qt.io. * qt5everywheredemo needs different SRCREV because this repo was recreated in code.qt.io and SRCREV 9a868f96ee63c21ceda890d8dfc9d33f093d1b6d doesn't exist on code.qt.io It was initial commit in gitorious repo: commit 9a868f96ee63c21ceda890d8dfc9d33f093d1b6d Author: Sergio Ahumada <sergio.ahumada@digia.com> Date: Wed Jul 3 12:09:40 2013 +0200 Initial commit This is exactly matching with this commit in code.qt.io: commit c17fe9e0ec0882ac4c4dc1168095f569acab5d09 Author: Kimmo Ollila <kimmo.ollila@digia.com> Date: Wed Jun 19 13:02:05 2013 +0300 Fixed radio crash on application close Signed-off-by: Frederico Cadete <frederico@cadete.eu> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
This layer depends on: URI: git://github.com/openembedded/oe-core.git branch: master revision: HEAD URI: git://github.com/openembedded/meta-oe.git layers: meta-ruby 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' 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 gitorious, 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/ Main layer maintainers: Martin 'JaMa' Jansa <martin.jansa@gmail.com> Otavio Salvador <otavio@ossystems.com.br>