diff options
author | Jeroen Hofstee <jhofstee@victronenergy.com> | 2017-11-21 10:51:23 +0100 |
---|---|---|
committer | Martin Jansa <Martin.Jansa@gmail.com> | 2017-12-20 08:22:55 +0000 |
commit | aeeaa939c7f129a4be2220c86fcebca0fcc8b100 (patch) | |
tree | 6521892a6486329428438e82a746d5fdb98cf336 /recipes-qt/qt5/qtwebengine/0001-WebEngine-qquickwebengineview_p_p.h-add-include-QCol.patch | |
parent | d27c0199dbe453b3b9af32783f6d15c022f18429 (diff) | |
download | meta-qt5-aeeaa939c7f129a4be2220c86fcebca0fcc8b100.tar.gz |
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>
Diffstat (limited to 'recipes-qt/qt5/qtwebengine/0001-WebEngine-qquickwebengineview_p_p.h-add-include-QCol.patch')
0 files changed, 0 insertions, 0 deletions