- 07 Jan, 2016 1 commit
-
-
hjk authored
* SysRoot can always be determined from kit. * Pass around RunMode as extra parameter not as part of AnalyzerStartParameters. That's closer to the pattern used elsewhere. * Environment was always initialized from the runconfig's EnvironmentAspect. The tools can do that directly. * Provide setter for display name for cases where it is not equal to RunConfiguration::displayName Change-Id: I811a0d7cdeb55cc37a16a593b3942abb567a2150 Reviewed-by:
BogDan Vatra <bogdan@kdab.com> Reviewed-by:
Ulf Hermann <ulf.hermann@theqtcompany.com>
-
- 19 Nov, 2015 1 commit
-
-
Ulf Hermann authored
We have tcp, local, and native by now. We have to expose that in a clean way. Change-Id: I0ce7be693aa7f47ebea7abe435a224a176b6c94b Reviewed-by:
Joerg Bornemann <joerg.bornemann@theqtcompany.com>
-
- 19 Aug, 2015 1 commit
-
-
Anton Kreuzkamp authored
Extends RemoteLinuxAnalyzeSupport to add information about debuggee, debuggee arguments, working directory and environment to the AnalyzerStartParameters. This is required when starting the project from an analyzer plugin using remotelinux. Change-Id: I29cbeb1b22b193a2d815924282887a980c506ca0 Reviewed-by:
Christian Kandeler <christian.kandeler@theqtcompany.com>
-
- 17 Aug, 2015 1 commit
-
-
Ulf Hermann authored
The services need to be loaded before the first QML engine is created. The first QML engine may be created before a client connects. When the JavaScript debug service is loaded the engine is put into interpreter mode as we don't support debugging in JIT mode. Profiling, however should be done in JIT mode, whenever possible. Thus, in order to avoid the loading of unnecessary plugins and to get better results from the QML profiler we tell the debug server which services we expect, even before the client connects. Qt 5.6 will support additional command line arguments to specify the services and this change uses them. Change-Id: I6dcee016c39995e9adada6eaf0e39d8299c9b7e7 Reviewed-by:
Christian Kandeler <christian.kandeler@theqtcompany.com> Reviewed-by:
hjk <hjk@theqtcompany.com>
-
- 30 Jun, 2015 1 commit
-
-
BogDan Vatra authored
This provides a way for third-party plugins to implement run modes without the need to add a value to the central enum or using manual workarounds like RunMode(*(int*)&someUniqueObject). Instead of centrally defined enum values this uses Core::Id that could be defined anywhere. Change-Id: Ic350e3d8dbb8042c61b2d4ffec993ca151f53099 Reviewed-by:
Daniel Teske <daniel.teske@theqtcompany.com> Reviewed-by:
Eike Ziller <eike.ziller@theqtcompany.com>
-
- 17 Jun, 2015 1 commit
-
-
hjk authored
This is what it is on the top level. The change makes it obvious that in the valgrind(-derived) plugins the value is later wrongly used to make a decision on whether to run the valgrind process locally or remotely. But that's isolated in valgrind now and can be fixed there. Change-Id: I6fa5e669dec1f9e2cdebe42a1591d15144082a21 Reviewed-by:
Anton Kreuzkamp <anton.kreuzkamp@kdab.com> Reviewed-by:
Christian Stenger <christian.stenger@theqtcompany.com> Reviewed-by:
Ulf Hermann <ulf.hermann@theqtcompany.com>
-
- 23 Apr, 2015 1 commit
-
-
hjk authored
Change-Id: I500faf9846f610f224808a4664d43d50cc5ad870 Reviewed-by:
Christian Kandeler <christian.kandeler@theqtcompany.com>
-
- 30 Jan, 2015 1 commit
-
-
Montel Laurent authored
Change-Id: I873a36601d54065b61d0666558b93dc839ad0dfc Reviewed-by:
hjk <hjk@theqtcompany.com>
-
- 16 Jan, 2015 1 commit
-
-
Eike Ziller authored
Change-Id: I711d5fb475ef814a1dc9d2822740e827f3f67125 Reviewed-by:
Alessandro Portale <alessandro.portale@digia.com>
-
- 09 Oct, 2014 1 commit
-
-
Eike Ziller authored
Change-Id: I3c22ef2685d7aa589f5d0ab74d693653a4c32082 Reviewed-by:
Alessandro Portale <alessandro.portale@digia.com>
-
- 10 Apr, 2014 1 commit
-
-
Benjamin Zeller authored
Adds a generic interface (AbstractRemoteLinuxRunConfiguration), so plugins can ship a custom remote runconfig. Change-Id: I4ef8e39c4c69224d4e55224c782f3d544f10c945 Reviewed-by:
Christian Kandeler <christian.kandeler@digia.com>
-
- 19 Mar, 2014 1 commit
-
-
Ulf Hermann authored
As we cannot determine reliably what happened to the app we drop the "success" parameter to notifyRemoteFinished(). It was almost always true before and where it wasn't it didn't do anything useful. The transition from AppRunning to AppKilled without AppDying in between was invalid and would have triggered an assertion when it happened. Task-number: QTCREATORBUG-11760 Change-Id: Iebf4ca9bddbcc7b152131f9574bc5f2c0a8ba44f Reviewed-by:
Daniel Teske <daniel.teske@digia.com>
-
- 08 Jan, 2014 1 commit
-
-
Robert Loehning authored
Change-Id: Ib5423fdd064e4546f848c0b640b0ed0514c26d3a Reviewed-by:
Leena Miettinen <riitta-leena.miettinen@digia.com> Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
- 05 Nov, 2013 1 commit
-
-
Kai Koehne authored
Calling fromLocal8Bit() for literals is wrong, since that depends ont the user's environment. We use latin1 strings exclusively in Qt. Change-Id: I0cd0986787ea630425773672d3a892fbd0f0a77a Reviewed-by:
hjk <hjk121@nokiamail.com>
-
- 22 Oct, 2013 1 commit
-
-
Friedemann Kleint authored
They are a hassle for translators and reviewers alike. Change-Id: I07c1b61e8b6719e54fdc1f69cf63f573119a6776 Reviewed-by:
hjk <hjk121@nokiamail.com> Reviewed-by:
Robert Loehning <robert.loehning@digia.com> Reviewed-by:
Eike Ziller <eike.ziller@digia.com>
-
- 19 Aug, 2013 1 commit
-
-
Christian Kandeler authored
Provide a QProcess-like abstraction that can be used to implement processes running locally or on a remote device. Objects of a concrete class implementing the functionality are created by IDevice objects. Current implementations are: - Local execution (QProcess-based), provided via the DesktopDevice. - Remote execution via SSH. - A specialized case of the former for remote Linux systems (provided by LinuxDevice). The latter is already being used in a number of places. As a result, lots of code dealing with details such as setting the remote environment could be moved to a central location. These things are no longer the concern of whoever is wishing to run a remote process. Change-Id: I919260ee6e77a020ca47226a4a534e7b8398106f Reviewed-by:
hjk <hjk121@nokiamail.com>
-
- 05 Aug, 2013 1 commit
-
-
Aurindam Jana authored
Change-Id: I7a4ef54a02fcc8dedb28e843a2f05d737324a877 Reviewed-by:
Christiaan Janssen <christiaan.janssen@digia.com> Reviewed-by:
hjk <hjk121@nokiamail.com>
-
- 01 Aug, 2013 1 commit
-
-
hjk authored
Change-Id: I74edaef59600a44924d2692c1ebc7f98d8581115 Reviewed-by:
Christiaan Janssen <christiaan.janssen@digia.com>
-
- 23 Jul, 2013 3 commits
-
-
Aurindam Jana authored
Change-Id: I94f931338c2e6fece2db2f74f32f26d86d6020af Reviewed-by:
Christiaan Janssen <christiaan.janssen@digia.com>
-
Aurindam Jana authored
Change-Id: I214f133f34baf0e0d7fd5a9f23502e75a1932172 Reviewed-by:
Christiaan Janssen <christiaan.janssen@digia.com>
-
Aurindam Jana authored
Fix broken debug and profiling support on remote linux. Change-Id: Ic4173a47b8fd450a92407a66fa338c18f7062736 Reviewed-by:
Christiaan Janssen <christiaan.janssen@digia.com> Reviewed-by:
Christian Kandeler <christian.kandeler@digia.com>
-
- 19 Jul, 2013 1 commit
-
-
Aurindam Jana authored
Currently only QML profiling is supported. Pass the remote command along with -qmljsdebugger argument to device. Change-Id: Ia64396f9c6da80e70cb1ee624ed974f8cc32465f Reviewed-by:
Christian Kandeler <christian.kandeler@digia.com>
-
- 07 May, 2013 2 commits
-
-
Aurindam Jana authored
Change-Id: Idee11afe23fd6fa271a0776a460d227ced9b7916 Reviewed-by:
Aurindam Jana <aurindam.jana@digia.com>
-
Aurindam Jana authored
Change-Id: I3ff14691b4f9c80793a491b61444f8ceeb05a4fb Reviewed-by:
Christiaan Janssen <christiaan.janssen@digia.com>
-