- Add oars content rating to appdata xml
- Add screenshots to appdata xml
- Add release info
Change-Id: I61bf023814149983f7a64e03f49eb8d998dac85b
Reviewed-by: Youri Westerman <tetracon@gmail.com>
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
Previously, if enabled in the configuration, system
GDB pretty printers were loaded only once for all
objfiles present at the point in time when the loading
happened, which meant that GDB pretty printers for
objfiles loaded later were not taken into account
and thus unavailable if they were defined in the
corresponding autoload scripts for the objfiles.
In order to make use of those as well, remember whether
loading of system GDB pretty printer is enabled, and if so,
evaluate the pretty printers set at the new objfiles
in the handler for GDB's new_objfile event.
Extract the functionality for handling one objfile's
pretty_printers to a separate function
'importPlainDumpersForObj' to avoid code duplication.
Note: For this to actually work, it is required that the
objfile passed to the registered GDB new_objfile handler
actually has the pretty printers set at this stage.
This was only recently implemented on GDB side, in
GDB commit 2c473def12b08100e6b56261f01112db7f6aeab5
("gdb: do autoload before notifying Python side in
new_objfile event", 2021-04-27, [1]).
Therefore, this currently only works with the current
development version of GDB built from its git master
branch, not with any already released GDB versions.
(When older GDB versions are used, this will just behave
as it used to, and the corresponding GDB pretty-printers
will not be used.)
[1] https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=2c473def12b08100e6b56261f01112db7f6aeab5
Fixes: QTCREATORBUG-25339
Change-Id: Ibc0ab16fbb75184fa199c0709bfc73954f04c193
Reviewed-by: hjk <hjk@qt.io>
toStdList() has been removed in Qt6.
Amends a2dadb3d0b.
Change-Id: Id2032d7e0a0c3345614bc56d98152c41f199af07
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
This here is a step towards making SynchronousProcess interface more
similar to QtcProcess with the final goal of unifying them.
TerminalControllingProcess is just an implementation details of
SynchronousProcess, which in turn is mostly used in Android and
VcsCommand, e.g. for 'git blame' (good test...)
In the light of 04b20a1a46 /
QTCREATORBUG-21547 and the potential need to bisect later this here
is a first baby step.
Change-Id: I48e57d9fdb7c37eb0d2a5c5eef8643d6be97c3cc
Reviewed-by: Orgad Shaneh <orgads@gmail.com>
The idea is that "everything" that can run on the real local host also
can run in a docker container mimicking the same kind of environment.
I.e. all run configurations suitable for current "Desktop" would/should
also be runnable in a docker container, ideally without noticing.
_Desktop_RunConfiguration would then be a bit of a misnomer, it's more
"things that act like 'desktop'", but that can easily be changed later.
Change-Id: I0b284135202e64b54ee86a3815efa95d75a5e29f
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
By funneling file system accesses through Utils::FilePath.
Change-Id: I13a3aac23bd5fc301edf5e5c52e0c7ebd1e6ca6c
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
Copy for now, original will vanish once all is ported.
Idea is still to reduce the number of process related classes.
To avoid a new dependency for qmlpuppet, handle questions to
the user only inside #ifdef.
Change-Id: Ib1354fc0370a87052b4f9c8460dfcf5d762a6c4e
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
No real reason not to do it, and build systems print output there.
Change-Id: Ie0f08e3e88e585098b097e7c983d54e2fea8c6f2
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
Parsed snippets are now reported in chunks of texts and variables. A
variable has a index that can be used to identify matching variables and
maybe a mangler that can be used to modify the variable when applying
the snippet.
This effictively moves the variable matching logic from the overlay to
the parser of the snippet, which is needed to implement the LSP snippet
parser.
Task-number: QTCREATORBUG-22406
Change-Id: I6999554c6c6d0f1887c98bf732473f01aa1f230c
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Server name and version are potentially interesting information.
Change-Id: I4fc9a2556d7fd8285fe0024cf0f83baf95112e65
Reviewed-by: David Schulz <david.schulz@qt.io>
Clang 12 has added a template parameter as "CALLBACK",
which conflicts with the Windows "CALLBACK" define.
Change-Id: I773899d103dcb1a852b555a1900b2de4acb6d96f
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
Start using it in Utils::Archive.
The idea is to merge SynchronousProcess into QtcProcess (or avoid its
use) to have fewer classes to make "remote-aware".
Change-Id: Ieb08f6f66eab63fd058b75e3bafa79bfbf140387
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Use it to avoid IDevice interface clutter.
Change-Id: I4a04f04e2c343593d937a402060e56ef94fcabf1
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Container file system accesses are primarily done through the host
file system by prepending the appropriate path.
This is Linux-only, and only in case the volumes are mounted to
the same relative location in the container.
As a fallback, provide the functionality also via 'docker exec'.
This is, however, too slow to be used in the future.
Change-Id: I23185ae45184cb7b1de7c723a01ab96fe9c0801e
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
The "Mac static library" case from 2011 (c9f7d779a6) is still
local-only.
Change-Id: I5b437722bc1946458f54f3bdaf3e087f9264842a
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
This patch injects the hooks that let Utils::FilePath and QtcProcess
divert their operation to IDeviceManager which in turn looks for a
device feeling responsible for a given "global" path to do the actual
work.
Change-Id: Iecc1209f0475dbdf93d6f6243714d394a30fec74
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
Youri Westerman
Aleksei German
hjk
Michael Weghorn
Christian Kandeler
David Schulz
Christian Stenger
Cristian Adam
Eike Ziller