Fix build of clangrefactoring backend on Windows

Broke in ccab835455

Change-Id: Ic5db7597cb6cc3c798987997d8fe50c4d801ec8e
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
This commit is contained in:
Cristian Adam
2019-09-19 11:53:11 +02:00
committed by Eike Ziller
parent aa198b7e88
commit 2e63d2c7d3
3 changed files with 3 additions and 3 deletions

View File

@@ -57,7 +57,7 @@ QString processArguments(QCoreApplication &application)
}
#ifdef Q_OS_WIN
extern "C" void OutputDebugStringW(const wchar_t* msg);
extern "C" void __stdcall OutputDebugStringW(const wchar_t* msg);
static void messageOutput(QtMsgType type, const QMessageLogContext &/*context*/,
const QString &msg)
{

View File

@@ -247,7 +247,7 @@ struct Data // because we have a cycle dependency
};
#ifdef Q_OS_WIN
extern "C" void OutputDebugStringW(const wchar_t* msg);
extern "C" void __stdcall OutputDebugStringW(const wchar_t* msg);
static void messageOutput(QtMsgType type, const QMessageLogContext &, const QString &msg)
{
OutputDebugStringW(msg.toStdWString().c_str());

View File

@@ -131,7 +131,7 @@ struct Data // because we have a cycle dependency
};
#ifdef Q_OS_WIN
extern "C" void OutputDebugStringW(const wchar_t* msg);
extern "C" void __stdcall OutputDebugStringW(const wchar_t* msg);
static void messageOutput(QtMsgType type, const QMessageLogContext &, const QString &msg)
{
OutputDebugStringW(msg.toStdWString().c_str());