generic-poky/meta-qt5
Daniel Willmann 742a86d746 Merge commit 'eca7186eaa09df1870cd9d96017ddc385cffb68f' into dora 2017-06-02 15:01:47 +02:00
..
classes Add 'meta-qt5/' from commit '5cd79448e4b5a730922c0c63161a5b2ee5f0b344' 2014-07-30 17:26:11 +02:00
conf Merge commit 'eca7186eaa09df1870cd9d96017ddc385cffb68f' into dora 2017-06-02 15:01:47 +02:00
licenses Add 'meta-qt5/' from commit '5cd79448e4b5a730922c0c63161a5b2ee5f0b344' 2014-07-30 17:26:11 +02:00
recipes-qt Merge commit '8073a33e2cb0bbf3aa7ac14808e4cedebb0c20f4' into dora 2015-05-13 12:16:35 +02:00
yocto-dora Merge commit 'eca7186eaa09df1870cd9d96017ddc385cffb68f' into dora 2017-06-02 15:01:47 +02:00
COPYING.MIT Add 'meta-qt5/' from commit '5cd79448e4b5a730922c0c63161a5b2ee5f0b344' 2014-07-30 17:26:11 +02:00
README Add 'meta-qt5/' from commit '5cd79448e4b5a730922c0c63161a5b2ee5f0b344' 2014-07-30 17:26:11 +02:00

README

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>