summaryrefslogtreecommitdiffstats
path: root/recipes-qt/meta/meta-toolchain-b2qt-embedded-qt5-sdk.bb
Commit message (Collapse)AuthorAgeFilesLines
* qt5: use the new base bbclass to get qt.conf generatedSamuli Piippo2015-09-161-1/+1
| | | | | | | | populate_sdk_qt5 was split into two bbclasses and the qt.conf generation we need is in the new base class. Change-Id: I7fe2f3bdc0bf88e795add996f58b592ea12aa8a3 Reviewed-by: aavit <eirik.aavitsland@theqtcompany.com>
* qt5: patch qdevice.conf from correct locationSamuli Piippo2015-08-271-1/+2
| | | | | | | Mkspecs are now used directly from target sysroot, instead of the symlink. Change-Id: Ibd390b5377e137096e3c92a9b9af1f6ddf36bdff Reviewed-by: aavit <eirik.aavitsland@theqtcompany.com>
* Toolchain: add static device mkspec, suitable for Qt CreatorEirik Aavitsland2015-05-281-1/+38
| | | | | | | | | | | | | | | | | | The linux-oe-g++ mkspec used by meta-qt5 depends on the user sourcing the toolchain environment-setup script, which modifies the PATH and sets a long range of environment variables. That is not a "best practice" way of use Qt, and does not allow smooth integration of the toolchain into Qt Creator. Here, we instead create a static mkspec for the toolchain: devices/linux-oe-generic-g++. The toolchain recipe will will the qdevice.pri file with the required compiler flags etc. for the target. Additionally, we introduce an extra .pri file for device-specific settings, so they can be shared between the two mkspecs. Change-Id: Ie5a019524ba6cdddffb71b0c7c28861ddba17fbd Reviewed-by: Samuli Piippo <samuli.piippo@theqtcompany.com>
* Build Qt5 and all addonsSamuli Piippo2015-05-121-0/+31
Use meta-qt5 layer to build Qt5, commercial addons and b2qt addons. Create new image and toolchain recipes with Qt5 content, so that the existing image and toolchain remain as-is without Qt5. Currently support only for imx6 targets. Change-Id: I398750dd1a62c6ff8ea216cfe364da273d8e9a77 Reviewed-by: Andy Nichols <andy.nichols@theqtcompany.com>