Commit 3d2ff6f3 authored by Rolf Eike Beer's avatar Rolf Eike Beer Committed by Rolf Eike Beer

remove bad assert

Example on how to trigger this:
-have a CMake project with unit tests
-make clean
-try to launch one test that has an executable cleaned by the previous step

(cherry picked from commit 4a4592f3)
parent 904f73c7
Pipeline #11098 passed with stage
in 49 minutes and 38 seconds
...@@ -275,7 +275,6 @@ void NativeAppConfigType::configureLaunchFromItem ( KConfigGroup cfg, KDevelop:: ...@@ -275,7 +275,6 @@ void NativeAppConfigType::configureLaunchFromItem ( KConfigGroup cfg, KDevelop::
void NativeAppConfigType::configureLaunchFromCmdLineArguments ( KConfigGroup cfg, const QStringList& args ) const void NativeAppConfigType::configureLaunchFromCmdLineArguments ( KConfigGroup cfg, const QStringList& args ) const
{ {
cfg.writeEntry( ExecutePlugin::isExecutableEntry, true ); cfg.writeEntry( ExecutePlugin::isExecutableEntry, true );
Q_ASSERT(QFile::exists(args.first()));
// TODO: we probably want to flexibilize, but at least we won't be accepting wrong values anymore // TODO: we probably want to flexibilize, but at least we won't be accepting wrong values anymore
cfg.writeEntry( ExecutePlugin::executableEntry, QUrl::fromLocalFile(args.first()) ); cfg.writeEntry( ExecutePlugin::executableEntry, QUrl::fromLocalFile(args.first()) );
QStringList a(args); QStringList a(args);
......
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