[Paraview] ParaView and Qt 5

[Mark Olesen]

Thanks, this solves the problem.
________________________________________
From: Shawn Waldon <shawn.waldon at kitware.com>
Sent: Wednesday, January 18, 2017 9:22:18 PM
To: Mark Olesen
Cc: Utkarsh Ayachit; ParaView Developers; ParaView
Subject: Re: [Paraview] ParaView and Qt 5

Hi Mark,

CMake uses different variables to find Qt4 vs Qt5.  QT_QMAKE_EXECUTABLE is the Qt4 variable and is ignored by the code to find Qt5.  The variable you want is: -DQt5_DIR=/software/path/qt-5.7.1/lib/cmake/Qt5

HTH,
Shawn

On Wed, Jan 18, 2017 at 3:16 PM, Mark Olesen <Mark.Olesen at esi-group.com<mailto:Mark.Olesen at esi-group.com>> wrote:
I'm trying to compile a paraview using a Qt5 (5.7.1) that I've compiled with '-qt-xcb' to avoid too many dependencies. When compiling paraview (git version), I supposed that the following would be sufficient to convey which qt to use:

cmake -DPARAVIEW_BUILD_QT_GUI=ON -DQT_QMAKE_EXECUTABLE:FILEPATH=/software/path/qt-5.7.1/bin/qmake -DPARAVIEW_QT_VERSION:STRING=5  ...

However, the find_package(Qt5) locates the system Qt and its cmake file, which bombs out:

CMake Error at CMake/ParaViewQt.cmake:65 (find_package):
  Could not find a configuration file for package "Qt5" that is compatible
  with requested version "5.6".
  The following configuration files were considered but not accepted:
    /usr/lib64/cmake/Qt5/Qt5Config.cmake, version: 5.5.1
    /usr/lib64/cmake/Qt5/Qt5Config.cmake, version: 5.5.1
Call Stack (most recent call first):
  Qt/Widgets/CMakeLists.txt:200 (pv_find_package_qt)


Which config variables am I missing?

Thanks,
/mark
________________________________________
From: ParaView <paraview-bounces at paraview.org<mailto:paraview-bounces at paraview.org>> on behalf of Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com>>
Sent: Monday, January 16, 2017 7:51:36 PM
To: ParaView Developers
Cc: ParaView
Subject: [Paraview] ParaView and Qt 5

Folks,

With upcoming release (5.3), we plan to move to using Qt 5 by default.
Qt 5 has been out since 2012 and it is well supported on modern
platforms. ParaView will continue to build with Qt 4 until further
notice, but we highly recommend custom application developers and
plugin developers to move to Qt 5 at the earliest since active
development and testing for ParaView will happen with Qt 5.

Changes [1] that landed in master earlier today update ParaView to now
use QOpenGLWidget for rendering which creates a frame buffer object to
do all the rendering in. If you have custom mapper or rendering code
that assumed it was rendering to the default onscreen frame buffer, it
will not work correctly and will need to be updated. Please use the
mailing, if you encounter any such issues. For everything else, the
changes should be fairly transparent except in exceptions documented
here [2].

In the upcoming weeks, we will update the superbuild and dashboards to
build and test using Qt 5.

Thanks,
Utkarsh


[1] https://gitlab.kitware.com/paraview/paraview/merge_requests/1279
[2] https://gitlab.kitware.com/paraview/paraview/blob/master/Utilities/Doxygen/pages/MajorAPIChanges.md#changes-in-53
_______________________________________________
Powered by www.kitware.com<http://www.kitware.com>

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview
_______________________________________________
Powered by www.kitware.com<http://www.kitware.com>

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview