Andreas Müller f636eb7444 qt5: set SRCREVs,PVs to 5.6.0
* qtquick1: LICENSE.LGPLv3: I checked git repository.
  To be honest: I have no idea what caused checksum change.
  JaMa: it was modified in this change:
  OE @ ~/projects/qt-project/qtquick1 $ git log --oneline 87f2415adf34da08e6cd58f5da6f6a7d0d9cf141..dcc5e5c01c28b227f0e5e5e4976a9d26e8a45295 -- LICENSE.LGPLv3
  cd50897 Add the GPLv3 license text
  diff --git a/LICENSE.LGPLv3 b/LICENSE.LGPLv3
  index 8fbb743..4d67bac 100644
  --- a/LICENSE.LGPLv3
  +++ b/LICENSE.LGPLv3
  @@ -5,6 +5,8 @@

    You may use, distribute and copy the Qt GUI Toolkit under the terms of
    GNU Lesser General Public License version 3, which is displayed below.
  + This license makes reference to the version 3 of the GNU General
  + Public License, which you can find in the LICENSE.GPLv3 file.

* in some cases this is actually older SRCREV than what was
  used before (because normally the recipes use latest revision
  in stable - e.g. 5.6 branches, not the actuall tags). I'll
  upgrade to latest 5.6 revisions in follow-up commit (together
  with refreshing the .patch files and github.com/meta-qt5/qt*
  repositories to apply cleanly)

Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2016-04-20 10:58:33 +02:00
2016-04-20 10:58:33 +02:00
2015-12-18 13:11:42 +01:00

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>
Description
No description provided
Readme 4.6 MiB
Languages
BitBake 95.2%
Python 4%
Roff 0.7%