> If I add the QT_NO_CURSOR flag, Qt5 won’t compile at all. I’m more concerned
> about QT_NO_CURSOR not compiling for Qt5.
Here is more detail on the compile errors I am getting:
From the build log:
cd src\gui\ && "C:\Program Files (x86)\Microsoft Visual Studio
9.0\VC\BIN\nmake
>> I'm hitting the same issue the QT_NO_CURSOR. If I don't compile with this
>> flag, apps crash because the cursor isn't built onto the device. QCursor
>> has no constructor when compiled with QT_NO_CURSOR, but the QMetatype seems
>> to assume it is there. That is QT_FOR_EACH_STATIC_CORE_CLA
>> And also, we find that so many feature flags can't be easily disabled
>> for
>> example: QT_NO_DATASTREAM etc., as it seems many codes are not fully
>> controlled on some feature flag. So is that caused as the Qt5 code
>> refine ??
>
> Tasuku Suzuki has been trying to fix the feature system,
I wrote
>Im having a similar issue, but a bit farther off the beaten path. Im on
VS2008, but trying to cross compile for Wince.
Found the issue.
The problem was the parameters for syncqt. The link Rohan posted had stuff
like:
Project MESSAGE: c:\test\recipes\187508955\base\qtbase\bin\syncqt
Hi all,
I'm having a similar issue, but a bit farther off the beaten path. I'm on
VS2008, but trying to cross compile for Wince.
I can get the compile to finish after applying a number of patches and
hacks, but only if I manually add QtV8 to the include and lib paths for a
bunch of qtdecla
