[Development] About pcre in qt5

[Brett Stottlemyer]

>> 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, but I guess he
hasn't managed all combinations yet. Try 
> talking to him and coordinating your efforts to get this fixed.
>
> Right now, please understand that if you turn *any* of the feature flags
(that is, if you disable any API), you're > in wholly uncharted territory
and completely unsupported. Those combinations are not tested by the CI
system and I  > doubt anyone except Suzuki-san has tried running with them.


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_CLASS includes
QCursor, and the FOR_EACH crashes trying to create meta information and is
also used to create QVariant support (which breaks without a public
constructor as explained in the QVariant docs).

Does Suzuki-san follow this list?  Hopefully compiling without a cursor
isn't an edge case and this can be addressed in Qt5.