Commit d9e6854a authored by Christian Kandeler's avatar Christian Kandeler

RemoteLinux: Never disable the run configuration.

The current implementation disables the run config if the build system
does not supply information about which executable to run. But this is
too restrictive, because users can set the executable manually.

Change-Id: Ia792c06063ca88ad7168a0dd96131266e8aaf1cb
Reviewed-by: default avatarhjk <>
parent 3b5e84e6
......@@ -35,6 +35,7 @@
#include <utils/environment.h>
#include <utils/qtcassert.h>
#include <QCoreApplication>
#include <QStringList>
#include <QTimer>
......@@ -99,6 +100,13 @@ void DeviceApplicationRunner::start(const IDevice::ConstPtr &device,
if (command.isEmpty()) {
emit reportError(QCoreApplication::translate("RemoteLinux::RemoteLinuxRunConfiguration",
"Don't know what to run.")); // FIXME: Transitional message for 3.0.
d->stopRequested = false;
d->success = true;
......@@ -120,11 +120,6 @@ void RemoteLinuxRunConfiguration::init()
bool RemoteLinuxRunConfiguration::isEnabled() const
if (remoteExecutableFilePath().isEmpty()) {
d->disabledReason = tr("Don't know what to run.");
return false;
return true;
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment