OpenEmbedded "poky" with some sysmocom specific modifications. Mostly used only up to sysmocom release 201310, but the "pyro" branch is still used for 201705
Go to file
Otavio Salvador 91ac66d5e4 README: Reword the section about github forking
This splits the lines in 80 cols and rework the text a little bit to
easy reading.

Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
2014-02-07 11:39:50 -02:00
classes qttools-native: Add module to build lrelease+lupdate+lconvert 2013-09-13 14:32:02 +02:00
conf qt5: upgrade to 5.2.0 2014-01-12 15:01:37 +01:00
recipes-devtools/cmake cmake-native: disable test for Qt5Core 2014-01-27 13:30:49 +01:00
recipes-qt qtwebkit: drop obsolete patch 0001-jsc-Add-licuuc-licui18n-LIBS.patch 2014-01-29 21:55:25 +01:00
COPYING.MIT Add COPYING.MIT to be clear about license of this layer 2013-05-10 14:42:07 +02:00
README README: Reword the section about github forking 2014-02-07 11:39:50 -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>