| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
| |
configure-qtcreator.sh failed with errors:
find: ‘/opt/b2qt/2.2.1/sysroots/aarch64-poky-linux/var/cache/cups’: Permission denied
find: ‘/opt/b2qt/2.2.1/sysroots/aarch64-poky-linux/var/spool/cups’: Permission denied
find: ‘/opt/b2qt/2.2.1/sysroots/aarch64-poky-linux/home/root’: Permission denied
find: ‘/opt/b2qt/2.2.1/sysroots/aarch64-poky-linux/etc/cups/ssl’: Permission denied
Change-Id: I4e8098227852b8d77b4b57a68d9e0b95165cb4fe
Reviewed-by: Samuli Piippo <samuli.piippo@qt.io>
|
|
|
|
|
|
|
|
| |
This caused the given ABI for C++ compiler to be invalid. This was
usually not harmful, because Qt Creator guessed correctly as a fallback.
Change-Id: Ieff4e69d6bd635bbabd0420cf57b61755be381c5
Reviewed-by: Samuli Piippo <samuli.piippo@qt.io>
|
|
|
|
|
|
|
|
| |
Switch from adb to qdb when using QtCreator with custom
toolchain.
Change-Id: Iaf026a5550bc41f87fc20d062012ed1652ee6f8e
Reviewed-by: Kari Oikarinen <kari.oikarinen@qt.io>
|
|
|
|
|
|
|
|
| |
The application manager plugin needs own versions of Qt and Kit to work
correctly. Those can be enabled with --appman argument.
Change-Id: I089366367dad310f15b10d727931b0be46a97d93
Reviewed-by: Wolfgang Bremer <wolfgang.bremer@pelagicore.com>
|
|
|
|
|
|
|
|
| |
sdktool outputs "Error: Id was not found." when trying to remove
debugger id that doesn't exists.
Change-Id: I6ebb700e8b785b9309835cb5fba501db56f65084
Reviewed-by: Mikko Gronoff <mikko.gronoff@qt.io>
|
|
|
|
|
|
|
|
| |
Using new sdktool interfaces for <LANG>toolchain and debugger.
Change-Id: I0ddd788feba74280bda760826dd154a284ea9979
Reviewed-by: Mikko Gronoff <mikko.gronoff@qt.io>
Reviewed-by: Samuli Piippo <samuli.piippo@qt.io>
|
|
|
|
|
|
|
| |
License changed to GPLv3 + Commercial
Change-Id: I267c97216e717ed29071df064337e1bcf83de973
Reviewed-by: Kalle Viironen <kalle.viironen@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: Iabcf736e6f4ae2149b57c84ebdc8b5b1be82023d
Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
|
|
|
|
|
|
|
|
| |
ABI and default CONFIG file are set during build, so the script
can be called from installed toolchain without any arguments.
Change-Id: I533d79864133822f0ea86a39b8c9549280db4c38
Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
|
|
|
|
|
|
|
|
|
| |
Fix qtcreator configure script to use the correct path for mkspecs.
Also add command line argument to specify the sdktool location.
Change-Id: I6534e1df6dc01767e0e9904d12e7c51c9ec3f0bb
Reviewed-by: aavit <eirik.aavitsland@theqtcompany.com>
Reviewed-by: Teemu Holappa <teemu.holappa@theqtcompany.com>
|
|
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>
|