Hi Thiago,
Thiago Macieira wrote:
> It's a missing #include, it has to be.
In fact a missing #define as it turned out... :-)
To make the long story short: the problem was that the win32-msvc2013
mkspec has -DWIN32 in it whereas win32-icc doesn't.
I'll write up the details under QTBUG-43778. May
Hi Thiago,
Thiago Macieira wrote:
> It's a missing #include, it has to be.
In fact a missing #define as it turned out... :-)
To make the long story short: the problem was that the win32-msvc2013
mkspec has -DWIN32 in it whereas win32-icc doesn't.
I'll write up the detail
Hi Igor,
if you're using the code quoted in your message then you have simply registered
your pointer class with the wrong type name. If you use
qRegisterMetaType("SharedInt");
then things should work.
You should also be careful with typedefs like "SharedInt" for your pointer
class. Qt's meta t
Hi Jan-Arve,
thanks a lot for your suggestions.
I agree that simply using MSVC to build just iAccessible2 should do the job,
but I would keep that as a last resort solution (i.e. if it ever turns out to
be more than a missing header or so) since it's... ugly, as you said.
As far as I can see a
Hi Emre,
Well, there are not so many enlightening things to say.
Intel C++ on Windows is not among the "supported platforms" for Qt 5:
http://doc.qt.io/QtSupportedPlatforms/index.html
Which doesn't mean it can't be made to work. As far as I understand, Intel C++
and Visual C++ should in general
Hello Thiago!
Thank you very much; this is very helpful.
It's also good to know that there is support for Intel C++ on Windows in the
forums.
I'll try to compile earlier versions of Qt5 and see if they break and if they
do where -- maybe this will give a hint where the problem came from.
I alr
Hi all,
has anyone been successful with building Qt5 on Windows with the Intel compiler
lately?
I know that this is not an "officially supported" platform, so if it can't be
done at all I would be happy to hear that and abandon the Intel compiler.
The current Qt (5.4) builds mostly nicely exce
