Debugger/LLDB: Fix build on Windows.

Change-Id: I7cf64967f0fc5cc54d59b88ed08c445781ec56e1
Reviewed-by: Christian Stenger <christian.stenger@digia.com>

1 files changed, 8 insertions, 0 deletions

diff --git a/src/plugins/debugger/lldb/lldbengine.cpp b/src/plugins/debugger/lldb/lldbengine.cpp
index 714da360f0..6b7884681e 100644
--- a/src/plugins/debugger/lldb/lldbengine.cpp
+++ b/src/plugins/debugger/lldb/lldbengine.cpp
@@ -201,7 +201,11 @@ void LldbEngine::setupInferior()
     const DebuggerStartParameters &sp = startParameters();
 
     QString executable;
+#ifdef Q_OS_WIN
+    QString args;
+#else
     QStringList args;
+#endif
     Utils::QtcProcess::prepareCommand(QFileInfo(sp.executable).absoluteFilePath(),
                                       sp.processArgs, &executable, &args);
 
@@ -209,8 +213,12 @@ void LldbEngine::setupInferior()
     cmd.arg("executable", executable);
     cmd.arg("startMode", sp.startMode); // directly relying on this is brittle wrt. insertions, so check it here
     cmd.beginList("processArgs");
+#ifdef Q_OS_WIN
+    // fixme?
+#else
     foreach (const QString &arg, args)
         cmd.arg(arg.toUtf8().toHex());
+#endif
     cmd.endList();
 
     // it is better not to check the start mode on the python sid (as we would have to duplicate the