__fastcall' incompatible with the '/clr' option
-
I reuse some Qt sources in a /CLR (MS common language runtime) project. In this environment, I receive hundreds of warnings of this kind:
src/corelib/tools/qchar.h(310): warning C4561: '__fastcall' incompatible with the '/clr' option: converting to '__stdcall'- Is this "just for information", or will this break code?
- Is using Qt in a /CLR environment supported or not?
There is a sample combining Qt and .NET in the docs, which (to me) implies that combining Qt and CLR should be possible: https://doc.qt.io/archives/qt-4.8/activeqt-dotnet.html
I have found two old "rejected" issue reports (https://bugreports.qt.io/browse/QTBUG-13823 and https://bugreports.qt.io/browse/QTBUG-5399), but they don't really tell me anything about the behavior of Qt in this environment.
-
I reuse some Qt sources in a /CLR (MS common language runtime) project. In this environment, I receive hundreds of warnings of this kind:
src/corelib/tools/qchar.h(310): warning C4561: '__fastcall' incompatible with the '/clr' option: converting to '__stdcall'- Is this "just for information", or will this break code?
- Is using Qt in a /CLR environment supported or not?
There is a sample combining Qt and .NET in the docs, which (to me) implies that combining Qt and CLR should be possible: https://doc.qt.io/archives/qt-4.8/activeqt-dotnet.html
I have found two old "rejected" issue reports (https://bugreports.qt.io/browse/QTBUG-13823 and https://bugreports.qt.io/browse/QTBUG-5399), but they don't really tell me anything about the behavior of Qt in this environment.
- Is this "just for information", or will this break code?
It's a warning, and compiler is changing
__fastcallto plain__stdcall, so that bit should be alright. -
I reuse some Qt sources in a /CLR (MS common language runtime) project. In this environment, I receive hundreds of warnings of this kind:
src/corelib/tools/qchar.h(310): warning C4561: '__fastcall' incompatible with the '/clr' option: converting to '__stdcall'- Is this "just for information", or will this break code?
- Is using Qt in a /CLR environment supported or not?
There is a sample combining Qt and .NET in the docs, which (to me) implies that combining Qt and CLR should be possible: https://doc.qt.io/archives/qt-4.8/activeqt-dotnet.html
I have found two old "rejected" issue reports (https://bugreports.qt.io/browse/QTBUG-13823 and https://bugreports.qt.io/browse/QTBUG-5399), but they don't really tell me anything about the behavior of Qt in this environment.
- Just a warning fastcall/stdcall are simply different ways to call a function and pass parameters to it
- Yes, it does. There are even official builds. But you're simply including Qt code in your project.
-
Would the official build be "Qt for Windows UWP"?
Also, from the technical FAQ in the Qt Wiki:
Is there any way to compile the Qt source code and Qt applications with /clr flag?
We don't support building Qt or Qt applications with CLR directly. To integrate existing components you can use the Active Qt http://doc.qt.io/qt-5/activeqt.html framework, which allows integration of Active X and COM object in Qt applications.
-
Would the official build be "Qt for Windows UWP"?
Also, from the technical FAQ in the Qt Wiki:
Is there any way to compile the Qt source code and Qt applications with /clr flag?
We don't support building Qt or Qt applications with CLR directly. To integrate existing components you can use the Active Qt http://doc.qt.io/qt-5/activeqt.html framework, which allows integration of Active X and COM object in Qt applications.
@Asperamanca I think I'm wrong with what I said (not a Windows developer anymore :-)). "Qt for Windows UWP" uses C++ and is not based on .Net, so no CLR.
