FTBFS on Qt < 5.5 due to QtInfoMsg

[tomman]

I'm trying to build VapourSynth editor under several Debian targets: on my Debian Testing box it builds just fine, yet it fails under Debian Stable:

g++ -c -m64 -pipe -O2 -fexpensive-optimizations -funit-at-a-time -std=c++11 -O2 -w -D_REENTRANT -fPIE -DNDEBUG -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -I. -I/opt/tsdx_workbench/include -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -I../generated/moc -I../generated/ui -o ../generated/obj-release-64bit-gcc/main.o ../src/main.cpp
../src/main.cpp: In function ‘void handleQtMessage(QtMsgType, const QMessageLogContext&, const QString&)’:
../src/main.cpp:24:10: error: ‘QtInfoMsg’ was not declared in this scope
     case QtInfoMsg:
          ^
Makefile:789: recipe for target '../generated/obj-release-64bit-gcc/main.o' failed
make: *** [../generated/obj-release-64bit-gcc/main.o] Error 1

This is because QtInfoMsg was only introduced starting with Qt 5.5: http://doc.qt.io/qt-5/qtglobal.html#QtMsgType-enum Debian Testing ships with Qt 5.6.1 (as of October 2016) so no problem there. But Stable only has 5.3.2 (and unfortunately there is no newer version available through jessie-backports yet).

Commenting out the QtInfoMsg enum entry on the switch block allows the build to finish successfully under Debian Stable.

[Aleksey Lyashin]

While I see how this can be easily fixed and shall get on it, I really don't recommend building it by any Qt version lower than 5.6.1. Don't know about Linux, but on Windows that makes video encoding crash due to bug in I/O.

[tomman]

I've yet to perform in-depth testing (at least the editor runs) since I'm still rebuilding my encoding workbench over here (I've yet to install any plugins), but it's unlikely that Debian Stable will get any newer version of Qt 5 than the one already in the repos (yes, it sucks, some packages simply don't get the attention they need from the Backports guys).

However the thing at least runs which is a good sign. Should I find a crash, expect updates from me~

[Aleksey Lyashin]

Fixed in 41e6b61.