Jeroen Hofstee aeeaa939c7 qtbase: mkspecs: add default toolchain options
While most mkspecs use hardcoded compiler names / options, qmake in
meta-qt5 is setup to get them from the environment. While this works
fine with openembedded, it does break normal workflows outside of it.
For example to get the SDK working with Qt Creator either the environmental
script most be sourced first, making it impossible to switch between
different Qt versions or the OE_QMAKE must be set for every project,
otherwise you get cryptic errors like 'make: c: Command not found',
since the compiler name is not set and hence an attempt is made to
execute only the arguments.

Likewise on the target itself, qmake doesn't work without first setting
the OE_QMAKE variables.

This patch adds default toolchains options, so it is no longer required
to set them, but keeps the flexibility to alter them from the environment.

Signed-off-by: Jeroen Hofstee <jhofstee@victronenergy.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2017-12-20 08:22:55 +00: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%