summaryrefslogtreecommitdiffstats
path: root/recipes-qt/qt5/qtbase
Commit message (Collapse)AuthorAgeFilesLines
* Split meta-boot2qt layerSamuli Piippo2018-03-1213-261/+0
| | | | | | | | | | | Move distro specific recipes to own layer and leave only new recipes and bbclasses to meta-boot2qt layer. This makes it easier to include meta-boot2qt to your own distro layer to get access e.g., QDB and QBSP recipes that might be useful even without boot2qt distro. Task-number: QTBUG-65871 Change-Id: I6c353774dd1668b00f2d05aa262ad866b90bdef6 Reviewed-by: Timo Aarnipuro <timo.aarnipuro@qt.io>
* Merge remote-tracking branch 'origin/morty' into pyroMikko Gronoff2018-03-081-0/+3
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Not entirely a normal kind of merge. In previous merge from origin/morty into pyro several automotive suite specific commits were left out from the merge due conflicts in automotive component recipes between used platforms (morty 5.9 vs. pyro 5.10). The commits previously left out fo the merge are now included in this merge by a direct copy of origin/morty branch's recipes-qt/automotive folder into pyro. An exception is a single commit in pyro (8513b63 - neptune-ui: bump srcrev, install fonts system-wide) that's left in place and merged with origin/morty content. Also, the toolchain changes under packagegroups folder for automotive are applied, thus making the following included commits list: origin/morty: qtdeviceutilities: update to latest version meta-qt5: update meta layer meta-qt5: update meta layer neptune-ui: fetch sources from code.qt.io instead of github automotive: update neptune-ui automotive: update qtapplicationmanager automotive: update components intel: update mesa to 17.0.2 automotive: update qtapplicationmanager automotive: update qtivi & qtapplicatiomanager Update GammaRay to the 2.9.0 release automotive: update qtivi automotive: update revisions automotive: update revisions automotive: update revisions automotive: update revisions Neptune-UI: Update to use the latest Neptune-UI qtivi: Fix the broken python3 binary inside an yocto SDK Update GammaRay qtquickcontrols2: Fix background regression kontron: update SMARC-sAMX6i BSP to r03.00 origin/morty (previously left out): Fix license checksum due to incremented year number Update GammaRay revision multiscreen-demo: update revision and fix startup automotive: update revisions sdk: add qtapplicationmanger staticdev package qtivi: enable ivigenerator for toolchain appman: add dependency to nativesdk-qtdeclarative qtivi: Update to the latest version and add PACKAGECONFIG options for qtsimulator Conflicts: recipes-qt/automotive/gammaray_git.bb recipes-qt/automotive/multiscreen-demo_git.bb recipes-qt/automotive/neptune-ui_git.bb recipes-qt/automotive/qtapplicationmanager_git.bb recipes-qt/automotive/qtivi_git.bb recipes-qt/b2qt-addons/b2qt-demos.bb recipes-qt/qt5/qtdeviceutilities.bb recipes-qt/qt5/qtsystems_git.bbappend scripts/manifest.xml Change-Id: I95ee06882d88e0dc91be1b9a769e4d88e0b11591
| * kontron: update SMARC-sAMX6i BSP to r03.00Samuli Piippo2018-01-311-0/+3
| | | | | | | | | | Change-Id: Ia33509ecbbc9394b7cbdcd548abb0f6f28cf3c73 Reviewed-by: Rainer Keller <Rainer.Keller@qt.io>
* | qtbase: update patch for 5.10.0 RC2Mikko Gronoff2017-11-291-3/+3
| | | | | | | | | | Change-Id: I79d6f5c35f5960f3b42ef5942f4f767d6ae4e65e Reviewed-by: Samuli Piippo <samuli.piippo@qt.io>
* | qtbase: add workaround for internal compiler errorSamuli Piippo2017-11-251-0/+25
| | | | | | | | | | | | | | | | | | | | mingw32 build fails with gcc's internal compiler error: in ix86_compute_frame_layout, at config/i386/i386.c:11420 As a workaround, disable to offending code. Task-number: QTBUG-64707 Change-Id: I8fcc767dc3eaba131944a06d13c773842a18af76 Reviewed-by: Mikko Gronoff <mikko.gronoff@qt.io>
* | Enable eglfs emulator extensionsRainer Keller2017-11-131-1/+1
| | | | | | | | | | Change-Id: I1b895adc5ee4a32a4327afb681a799f2c8c7a48f Reviewed-by: Samuli Piippo <samuli.piippo@qt.io>
* | Add support for jetson-tx2Ilari Ängeslevä2017-11-021-0/+4
|/ | | | | | | | | | * Update env init and set-up scripts with jetson-tx2 definitions. * Include jetson-tx2 specific configuration files. * Create a copy of an existing patch to adapt to recent changes in the kernel directory structure. Change-Id: I28fbc6cdfe91562ef261543bba4d136c4291ce23 Reviewed-by: Samuli Piippo <samuli.piippo@qt.io>
* meta-qt5: update to Qt 5.9.1 RCSamuli Piippo2017-06-231-53/+30
| | | | | | | Update mingw mkspec to fix Qt build Change-Id: I1f9ff8f09a7b2cac3b26426a44139b351e39abad Reviewed-by: Mikko Gronoff <mikko.gronoff@qt.io>
* qtbase: disable eglfs device integration plugin usage in emulatorMikko Gronoff2017-04-051-0/+1
| | | | | | | | | | Boot2Qt Emulator does not launch with Qt 5.9.0 due changes in qtglesstream. Instead of updating emulator & qtglesstream, disable eglfs device integration plugin usage in the emulator VM image. Task-number: QTBUG-59771 Change-Id: I40998fc81fb75cede447d6dd6142e3bd87e387b9 Reviewed-by: Samuli Piippo <samuli.piippo@qt.io>
* Support for NVIDIA Jetson TX1Samuli Piippo2017-02-151-0/+4
| | | | | Change-Id: Ic84d78d201c48aff296715fa6ce0a7ea5e5921c3 Reviewed-by: Mikko Gronoff <mikko.gronoff@qt.io>
* NUC: use the common intel-corei7-64 BSPSamuli Piippo2016-04-081-0/+0
| | | | | | | | meta-intel no longer has specific BSPs for each machine, but they share a common BSP based on the architecture. Change-Id: Ibbb7b8b2153103367168ea37d904ce23bc245108 Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
* nvidia-t18x supportLouai Al-Khanji2016-03-221-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Steps to use this: Set up vibrante installation, mine looks like this: $ ls -l ~/VibranteSDK total 234880 drwxrwxr-x 1 louai louai 298 Mar 20 2014 eclipse -r-xr-xr-x 1 louai louai 171826846 Jan 4 09:59 NVIDIA_Tegra_Graphics_Debugger_2.1_linux-v4l_l4t-egl.run -r--r--r-- 1 louai louai 68688729 Jan 4 09:59 NVIDIA_Tegra_System_Profiler_2.5-linux-x64.tar.gz drwxr-xr-x 1 louai louai 262 Jan 5 14:50 toolchains drwxrwxr-x 1 louai louai 34 Jan 5 13:55 vibrante-oss-src drwxr-xr-x 1 louai louai 12 Jan 4 09:47 vibrante-t186ref-cuda drwxrwxr-x 1 louai louai 264 Feb 10 10:50 vibrante-t186ref-foundation drwxr-xr-x 1 louai louai 164 Jan 5 14:49 vibrante-t186ref-foundation_src drwxrwxr-x 1 louai louai 228 Jan 5 13:56 vibrante-t186ref-linux drwxr-xr-x 1 louai louai 314 Feb 10 10:58 vibrante-t186ref-linux_sr Set up Yocto build dir: $ mkdir ~/work $ cd ~/work $ ~/tqtc-b2qt/yocto-meta/b2qt-init-build-env init --device tegra-t18x Add NVIDIA's Yocto things: $ mkdir ~/work/sources/nvidia-layer $ cd ~/work/sources/nvidia-layer $ tar xf ~/VibranteSDK/vibrante-t186ref-linux_src/yocto/nvidia-layer.tgz $ cd - Set up build environment: $ export MACHINE=tegra-t18x $ . setup-environment.sh Set the following environment variables: $ export KERN_DIR=~/VibranteSDK/vibrante-t186ref-linux_src/kernel $ export PLATFORM_TOPDIR=~/VibranteSDK/vibrante-t186ref-linux $ export TOOLCHAIN_PATH=~/VibranteSDK/toolchains/tegra-4.9-nv $ export BB_ENV_EXTRAWHITE="$BB_ENV_EXTRAWHITE TOOLCHAIN_PATH KERN_DIR PLATFORM_TOPDIR" Add NVLAYER_DIR to local.conf: $ echo 'NVLAYER_DIR = "${TOPDIR}/../sources/nvidia-layer"' >> conf/local.conf Build your image: $ bitbake b2qt-embedded-qt5-image Flash your board: $ cd $PLATFORM_TOPDIR $ mv targetfs targetfs-old $ cd targetfs && tar xf /path/to/rootfs.tar.bz2 $ cd ../../vibrante-t186ref-foundation/utils/scripts/bootburn $ ./bootburn.sh -b p2382-t186 Change-Id: I4209cd0c19a007c4457460fd67342fc579c2a735 Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
* qt5: move mingw32 specific parts from meta-qt5Samuli Piippo2016-03-091-0/+180
| | | | | Change-Id: Id380844d530ef599f78591a282474aa66d3dec69 Reviewed-by: David Schulz <david.schulz@theqtcompany.com>
* Changed eglfs kms as default platform plugin for NUC device.Teemu Holappa2016-01-281-0/+10
| | | | | Change-Id: I0f6a4ad478ff786940d9f680d3fd546af950082d Reviewed-by: Samuli Piippo <samuli.piippo@theqtcompany.com>
* Added support for Jetson-tk1-pro device.Teemu Holappa2015-12-141-0/+11
| | | | | | | The configuration has dependency to the interal repositories (meta-tegra and jetson-tk1-pro). Change-Id: I5e13377cf8cfbe4fad3f19215a292b49195f1546 Reviewed-by: Samuli Piippo <samuli.piippo@theqtcompany.com>
* Merge "Merge remote-tracking branch 'origin/dizzy' into dev" into ↵Samuli Piippo2015-11-035-0/+12
|\ | | | | | | refs/staging/dev
| * qt5: oe-device-extra.pri is now supported in upstreamSamuli Piippo2015-10-265-0/+12
| | | | | | | | | | | | | | | | 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>
* | Remove qdoc patch not needed for anymore in dev/5.6Laszlo Agocs2015-11-031-29/+0
|/ | | | | Change-Id: I5013bb78d9e0140b52b29d9789f97b0f0037eb48 Reviewed-by: Samuli Piippo <samuli.piippo@theqtcompany.com>
* qt5: add workaround for gcc's internal compiler errorSamuli Piippo2015-09-161-0/+29
| | | | | | | | | Crosscompilation of qdoc causes gcc internal compiler error on some platforms. Removing the c++11 option from the compilation prevents this. Change-Id: I0ad5832859f8c79dba401ecc1d9026559a1ec324 Reviewed-by: aavit <eirik.aavitsland@theqtcompany.com>
* Update to using Qt 5.5Samuli Piippo2015-06-162-3/+2
| | | | | | | | | | | | | | Changes required to support Qt 5.5. - eglfs hooks are now plugins - disable Qt .bbappends from meta-fsl-extra - include qt3d and qtcanvas3d to image - remove QtQuickEnterpriseControls - use Qt Quick Compiler 3.0 - update Qt VKB sha1 - use 5.5 branch from meta-qt5 (playground repo) Change-Id: I6fe830ee1edf6937c40ddedba06fdf1694f9dacc Reviewed-by: Eirik Aavitsland <eirik.aavitsland@theqtcompany.com>
* Toolchain: add static device mkspec, suitable for Qt CreatorEirik Aavitsland2015-05-285-0/+24
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>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-07-23 01:08:34 +0000