Commit 4a4592f3 authored by Rolf Eike Beer's avatar 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
parent 8c9f26dc
Pipeline #11085 failed with stage
in 60 minutes and 1 second
......@@ -275,7 +275,6 @@ void NativeAppConfigType::configureLaunchFromItem ( KConfigGroup cfg, KDevelop::
void NativeAppConfigType::configureLaunchFromCmdLineArguments ( KConfigGroup cfg, const QStringList& args ) const
{
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
cfg.writeEntry( ExecutePlugin::executableEntry, QUrl::fromLocalFile(args.first()) );
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