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
Holger Hans Peter Freyther 8073a33e2c qtbase: Cherry-pick ioctl change from Qt 5.4
The log is spammed with:

May 03 06:24:58 kernel[221]: Loading kernel module for a netw....
May 03 06:24:59 kernel: Loading kernel module for a network ...d.

this is because of an ioctl for an invalid device which leads
to the kernel trying to load a module. This occurs many times
a minute.

I have cherry-picked 1910454fe00cce8b815b1abc0a18a04d3d387ccf which
merged without conflicts. It has not been compile tested.

Related: SYS#1610
2015-05-13 12:11:56 +02:00
classes populate_sdk_qt5.bbclass: Add support for qtcreator-debug 2014-02-28 10:47:04 -03:00
conf licenses: Fix WARNING: qt3d: No generic license file exists for: PREVIEW.COMMERCIAL in any provider 2014-03-15 14:47:28 +01:00
licenses licenses: rename NOKIA-TPLA-2.4 to DIGIA-TPLA-2.4 2014-03-15 18:52:45 +01:00
recipes-devtools/cmake cmake: Be able to use this layer with Dora 2014-03-21 15:50:28 +01:00
recipes-qt qtbase: Cherry-pick ioctl change from Qt 5.4 2015-05-13 12:11:56 +02: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>