You now have the option to create projects that you can open in QDS.
Task-number: QTCREATORBUG-28721
Change-Id: Ia8f36fd65f2356b9987b027d7b37ac6848ff7e03
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
We don't have to rely on qdoc being located alongside qmake anymore,
because nowadays Qt defines a Qt::doc target with IMPORTED_LOCATION set,
so we can use that directly.
Change-Id: I450578e711e0835e00320251dcadc78c1f02ab7d
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: <github-actions-qt-creator@cristianadam.eu>
This happens from time to time, but I do not have a way to reproduce it
safely. In order to present the user a somewhat usable state after this
error cancel the debug run and show a message box with potential fixes.
Fixes: QTCREATORBUG-24323
Change-Id: I7e557001bd5dfb3b0abb19fa635bf2d20bb3b16c
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Compilers are getting increasingly better in optimizing this stuff
out, it's difficult and rather unnecessary to keep track of all
variations.
Change-Id: I9e05d5afadc4d875dc3b61e61364cf085a825239
Reviewed-by: David Schulz <david.schulz@qt.io>
On my system where I have strawberry perl installed, the "patch.exe"
from strawberry perl is picked.
This patch.exe has issues while reverting chunks, where as git's
patch.exe works perfectly.
Change-Id: I7e8c8f91f0f841c128ff8538dba68bee161a5f7b
Reviewed-by: Orgad Shaneh <orgads@gmail.com>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Instead of performing costly computations keep
track of the currently present types in the
respective branch of the subtree.
This also makes the filter invalidation on
newly added items obsolete.
Fixes: QTCREATORBUG-28831
Change-Id: I12cd31dc95b4c310a04ced2c98de3d509032482c
Reviewed-by: David Schulz <david.schulz@qt.io>
Similar to what has been done for fixing VS2017. But VS2015 also needs
to add a matching Windows Kit tools path.
This magically happens if the kit is set up manually, but as we
provide a stripped version of toolchains and kits we need to adjust the
kit environment manually.
Change-Id: I9a88e7424acf2768774f5ef580ef6d1fa73bcb5a
Reviewed-by: David Schulz <david.schulz@qt.io>
This can get very expensive for targets that have a lot or big modules,
but are not linked against Qt. On the downside we might not be able to
identify Qt namespaces in static builds.
Task-number: QTCREATORBUG-18287
Change-Id: I90e0c4afcde17fd81d49017e828ce59f0abe9b5c
Reviewed-by: hjk <hjk@qt.io>
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
and disable the QV4::Value dumper for that version.
Change-Id: I31a0ddba2bdab3b196e4fc5298fd8e7c10f9dc92
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Use dumpbin to extract the symbols from the host dll.
Use lib to create an arm64 library to link the qtcreatorcdbext.dll arm64
shared library.
Use the PythonTargetArchDll CMake or environment variable to install the
target arm64 python.dll
If PythonTargetArchDll is not configured the script will download the
python-embed-arm64.zip, extract and set PythonTargetArchDll
Task-number: QTCREATORBUG-25859
Change-Id: I09320bb758fded546f203c905b75485d7de3b94e
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: David Schulz <david.schulz@qt.io>
For toolchains-on-device scenarios we need the devices.
Change-Id: I83547b8c342c87c1c83ed432432f8d151d7e3f1d
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
Add information about how to write plugin tests and how to integrate
unit tests.
Change-Id: I13721f03c4c55a265a93f71a7c4d892f3e53a6bb
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
That generates build files for other build systems, such as
Microsoft Visual Studio and Eclipse.
Task-number: QTCREATORBUG-28721
Change-Id: I980ee851293b41a9320b90458132ba035dc1f3f4
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
Stopping/Aborting the debugger popped an error message saying "An error
occurred when attempting to write to the process."
Change-Id: Iceb41ea6144cb4d5a6384862da5bf5638f78f519
Reviewed-by: hjk <hjk@qt.io>
This is just there at the front to force word-wrap on the tooltips, it
shouldn't be part of the translated text.
Change-Id: I62157aba303071677ca89929f9e56c03ee1f21e7
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
Reviewed-by: hjk <hjk@qt.io>
... by caching the info whether we have a debug build. This avoids
expanding members of the container to check for a potential offset of
the actual data.
Change-Id: I4d7ac83003c303185ae51d57f0f0571b627edf22
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Avoid parsing the gdbmi output twice just for printing out messages to
the debugger log.
Change-Id: I928fc3a7d55c318056afff09cfbc25d115932bc0
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
It's more flexible for the user to have them modifiable.
Tendency nowadays is to only have SDK-provided kits (or possibly
everything that also 'goes away byitself' marked autodetected.
Change-Id: I0098196320abe73998c38e9944fcb89554e36bb7
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
When expanding all children of a long array, this is called
once per item. If we have one update in the end that's enough.
Change-Id: Ibb63a9aef752418a1dcafb6190edf5a8005a855f
Reviewed-by: David Schulz <david.schulz@qt.io>
So far we insisted on a Qt version being present. For more general
use, including limited testing it's more convenient to also allow
kits being generated when no QNX Qt is around.
Change-Id: I99954b76543f2a04063a737444dce0ae5c921929
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
... by using approximations of the value widths instead of precise
comuptation.
Change-Id: Ia7eefad8d79f09d1e0cfda32067d052f56b820a9
Reviewed-by: David Schulz <david.schulz@qt.io>
The base problem is that gdb output is weird outside the 7 bit
ASCII range. Could be true UTF-8, or \x encoded UTF-8 byte
sequences, i.e. three layers of encoding.
Change-Id: Id9ee4bd4a8979624f9682f28064c3ac599afe4b9
Reviewed-by: David Schulz <david.schulz@qt.io>
