- Scheduling running projects after they are built
- Building for run configuration
- Continuing building other apps if one fails during "Build All"
Change-Id: I9f161199394495944c6e8482b50dd9a2b4c8a92d
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
They were always printed as enabled, because the
condition is not evaluated within add_feature_info
Change-Id: I9e50648d037aebecdb895d4ce5f4de7c1fee3ead
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
Make it possible to distinguish between all and selected
test cases also for the automatic run after build feature.
Change-Id: I91715a7ae4f09cea2e31844940a6b21ae9e62157
Reviewed-by: David Schulz <david.schulz@qt.io>
This will make the build directory size smaller, as only two
pch files will be generated. Not one for every target.
Change-Id: I3eec91e7536eab1c62bff8843f075f0ef7b5fff6
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
On Windows the debugging of clang tools is not working due to the
nature of how processes are started.
This makes it possible to use DebugViewer or DebugViewPP
Change-Id: I2c1e4bb7a8fafd6f07570e5d2ba4df5b44e9d44d
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
The GMock/GTest unittest was not working with the latest translation
patches.
Change-Id: I83e337c6278cb93344c734c05d090a65def34a3b
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
Make sure to generate unique ids for each project part to unconfuse the
code model.
This was never triggered so far since before PCH support all my test projects
ended up with exactly one compile group per target:-)
Change-Id: Ida34f71f77cdf679fea7007f13ac19713175d916
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
Adding this to other readers makes no sense: PCH support in cmake
is younger than fileapi.
Change-Id: I4cd88882764ab8a8f81316a17098878c8e3699eb
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
open a document in all clients supporting the document, but have just
one client that provide functionality like highlights, completions, and
find usages.
Change-Id: I6bd72eb022005ed643fefd1da139d482f4dd5279
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
This should prevent slowdown of the IDE (and the rest of the system) while
building with all the CPU cores.
Fixes: QTCREATORBUG-5155
Change-Id: Icaadc53958f2d8e918035463e3c9344c91235615
Reviewed-by: hjk <hjk@qt.io>
Instead of re-parsing all test frameworks trigger a reparse
just for the newly added as results for the other should not
have changed.
Change-Id: I6eb53da04bb927a884d6431e137bfe68f391f2ad
Reviewed-by: David Schulz <david.schulz@qt.io>
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Users have to install Qt for WebAssembly and the tool chain,
as well as add a kit.
Fixes: QTCREATORBUG-22927
Change-Id: Id22d5fb5e7d9e676d77f3f80880030cb9c1f61c7
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
Use extend_qtc_executable instead of extend_qtc_target.
In addition to using the correct function, this also allows to
configure Qt Creator without sdktool. extend_qtc_target does not
(yet) handle disabled targets, properly.
Change-Id: Ie99f158a814c14b3e207d6ca720da074671ac9a8
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
This kind of filtering has been removed long ago
and therefore it should be impossible to get triggered.
Change-Id: Ic9ea02b5446edaadda4d7f21846b37a2f8178505
Reviewed-by: David Schulz <david.schulz@qt.io>
Avoid expanding parsing over all parsers if we trigger a
re-parse for a different parser and there is already a
re-parse postponed.
Change-Id: If74480fea2c671b32083fb7cf3f4dc4c418e6e33
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: David Schulz <david.schulz@qt.io>
Build an index between (visible) text and litehtml elements, so we can
use the regular text search functionality of Qt.
Change-Id: I2bf29628482f81c67b20b9a02d7808a330a073eb
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
Reviewed-by: hjk <hjk@qt.io>
(Optionally) re-generate .ts files from CMake by running lupdate and
run lrelease to generate .qm files.
Changes to qmake:
* src/libs/3rdparty/syntax-highlighting/src/cli/kate-syntax-highlighter.cpp
is no longer translated: It's a command line tool that is not used by creator
* src/libs/aggregation/examples/text/main.cpp is no longer included in ts files
* src/libs/qt-breakpad/qtcrashhandler/* is no longer included in ts files:
It is not built right now
Change-Id: Iec018da86a111a68ec983a880cef2961b48ccdf9
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
"\." is an invalid backslash escape sequence in JSON. QJSON accepts
this though and silently "fixes" the string by removing the stray
'\' character. This is QTBUG-78443 now, as a conforming JSON parser
should reject invalid data.
The string as "fixed" by QJSON is also not what we wanted in the
first place.
Change-Id: I070999957c6a0c3d0f1753d907ac460e9e341fc1
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
The original version is not valid JSON, even though the QJSON parser
will accept it:-/
Change-Id: Id408e4b83a62bca358191cf6fe4b3a7ce7d7c59e
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
Detect Core library for Qt 6 as well as Qt 5.
Change-Id: If4b7c0ad3adad796e56706880d03f4824b8ebcd3
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
... by a permanent connection, and only evaluate output for the
active build configuration.
Task-number: QTCREATORBUG-21235
Change-Id: I06f87f7ea680f8f25687a0c5ffc936c801ab7de0
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
... instead of Utils::FilePath
Change-Id: I4ca38ca127fbb1a503a0cb9b5228cab325519550
Reviewed-by: David Schulz <david.schulz@qt.io>
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Because we attached the model inside the transaction,
then transaction begin message was not handled properly.
Change-Id: I77a56d7874061c0af907047e38a37fec4dab12c1
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
- check case-insensitively
- need to break after the first font was found in database
Change-Id: Iddd58ec88d61b2506965a618441205e8176e383f
Reviewed-by: hjk <hjk@qt.io>