summaryrefslogtreecommitdiffstats
path: root/recipes-qt/meta
Commit message (Collapse)AuthorAgeFilesLines
* AM: Add appman tools to automotive nativesdkGordan Markuš2017-02-101-1/+1
| | | | | | | Task-number: QTAUTO-274 Change-Id: I467e93dc25a314cda0a4c35fe990c2b1274bc251 Reviewed-by: Gordan Markus <gordan.markus@pelagicore.com> Reviewed-by: Samuli Piippo <samuli.piippo@qt.io>
* Add support for creating QBSP packageSamuli Piippo2016-11-212-0/+95
| | | | | | | | | | | | | | | | | | | | | | | | QBSP is a Qt specific Board Support Package that can be installed with the Qt SDK or MaintenanceTool and contains a system image and a toolchain. The toolchain is automatically registered to the QtCreator. The recipes used for creating the system image and the toolchain can be configured with QBSP_IMAGE_TASK and QBSP_SDK_TASK. The files wanted for the system image can be further configured with QBSP_IMAGE_CONTENT, with a list of files located in DEPLOY_DIR_IMAGE folder. By default, .img and .conf files are used from the selected image recipe. QBSP_INSTALLER_COMPONENT defines the location in the Qt installer tree where the QBSP is shown and QBSP_VERSION defines the version for the components. The QBSP is installed to path defined by QBSP_INSTALL_PATH. The regular SDK creation can now reuse the same image package .7z, so update upload script to use it instead of creating new package. Task-number: QTBUG-57018 Change-Id: Id1e7cc4ab3998a7d450f23ed603b8e676b314d63 Reviewed-by: Iikka Eklund <iikka.eklund@qt.io> Reviewed-by: Teemu Holappa <teemu.holappa@qt.io>
* sdk: do not explicitly define Qt dependency packagesSamuli Piippo2016-11-031-0/+32
| | | | | | | | | | | | | Until now, the toolchain used by CI has been created without Qt, but with all (best guess) Qt dependencies. Now toolchain is created with Qt and we get all Qt dependencies correctly into the toolchain. As a consequence, CI will now need to build Qt, which has not been covered in CI before. The difference between embedded-sdk and embedded-qt5-sdk is that the former does not include files needed for debugging. Change-Id: Ie2be156c07e51119c0d4782494d6bcde6f34ed60 Reviewed-by: Risto Avila <risto.avila@qt.io>
* Add Qt for Device Creation licenseSamuli Piippo2016-06-072-4/+4
| | | | | | | | Replace CLOSED and QtEnteprise licenses with the Qt for Device Creation license on all recipes. Change-Id: I02fddc0ee4375bddf18a6c1f7ab093462a5f5153 Reviewed-by: Kalle Viironen <kalle.viironen@theqtcompany.com>
* Update license headersSamuli Piippo2016-05-182-14/+30
| | | | | | | License changed to GPLv3 + Commercial Change-Id: I267c97216e717ed29071df064337e1bcf83de973 Reviewed-by: Kalle Viironen <kalle.viironen@theqtcompany.com>
* Update license headersSamuli Piippo2016-02-092-28/+26
| | | | | Change-Id: Iabcf736e6f4ae2149b57c84ebdc8b5b1be82023d Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
* Move qt5 sdk creation bits to new bbclassSamuli Piippo2016-02-015-78/+8
| | | | | | Change-Id: I6d00c21fa04e77db60c7c48ad6ba10eacad00b42 Reviewed-by: David Schulz <david.schulz@theqtcompany.com> Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
* qt5: use qmake built-in variables instead of patchingSamuli Piippo2016-01-141-11/+4
| | | | | | | | | Change the host paths during SDK build to qmake build-in variables, so that we don't need to patch anything during SDK installation. Change-Id: I9273d85f10da5aa1897f35f1866abb4d80a625fd Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com> Reviewed-by: David Schulz <david.schulz@theqtcompany.com>
* Fix up toolchain packaging for Windows hostsDavid Schulz2016-01-141-1/+1
| | | | | Change-Id: Idb7af9308e702b4ef5f26e6423cfa270f8c036e5 Reviewed-by: Samuli Piippo <samuli.piippo@theqtcompany.com>
* Create separate automotive SDKSamuli Piippo2015-12-085-47/+99
| | | | | | | | | Automotive toolchain will contain packages that are not available in the B2Qt embedded toolchain. Add empty packagegroup recipe that can be used to add new content to automotive sdk. Change-Id: I43c520db9b4f292226b2b5402bb460232a20ede3 Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
* sdk: relocate paths in qt5 sdk .pri filesSamuli Piippo2015-11-261-1/+5
| | | | | | | | mkspecs/qconfig.pri has envs for PKG_CONFIG which need to be relocated when SDK is installed. Change-Id: Ibeccb5c6b26f5f40ad5e515023eb259903c20fb8 Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
* Merge remote-tracking branch 'origin/dizzy' into devSamuli Piippo2015-11-031-2/+0
|\ | | | | | | | | | | | | | | | | | | | | | | * origin/dizzy: VKB: use correct SHA1 for v1.3.1 qt5: add qt addons dev packages to the toolchain qtquickcompiler: add dev packages to toolchain Go back to branch 5.5 in b2qt-demos build qt5: use jethro branch for meta-qt5 qt5: oe-device-extra.pri is now supported in upstream Change-Id: Ib369f45fe6644d4e44e24e7850c3dfe7431d31f4
| * qt5: oe-device-extra.pri is now supported in upstreamSamuli Piippo2015-10-261-2/+0
| | | | | | | | | | | | | | | | Use of oe-device-extra.pri was merged upstream, so remove unneeded parts for our layer. Change-Id: I40ffeadc80780d49ba777e7cfd24fc2048d3a418 Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
* | set proper S valueSamuli Piippo2015-10-141-0/+1
|/ | | | | | | Remove warning: ('S') doesn't exist, please set 'S' to a proper value Change-Id: I1e771d31b4fa6ae50a0ff63b87241a8fe81e90c3 Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
* 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-283-1/+54
| | | | | | | | | | | | | | | | | | 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>