summaryrefslogtreecommitdiffstats
path: root/recipes-qt/images
Commit message (Collapse)AuthorAgeFilesLines
* Add support for creating QBSP packageSamuli Piippo2016-11-212-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | 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>
* images: do not explicitly define Qt dependency packagesSamuli Piippo2016-11-033-8/+74
| | | | | | | | | | | | | | | Remove all Qt dependency packages from machine include files and base packagegroups, instead let packagemanager pull in all the needed dependent packages. Do not create tar image or bootfs, since they are not used anymore. The old base image is now renamed for CI usage and contains all the Qt dependent packages but without any Qt modules. This is achieved by first installing all the Qt modules (which pulls in all the dependencies) and then removing only Qt modules. Change-Id: I36d996d4531af42e955f19a487c22d0b90c5ada9 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>
* Use consistent mtime timestampsGatis Paeglis2016-03-162-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds consistent_timestamps.bbclass which is a hackish way of resembling reproducible build - byte-for-byte identical binary packages from a given source. Naturally this is not a complete solution, but it fixes the issue described below. Real solution for this should be done by the Yocto project itself. In OSTree each new update is checked out with all files and directories having mtime=0, this breaks fontconfig cache validity check (mtime embedded in the cache should match the containing directories mtime). Yocto generates this cache file in poky/meta/lib/oe/rootfs.py::create by calling self._run_intercepts() after all packages have been installed. These timestamps are nondeterministic as they depend on current system time. By using ROOTFS_POSTINSTALL_COMMAND hook we can ensure that these embedded time stamps have a known time, which is a basic property of reproducible build system. Change-Id: Ib2f130248f2e65db391d2b2f19ab5dac30a2cfb0 Task-number: QTEE-1081 Reviewed-by: Samuli Piippo <samuli.piippo@theqtcompany.com>
* Update license headersSamuli Piippo2016-02-092-28/+26
| | | | | Change-Id: Iabcf736e6f4ae2149b57c84ebdc8b5b1be82023d Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
* Generate deploy conf for flashing wizardSamuli Piippo2015-12-022-0/+4
| | | | | | Change-Id: I23cc54e51b7d10db0fd64d6676bd86cdf029beda Reviewed-by: Rainer Keller <rainer.keller@theqtcompany.com> Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
* automotive: create new automotive specific imageSamuli Piippo2015-11-252-2/+51
| | | | | | | | | Reuse most parts from b2qt image, only difference is the demo addons which will be different for the automotive image. For now, add no demo app, so image boots to empty screen. Change-Id: I67bbe8724422c9ea86dae6e4d5f8f38d3d567ba1 Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
* gstreamer: make gstreamer version a DISTRO_FEATURESamuli Piippo2015-06-191-1/+2
| | | | | | | | | | | | | GStreamer version can now be changed using a DISTRO_FEATURE: 'gstreamer010' for GStreamer 0.10 and 'gstreamer' for GStreamer 1.0 This can also be used to remove all gstreamer packages from image and toolchain. Default version is still the old 0.10 Change-Id: I54b19962ccd0dfd2f71bb44e231bf5af43ccfab9 Reviewed-by: Eirik Aavitsland <eirik.aavitsland@theqtcompany.com>
* emulator: Qt5 support for emulatorSamuli Piippo2015-05-271-0/+3
| | | | | | | | | | | Emulator has special handling for OpenGL support: QtGlesStream provides the runtime opengl support but since it depends on qtbase, we need to use qtglesstream-dummy-client when building qt. Also since both recipes provide same files, we must disable do_populate_sysroot from qtglesstream so that libs from dummy-client remain there. Change-Id: Ifde698e7d46863dbb82c6f3ad791412775e111ea Reviewed-by: Eirik Aavitsland <eirik.aavitsland@theqtcompany.com>
* Build Qt5 and all addonsSamuli Piippo2015-05-121-0/+45
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>