| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
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>
|
