Compiling QT5 from git with intel compiler 2013
-
Have anyone done it?Main libs are compiled without errors, but it is not possible to compile WebKit Qt library.. it breaks on JavaScriptCore compilation....
Is there any plans to support this version of intel compiler???
-
I'm sure this will be addressed, ICC is actively supported (ping development ML or Thiago on IRC).
-
bq. actively supported
I'm not sure it is actively supported :) last supported version according to mkspecs is 10.x ... :)
I'll try to catch Thiago on IRC... Thank you! -
Hi everyone!
Has anybody been successful in doing this lately, preferably under Windows?
I have been trying to get Qt 5 (beginning with 5.3 up to the latest git source) compiled with Intel C++ 2015 under Windows for months now and yet it keeps breaking at various points in the build process. Currently, I get as far as iAccessible2 which breaks with
......\3rdparty\iaccessible2\generated\x86\Accessible2_p.c(997): error: expected a "{"
CINTERFACE_PROXY_VTABLE(46) _IAccessible2ProxyVtbl =I wonder if this is just me or Qt 5 actually can't be compiled with Intel C++ under Windows at all. There is not very much about this in the Qt documentation (other than that Intel C++ is not "officially supported") and most forum posts are months/years old.
Cheers,
Carsten.
-
Hi everyone!
Has anybody been successful in doing this lately, preferably under Windows?
I have been trying to get Qt 5 (beginning with 5.3 up to the latest git source) compiled with Intel C++ 2015 under Windows for months now and yet it keeps breaking at various points in the build process. Currently, I get as far as iAccessible2 which breaks with
......\3rdparty\iaccessible2\generated\x86\Accessible2_p.c(997): error: expected a "{"
CINTERFACE_PROXY_VTABLE(46) _IAccessible2ProxyVtbl =I wonder if this is just me or Qt 5 actually can't be compiled with Intel C++ under Windows at all. There is not very much about this in the Qt documentation (other than that Intel C++ is not "officially supported") and most forum posts are months/years old.
Cheers,
Carsten.
-
I'll expand on what I've said before: Thiago is the maintainer of QtCore module, and he also works at Intel. As far as I know he is regularly checking whether it (qtbase repository) builds using ICC. However, maintainers of other modules might not do this - hence errors can show up.
Not sure if anybody will fix it for you, but you can at least try asking for help on Mailing List (interest mailing list) or on IRC. More info on those channels of communication here: "link":https://qt-project.org/contribute.
-
I'll expand on what I've said before: Thiago is the maintainer of QtCore module, and he also works at Intel. As far as I know he is regularly checking whether it (qtbase repository) builds using ICC. However, maintainers of other modules might not do this - hence errors can show up.
Not sure if anybody will fix it for you, but you can at least try asking for help on Mailing List (interest mailing list) or on IRC. More info on those channels of communication here: "link":https://qt-project.org/contribute.
-
Thanks for your comment. It's good to know that Windows/Intel is still meant to be maintained as a possible platform.
I'll post the question on the interest list and see whether I can get hold of one of the maintainers.The iAccessible2 plugin is actually part of qtbase; so currently, it should be plain impossible to build even the core Qt libs on Windows/Intel.
From what I understand, although it is termed a "plugin" there is no way to disable it other than disabling accessibility support altogether (-no-accessibility). In principle I don't need accessibility features at all, but the Qt doc advises strongly against using -no-accessibility since it seems to break various "internal parts" of Qt.
Carsten.
-
Thanks for your comment. It's good to know that Windows/Intel is still meant to be maintained as a possible platform.
I'll post the question on the interest list and see whether I can get hold of one of the maintainers.The iAccessible2 plugin is actually part of qtbase; so currently, it should be plain impossible to build even the core Qt libs on Windows/Intel.
From what I understand, although it is termed a "plugin" there is no way to disable it other than disabling accessibility support altogether (-no-accessibility). In principle I don't need accessibility features at all, but the Qt doc advises strongly against using -no-accessibility since it seems to break various "internal parts" of Qt.
Carsten.
