Github Push to arBmind/qt-creator
-
Use QTEST_GUILESS_MAIN where applicable
instead of QTEST_MAIN. Reduces the initialization that is done by the Qt
test applications, and can also reduce interference with normal OS
operations like the current window loosing focus.
Change-Id: If88f289281aa1c8703ac7d4dbe0799d067c16588
Reviewed-by: Christian Stenger
Reviewed-by: Qt CI Bot
-
CppEditor: Fix looking up containing function for search result
- Move look-up to CplusPlus::FindUsages, where we are guaranteed that
we actually have the document source.
- Use the same straightforward algorithm as with clangd.
- Undo the changes to CppDocument::functionAt(), which broke
the autotest.
Amends 6f7e7980d2b604c79507f9165098f783db8ab2e3.
Change-Id: I008d05ba41a3b63b71e3131d7021e0d4e7d0641f
Reviewed-by: Qt CI Bot
Reviewed-by: Christian Stenger
-
TextEditor: fix typo
Change-Id: Ibad6729f5281a1b7036af7483a82eae7e22649a5
Reviewed-by: Christian Stenger
-
macOS: Fix importing command line builds with CMake
When configuring a CMake project on the command line, CMake will
(correctly) find and use the compiler from the current developer
directory, usually somewhere in
/Applications/Xcode.app/Contents/Developer
But Qt Creator auto-detects and sets up the compiler /usr/bin/clang(++)
for desktop kits. This leads to a compiler mismatch between kits and the
imported build, and to new kits registered in Qt Creator for the import.
Since /usr/bin/clang(++) is just a thin wrapper that resolves to the
compiler in the current developer directory, resolve that in Qt Creator
with "xcrun -f " too (caching the result), and include that
when comparing toolchains for importing builds.
Fixes: QTCREATORBUG-27591
Change-Id: I301e2a4e267450b488b49d0c32d4ce89001bb5ec
Reviewed-by:
Reviewed-by: Qt CI Bot
Reviewed-by: Mitch Curtis
Reviewed-by: Christian Stenger
Reviewed-by: Cristian Adam
-
CMake: Make QML debugging state reflect build system state
After parsing the CMake response, we make the configuration variables
table reflect the actual configuration in the build directory. It is one
of our "promises" that we do not break an existing build configuration,
to avoid unexpected rebuilds.
This was not quite true for the "QML debugging and profiling" setting.
When that setting and the actual build directory disagreed, the user
would get a dialog asking for running CMake with additional parameters,
and when running CMake via the button in projects mode or the menu, it
would just change these configuration parameters, potentially leading to
an unexpected complete rebuild of the application.
So, after parsing check if the actual CMake configuration matches our
QML debugging setting, and if not, change the setting to "Leave at
Default", to ensure that we don't mess with the build.
Fix the "Run CMake" button state (in the "Current Configuration") when
changing the QML debugging option, which should become bold, if the
CMake parameters change.
Amends 2577ce8ba1a69ad716c2fc2a5d0d5cc742c3c4cf and fixes the drawback
mentioned there, i.e. setting the build directory of a "Debug" build
configuration to an existing build directory with QML debugging
disabled, will now simply set the QML debugging option to "Leave at
Default" instead of forcing it to "Enabled".
Change-Id: Ie6d4875d59319687d94e44e459ca76038e5813c0
Reviewed-by: Qt CI Bot
Reviewed-by: Christian Stenger
Reviewed-by: Cristian Adam
-
qbs build: Require Qt 6.2 for QmlDesigner
As in the cmake build.
Change-Id: Iedd7032093682e7cf6f423909724201f6c5840d0
Reviewed-by: Christian Stenger
-
ProjectExplorer: Move makeInstallCommand()
... from Project to BuildSystem.
More direct and less use of Target::activeBuildConfiguration().
Change-Id: I148381d23be0f9ab0750ed1440e1b2b3e25aded0
Reviewed-by: Christian Kandeler
-
LiteHtmlHelpViewer: Handle mouse back/forward buttons
Fixes: QTCREATORBUG-25168
Change-Id: I856743040e81a0164e666f14ea7efd10f208f865
Reviewed-by: Eike Ziller
-
CppEditor: remove unused function hint provider
Since we removed the libclang based backend both implementations of
ModelManagerSupport::functionHintAssistProvider returned a nullptr.
Change-Id: I113c5a08cf604eb1bb2a64a851f022ecd5c908d6
Reviewed-by: Christian Kandeler
-
CppEditor: Fix check for static-ness
... in generate getter/setter quickfixes.
Fixes: QTCREATORBUG-27547
Change-Id: I29e937ae28c0bce7cd7745b92f371b97876f3e01
Reviewed-by: Qt CI Bot
Reviewed-by: Christian Stenger
-
GitHub: Add pull request template
Add a pull request template to inform the potential contributor that the
github Qt Creator presence a mirror is, and that the only way to
contribuite is through gerrit.
Change-Id: I5ddc93f182aaaa87e465677a28705ac5efa04f7f
Reviewed-by: Eike Ziller
Reviewed-by: Alessandro Portale
-
Add install command to wizard generated CMake files
Add a default install(TARGETS ...) command.
It doesn't hurt on desktop and mobile targets, and it is required for
deployment on remote Linux devices.
Change-Id: Ib39c6130b63a9a699ff5cd81756c2913b1246142
Reviewed-by: Cristian Adam
Reviewed-by:
-
ProjectExplorer: Fix crash in toolchain widget
Amends d73d5fe0b1431b913e8cc763d5cf86471755b9ba
Fixes: QTCREATORBUG-27696
Change-Id: Id94f39cd4fc6768af3f66039f808ed7c974cfeed
Reviewed-by: Qt CI Bot
Reviewed-by:
Reviewed-by: Eike Ziller
-
GitHub Actions: Update Qt version to 6.3.0
To be in sync with coin and packaging jobs.
Change-Id: I71e95e8283c70a17c42dadeb893ad4b24977f574
Reviewed-by:
Reviewed-by: Eike Ziller
-
Fix public key deployment in device wizard
Since there is no easy way to make device temporary added
into cloned device manager, we construct a full ssh command
manually inside PublicKeyDeploymentDialog.
Fixes: QTCREATORBUG-27706
Change-Id: I28e368a5bff0d89094115e9eaee1395b388359fa
Reviewed-by: Eike Ziller
-
DeviceSettingsWidget: Fix testing newly added device
Save settings before starting a test, otherwise the
test for newly created device fails since the new
device was added only for the clone of device manager.
Change-Id: Ia36d2ef68740907d7fce51e31c352328de83421c
Reviewed-by: hjk
Reviewed-by: Eike Ziller
-
GenericLinuxDeviceTester: Don't continue testing when echo fails
Change-Id: I4b21e1b914816271d59f9001122aedf1eda342dc
Reviewed-by: Eike Ziller
-
Introduce ProcessBlockingInterface
This replaces the ProcessInterface::waitFor...() methods.
It's not obligatory to provide this interface when
implementing ProcessInterface subclass. In this case
generic blocking implementation will be used.
The generic implementation usually isn't as efficient as
the custom one, however, for some sophisticated implementations
of process interface, like e.g. SshProcessInterface, providing
custom implementation is really difficult and error prone.
That's why we try to keep a balance: we provide two custom
implementations for QProcessImpl and for ProcessLauncherImpl,
as they are relatively easy to implement, and rely on
generic implementation for others.
Change-Id: Ifc8bd354479ec67b2e8f74f1510f8de8883e9b94
Reviewed-by:
Reviewed-by: hjk
-
Increase ctest timeout for tst_qtcprocess
Default is 5 seconds, which is by far not enough.
Change-Id: I4a5851de3ec2268bd68b6a386efa8dfa181e0af3
Reviewed-by:
Reviewed-by: Jarek Kobus
-
QmlProjectManager: Fix crash when building with Qt5
Change-Id: Id5af5b6dfe4613f2a0669febee4622944854a999
Reviewed-by: Alessandro Portale