Mike Crowe 743b3b93e1 qtbase-native: Force use of built-in pcre
If we specify neither -system-pcre nor -qt-pcre then qtbase will first see
if it can find the pcre library in the system and fall back to compiling
its own if that's not possible.

Unfortunately, this means that if qtbase-native happens to be built on a
machine with system pcre available then the resulting binaries such as
bin/qt5/uic in sstate files won't work correctly on machines that don't
have pcre available. Even ignoring that, it doesn't help for packages to
build differently depending on how the build system is configured.

We could depend on pcre-native and pass -system-pcre, but this doesn't work
by default because qtbase actually requires pcre16 which is an optional
(via PACKAGECONFIG) feature of pcre so the default there would need to be
changed too.

So, let's make qtbase-native match the default of qtbase by passing
-qt-pcre in order to ensure that qtbase-native is always built with its
own pcre implementation.

Signed-off-by: Mike Crowe <mac@mcrowe.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2017-09-11 13:20:22 +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%