Qt4to5

We update dependencies from Qt4 to Qt5. There should be no major change in the API but here are the main modifications we made :

• Module name is now OTBQT
• Variables and macros (if home made) do not have any version number anymore
• Variables such as QT_LMAKE_EXECUTABLE or QT_LMAKE_EXECUTABLE are not cached anymore

changed the description

changed milestone to %6.6.0

added To Do refactoring labels

added 2 commits

• 37f33909 - COMP: #1502 (closed) Fixed warning: format ‘%s’ expects argument of type ‘char*’, but…
• 8dcff543 - COMP: #1502 (closed) Replaced some dynamic assert() by static_assert().

Compare with previous version

Can we remove this Q_MOC_RUN definition?

Problem seems to still exist with Qt5 [1]. However, the #ifndef Q_MOC_RUN directive should enclose only boost #include<> onesand not all OTB Qt classes ones.

[1] https://forum.qt.io/topic/22458/semi-solved-qt5-moc-error-in-combination-with-boost/6

I'm not able to configure the branch with the default cmake settings. I've got the following CMake error:

======================= End of OTB cmake summary ======================= CMake Error at i18n/CMakeLists.txt:70 (qt5_add_translation): Unknown CMake command "qt5_add_translation".

The reason is that there are 2 cmake option OTB_USE_QT4 and OTB_USE_QT5.

Are we agree that we need only OTB_USE_QT option which will use Qt5?

added 1 commit

• ed922b14 - SuperBuild: adding an external cmake for QT5

Compare with previous version

added 1 commit

• 0fbabdfd - SuperBuild: adding option to config command

Compare with previous version

added 1 commit

• b370c8c5 - SuperBuild: work on Qt5 build on windows

Compare with previous version

added 1 commit

• 0cd76d38 - SuperBuild: unknown option demos

Compare with previous version

From my point of view, I agree that there should be only one OTB_USE_QT option (because we cannot switch between Qt4 and Qt5 but we can only enable/disable Qt support in OTB).

Yes, we are replacing qt4 by qt5 step by step. The branch cannot build with qt4. Maybe the default settings are still using QT4!

Anyway, yes we can change the name to QT instead of QTVersionNum. But we are not there yet! This can be done when everything will be clean!

Maybe, you should set OTB_USE_QT4=OFF and OTB_USE_QT5=ON.

added 3 commits

• 48c3a5d4 - SuperBuild: fix broken list of configure options
• e6ee9c27 - SuperBuild: by default use Qt5, not Qt4
• 6b741d3a - SuperBuild: qwt uses Qt5

Compare with previous version

added 1 commit

• 14b544a4 - SuperBuild: fix configure list QT5

Compare with previous version

added 1 commit

• e4c28c81 - ENH: change qt4 to 5 in translation macro

Compare with previous version

added 1 commit

• f09c5e69 - BUG: add execution permission to .sh.in

Compare with previous version

added 1 commit

• 211c9613 - SuperBuild: get rid of no know command line arguments

Compare with previous version

added 1 commit

• 753057a6 - SuperBuild: change QT5 build directory

Compare with previous version

added 1 commit

• e59409e9 - SuperBuild: patch for jpeg detection on windows

Compare with previous version