summaryrefslogtreecommitdiffstats
path: root/recipes-qt/qt5/qtbase
Commit message (Collapse)AuthorAgeFilesLines
* 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>