Bump moc revision after introducing QMetaType::SChar.
Normally we do not have to change moc version if a new type is added, but for this particular case we need to do it. It is so because the old moc could generate wrong type id (QMetaType::Char) for signed char. Change-Id: I20be2a24adc59a305674595dafe23fb1774b475d Reviewed-by: Kent Hansen <kent.hansen@nokia.com>
This commit is contained in:
parent
cf48eded4d
commit
4a1a13a81b
@ -58,7 +58,7 @@ typedef QArrayData QByteArrayData;
|
||||
class QString;
|
||||
|
||||
#ifndef Q_MOC_OUTPUT_REVISION
|
||||
#define Q_MOC_OUTPUT_REVISION 66
|
||||
#define Q_MOC_OUTPUT_REVISION 67
|
||||
#endif
|
||||
|
||||
// The following macros are our "extensions" to C++
|
||||
|
@ -43,6 +43,6 @@
|
||||
#define OUTPUTREVISION_H
|
||||
|
||||
// if the output revision changes, you MUST change it in qobjectdefs.h too
|
||||
enum { mocOutputRevision = 66 }; // moc format output revision
|
||||
enum { mocOutputRevision = 67 }; // moc format output revision
|
||||
|
||||
#endif // OUTPUTREVISION_H
|
||||
|
Loading…
Reference in New Issue
Block a user