| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Fixes: QBS-1451
Change-Id: I644835cf8ce18d546e6c8e2c75f689766456555d
Reviewed-by: Orgad Shaneh <orgads@gmail.com>
|
|
|
|
|
| |
Change-Id: I475736e1fb146858264cc1da99554630c3af30a9
Reviewed-by: Jörg Bornemann <joerg.bornemann@qt.io>
|
|
|
|
|
| |
Change-Id: I2d1f0704385d3ba863a832f74718068c0d00ca6d
Reviewed-by: Jörg Bornemann <joerg.bornemann@qt.io>
|
|
|
|
|
|
|
|
|
|
| |
We did not take into account that these might be located in a different
place than the target libs.
Change-Id: I2c27b6be6c8962416f1c062cd1d51ebed45f1796
Fixes: QBS-1445
Reviewed-by: Ola Røer Thorsen <ola@silentwings.no>
Reviewed-by: Jörg Bornemann <joerg.bornemann@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
| |
This functionality broke completely in c4e60ed828, which went unnoticed
because it turned into a no-op rather than causing an error.
As a result, Qt libraries tended to appear more than once on the linker
command line.
Task-number: QBS-1441
Change-Id: Ic2634b4501f0360a1adb13aa847e34e9d38674f7
Reviewed-by: Ola Røer Thorsen <ola@silentwings.no>
Reviewed-by: Jörg Bornemann <joerg.bornemann@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When re-resolving a project with an existing in-memory build graph, we
must make sure that the old project object does not remove the generated
modules from the build directory in its destructor.
This fixes the following bug in Qt Creator:
- Open a project initially (but do not build).
- Edit the project file and re-resolve.
- Build the project. This now fails, because the generated modules
were erroneously removed in step 2.
Change-Id: If6c1c1ed986e8f00e4d89ba5525bac7e032388d9
Reviewed-by: Jörg Bornemann <joerg.bornemann@qt.io>
|
|
|
|
|
|
|
|
| |
Amends commit f4f443a16a342300638d364175cf2958279cf23f.
Change-Id: Ied9bd9188e719657228a53b7a7f1baca86c1bd71
Reviewed-by: Ivan Komissarov <ABBAPOH@gmail.com>
Reviewed-by: Jörg Bornemann <joerg.bornemann@qt.io>
|
|
|
|
|
|
| |
Fixes: QBS-1447
Change-Id: Ie03530e960cbcf0ab14a9cb501a169aec311ec1a
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
|
|
|
|
|
| |
Task-number: QBS-1447
Change-Id: Icdd94b7731d1c84a225c53f780e339f9c7034320
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
|
|
|
|
| |
Change-Id: Id352796fbf535e381bafd7f98dd5a53b785f9064
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
|
|
|
|
|
|
|
| |
As of 3f80c821e9, we no longer link plugins into static libraries.
Change-Id: I35816d0d84b8758fb9792387bf450d53d7ea6e5a
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
|
|
|
|
|
|
|
|
|
| |
QtCreator does not set the qbs.architecture property for the ios-
simulator and the condition check for the Qt modules fails.
Task-number: QBS-838
Change-Id: I39fe4ad75d3261a6b83f81bf0593ee9445bcefd8
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
|
|
|
|
|
|
|
|
| |
Plugins should only be linked into applications and shared libraries.
Change-Id: I95adc3f1f1ec8ea512e4166e78be1d9c5abb6745
Fixes: QBS-1441
Reviewed-by: Ola Røer Thorsen <ola@silentwings.no>
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
|
|
|
|
|
|
|
|
|
|
|
| |
It seems, that QSettings is not working properly with SystemScope on
Macos (QTBUG-21062). QSettings::fileName returns a path to a file in a
test directory, not in "/Library/Application Support" as expected. Thus,
canWriteToSystemSettings is true and test fails when real qbs binary
tries to write to the /Library... location
Change-Id: I726360a1daacf4871f944f5afe30089083283dce
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
|
|
|
|
| |
Change-Id: Iebe425c3e10be927666dd19d3be86bd30d8a43cd
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
|
|
|
|
|
|
| |
stdout is a define and should not be used as a variable name
Change-Id: If84e526211bcaf8f3f7e169d95c5ea093e712ef4
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
|
|
|
|
|
|
|
| |
On Macos, default bison version is 2.3 which means newer syntax is not
recognized and test fails
Change-Id: I1180528fc8f4aa49f5327e736c1c97dade53c194
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
|
|
|
|
|
|
| |
LC_BUILD_VERSION was introduced in apple clang 10.0
Change-Id: I06dd5bba7cab7d28d83c50f2878b5b434e97cca0
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
|
|
|
|
|
|
| |
Since macOS 10.14, the LC_VERSION_MIN_MACOSX is not inserted into binary when compiling for the current macOS
Change-Id: Id5fce8fecc656916d3b1c2cb9f07716b6c86a07a
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
|
|
|
|
|
|
| |
remove \r\n or \n from the qmake query output not just \r or \n
Change-Id: I4cd12fb5e708b28eedc43381a8d67f9e54c82d9f
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
|
|
|
|
|
|
|
|
|
|
| |
Apparently, windeployqt copies all resources into the directory of the
first binary it encounters on the command line. So make sure that binary
is qbs.exe and not one of our plugins, as we want the libs to end up
under bin/.
Change-Id: Ib23f1b355a058ca1deec5e10535c68dc9170a2bf
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
|
|
|
|
|
| |
Change-Id: I48e8efd18b026e2d8f58e2ae2ddc60b67c9acf68
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
|
|
|
|
|
|
|
| |
Configs must be prepended by 'config:' when building with newer qbs
versions.
Change-Id: I9524c1a7f034cb5a612a5408a57ad224cfcda6c3
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
|
|
|
|
| |
Change-Id: I34cb21cb3f05b9108b8fa26c73888d0992fd1c68
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
|
|
|
|
|
|
|
|
|
|
|
| |
In Qt 5.12, the deployment target information has moved from qmake.conf
into an included file, so let's expand the includes before looking for
the respective line.
Fixes: QBS-1434
Change-Id: I174c03cf227f319e33f484e82735d7ed550c2b11
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
|
|
|
|
|
|
|
| |
... the same way as Android.sdk.platform.
Change-Id: I974fdfd9f56f312cbd39ea155d87694622a9c0b8
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
|
|
|
|
|
|
|
| |
I now get a different error message after a system update.
Change-Id: Ic403e065c80e9297eadb636faf06a057d9328be6
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
|
|
|
|
|
|
|
|
| |
Added some additional allowed output patterns (for MCS51
architecture).
Change-Id: I68629566ea11c53fd5d4c10ae6e1c4e668a70694
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
|
|
|
|
|
|
| |
MSVC 2017 starts at 19.1, not 19.10.
Change-Id: Ib65d36ca19af829c8e616f40db6bcb11d9b288f0
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
|
|
|
|
|
|
|
|
|
| |
The version number for recent MSVC2017 installation has changed to the
format \d+\.\d+\.\d+\.\d+ and the second number is not guaranteed to be
a zero.
Change-Id: I13728d2a5ea3162c3ff29558757cd576a83f4983
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
|
|
|
|
| |
Change-Id: I7654eb66ea4a11c9e7e035d3512f2b0601733b28
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
|
|
|
|
|
|
|
|
| |
The --*-version arguments cannot be mixed with --cflags and --libs.
Change-Id: I6326fd34f4698cb91cdaa592d7843bd2fdeaa7cf
Fixes: QBS-1430
Reviewed-by: Kai Dohmen <psykai1993@googlemail.com>
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
None of them really necessary or even desirable to fix, but...
tools/launcherinterface.cpp:114:80: warning: ‘void QProcess::finished(int)’ is deprecated:
Use QProcess::finished(int, QProcess::ExitStatus) instead [-Wdeprecated-declarations]
api/projectdata.cpp: In function ‘QString qbs::mapToString(const QVariantMap&, const QString&)’:
api/projectdata.cpp:882:15: warning: ‘void qSort(Container&) [with Container = QStringList]’
is deprecated: Use std::sort [-Wdeprecated-declarations]
parser/qmljsparser.cpp: In member function ‘void QbsQmlJS::Parser::reallocateStack()’:
parser/qmljsparser.cpp:72:104: warning: ‘void* realloc(void*, size_t)’ moving an object of non-trivially copyable type ‘class QStringRef’; use ‘new’ and ‘delete’ instead [-Wclass-memaccess]
etc.
The QStringRef is the only one theoretically applicable, but isn't in
practice given the current implementation.
Change-Id: Idb2a03e3fd096b6ad428615f81266f952d2a8d95
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
|
|
|
|
|
|
|
|
| |
That's nicer than letting users get a cryptic error message when they
try to install their package on the device.
Change-Id: Ie5321a28475f879f991c4440c7e64c1c3ebd5a9d
Fixes: QBS-1428
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
|
|
|
|
|
|
|
|
|
| |
This fixes this clang-tidy warning:
warning: avoid repeating the return type from the declaration; use a braced initializer list instead [modernize-return-braced-init-list]
Change-Id: I421e1e47462fe0e97788672684d47943af7df850
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
|
|
|
|
| |
Change-Id: I1b02b1674794760ad973e04fad833e43e4190228
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
|
|
|
|
|
| |
Change-Id: I7419cc3fbc1e8776de3943852dcedab4c95d1c32
Reviewed-by: Anton Kudryavtsev <antkudr@mail.ru>
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
|
|
|
|
|
|
|
| |
One exception is that the 'typedef' for function pointers
were skipped due to an additional work is required.
Change-Id: I2112fded3abeaee1d1f49f56adfd2914d5db0324
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
|
|
|
|
|
| |
Change-Id: I592d433e7c473ae9f27ca08e701516efe53650ba
Reviewed-by: Ivan Komissarov <ABBAPOH@gmail.com>
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
|
|
|
|
|
|
|
| |
This fixes -Wclazy-detaching-temporary
Change-Id: I3c866c29c05f16e93eb86551efb21ccf9dc120b9
Reviewed-by: Denis Shienkov <denis.shienkov@gmail.com>
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
|
|
|
|
|
|
| |
This fixes -Wclazy-range-loop
Change-Id: I5424d2626d6134ac7be2ce70b83f5a617f58dd7e
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
|
|
|
|
|
| |
Change-Id: I040e90bebe51e587e21b5db3292790a1b2f172f7
Reviewed-by: Denis Shienkov <denis.shienkov@gmail.com>
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
|
|
|
|
|
|
| |
Task-number: QBS-1187
Change-Id: If6fa86c37bfff26ae84a3833a2cc291120fe731b
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
|
|
|
|
|
|
| |
Fixes -Wloop-range-analysis
Change-Id: I16b1852aa357fb7aeb09d29e3cb6106cad0adf7b
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
... from the qbs console using the 'setup-toolchains' command.
To create the KEIL profile it is enougth to use the following
command:
qbs setup-toolchains --type keil <path/to/keil/compiler/binary>
<profile name>
A toolchain type can be omitted; in this case the QBS will
tries to detect the toolchain type from the specified compiler
name.
Also it is possible to auto-detect the KEIL toolchain from the
PATH environment using the following command:
qbs setup-toolchain --detect
At current time are supported the following KEIL toolchains:
* for 8051
* for ARM
Change-Id: I80241866c3ec49a4294d896c70b65b75a2341a2a
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
|
|
|
|
| |
Change-Id: Id8467f8bb703ffc98b0f77cd390a7e8a22961ac8
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
|
|
|
|
| |
Change-Id: If126c3b27272386ed513fdfdbf9448ec00019c11
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The pre-defined '__AVR_ARCH__' macro just defines a machine
specific type of a core:
https://www.microchip.com/webdoc/AVRLibcReferenceManual/using_tools_1using_avr_gcc_mach_opt.html
Each core may differ in the size of a RAM, ROM, FLASH, presence
of an additional instructions or a periphery, but an architecture
always is 8-bit RISC AVR.
Change-Id: I39b12e6b4cf4a24a1c5c27c61c31a6e01437acea
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
|
|
|
|
| |
Change-Id: I7a3c0f8f7df793f23a5411d39a6383d232ddedf6
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
... from the qbs console using the 'setup-toolchains' command.
To create the IAR profile it is enougth to use the following
command:
qbs setup-toolchains --type iar <path/to/iar/compiler/binary> <profile name>
A toolchain type can be omitted; in this case the QBS will
tries to detect the toolchain type from the specified compiler
name.
Also it is possible to auto-detect the IAR toolchain from the
PATH environment using the following command:
qbs setup-toolchain --detect
At current time are supported the following IAR toolchains:
* for 8051
* for ARM
* for AVR
Change-Id: I5cdc406e475da7c6649427138b8852239012dbea
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|