<div dir="ltr"><div><div><div>Hi Mark,<br><br></div>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<br><br></div>HTH,<br></div>Shawn<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 18, 2017 at 3:16 PM, Mark Olesen <span dir="ltr"><<a href="mailto:Mark.Olesen@esi-group.com" target="_blank">Mark.Olesen@esi-group.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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:<br>
<br>
cmake -DPARAVIEW_BUILD_QT_GUI=ON -DQT_QMAKE_EXECUTABLE:<wbr>FILEPATH=/software/path/qt-5.<wbr>7.1/bin/qmake -DPARAVIEW_QT_VERSION:STRING=5 ...<br>
<br>
However, the find_package(Qt5) locates the system Qt and its cmake file, which bombs out:<br>
<br>
CMake Error at CMake/ParaViewQt.cmake:65 (find_package):<br>
Could not find a configuration file for package "Qt5" that is compatible<br>
with requested version "5.6".<br>
The following configuration files were considered but not accepted:<br>
/usr/lib64/cmake/Qt5/<wbr>Qt5Config.cmake, version: 5.5.1<br>
/usr/lib64/cmake/Qt5/<wbr>Qt5Config.cmake, version: 5.5.1<br>
Call Stack (most recent call first):<br>
Qt/Widgets/CMakeLists.txt:200 (pv_find_package_qt)<br>
<br>
<br>
Which config variables am I missing?<br>
<br>
Thanks,<br>
/mark<br>
______________________________<wbr>__________<br>
From: ParaView <<a href="mailto:paraview-bounces@paraview.org">paraview-bounces@paraview.org</a><wbr>> on behalf of Utkarsh Ayachit <<a href="mailto:utkarsh.ayachit@kitware.com">utkarsh.ayachit@kitware.com</a>><br>
Sent: Monday, January 16, 2017 7:51:36 PM<br>
To: ParaView Developers<br>
Cc: ParaView<br>
Subject: [Paraview] ParaView and Qt 5<br>
<div class="HOEnZb"><div class="h5"><br>
Folks,<br>
<br>
With upcoming release (5.3), we plan to move to using Qt 5 by default.<br>
Qt 5 has been out since 2012 and it is well supported on modern<br>
platforms. ParaView will continue to build with Qt 4 until further<br>
notice, but we highly recommend custom application developers and<br>
plugin developers to move to Qt 5 at the earliest since active<br>
development and testing for ParaView will happen with Qt 5.<br>
<br>
Changes [1] that landed in master earlier today update ParaView to now<br>
use QOpenGLWidget for rendering which creates a frame buffer object to<br>
do all the rendering in. If you have custom mapper or rendering code<br>
that assumed it was rendering to the default onscreen frame buffer, it<br>
will not work correctly and will need to be updated. Please use the<br>
mailing, if you encounter any such issues. For everything else, the<br>
changes should be fairly transparent except in exceptions documented<br>
here [2].<br>
<br>
In the upcoming weeks, we will update the superbuild and dashboards to<br>
build and test using Qt 5.<br>
<br>
Thanks,<br>
Utkarsh<br>
<br>
<br>
[1] <a href="https://gitlab.kitware.com/paraview/paraview/merge_requests/1279" rel="noreferrer" target="_blank">https://gitlab.kitware.com/<wbr>paraview/paraview/merge_<wbr>requests/1279</a><br>
[2] <a href="https://gitlab.kitware.com/paraview/paraview/blob/master/Utilities/Doxygen/pages/MajorAPIChanges.md#changes-in-53" rel="noreferrer" target="_blank">https://gitlab.kitware.com/<wbr>paraview/paraview/blob/master/<wbr>Utilities/Doxygen/pages/<wbr>MajorAPIChanges.md#changes-in-<wbr>53</a><br>
______________________________<wbr>_________________<br>
Powered by <a href="http://www.kitware.com" rel="noreferrer" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" rel="noreferrer" target="_blank">http://www.kitware.com/<wbr>opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the ParaView Wiki at: <a href="http://paraview.org/Wiki/ParaView" rel="noreferrer" target="_blank">http://paraview.org/Wiki/<wbr>ParaView</a><br>
<br>
Search the list archives at: <a href="http://markmail.org/search/?q=ParaView" rel="noreferrer" target="_blank">http://markmail.org/search/?q=<wbr>ParaView</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://public.kitware.com/mailman/listinfo/paraview" rel="noreferrer" target="_blank">http://public.kitware.com/<wbr>mailman/listinfo/paraview</a><br>
______________________________<wbr>_________________<br>
Powered by <a href="http://www.kitware.com" rel="noreferrer" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" rel="noreferrer" target="_blank">http://www.kitware.com/<wbr>opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the ParaView Wiki at: <a href="http://paraview.org/Wiki/ParaView" rel="noreferrer" target="_blank">http://paraview.org/Wiki/<wbr>ParaView</a><br>
<br>
Search the list archives at: <a href="http://markmail.org/search/?q=ParaView" rel="noreferrer" target="_blank">http://markmail.org/search/?q=<wbr>ParaView</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://public.kitware.com/mailman/listinfo/paraview" rel="noreferrer" target="_blank">http://public.kitware.com/<wbr>mailman/listinfo/paraview</a><br>
</div></div></blockquote></div><br></div>