[Paraview] [Non-DoD Source] Re: Qt version support update 2016

Tue Aug 16 10:57:50 EDT 2016

Shawn,

thanks for the info. I will give it a try

thanks
-simon

________________________________
From: Shawn Waldon [shawn.waldon at kitware.com]
Sent: Monday, August 15, 2016 9:06 AM
To: Su, Simon M CIV USARMY RDECOM ARL (US)
Cc: Mega Mind; ParaView list
Subject: Re: [Non-DoD Source] Re: [Paraview] Qt version support update 2016

All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser.

________________________________

Mega Mind,

I have a project that is using ParaView with Qt 5.7 on Windows.  Of course we use VS 2013 still, so that may be the difference.  It still sounds like you forgot to set the PARAVIEW_QT_VERSION to 5.  If this is 4 (the default), the CMake scripts will ignore Qt5.  I think it may be smart enough to default to 5 when there is no Qt4 preset which may be why that build worked.  Our build machine has both Qt4 and Qt5 installed and it works fine.  Still, I don't know if anyone has tried Qt5 + VS 2015....  Anyway, your runtime error with the dll not found?  That is a Windows thing.  Not found means it is not in the PATH environment variable's list of folders.  Windows doesn't bake into the executable the paths to its runtime dependencies.  Linux and OSX do, which is why you can typically run things from a build tree there without any problems.  But to run it from Windows, you will need to add the Qt5 dll's directory to your PATH or move it to the same directory as the executable which needs it.

Simon,

The ParaView Superbuild uses a precompiled python 2.7 that was built with VS 2008.  Python 2.x doesn't support any newer versions (maybe 2010, but we've never used that version of python).  Since the API we link against is pure C, there are no ABI issues with using this prebuilt version.  You should be able to look in the superbuild and find the path for the zip file with the prebuilt python and download/use that one.  I know Python 3 is supported in VTK, but I'm not sure it is fully supported in ParaView yet.

HTH,
Shawn

On Sat, Aug 13, 2016 at 6:30 PM, Su, Simon M CIV USARMY RDECOM ARL (US) <simon.m.su.civ at mail.mil < Caution-mailto:simon.m.su.civ at mail.mil > > wrote:
you need python in the path for QT 5 to build for windows. specifically python with bz2 module.... both running configure and nmake

the next problem you will encounter after getting past the QT 5 which I am still stuck is to build python. Python 3 will compile with vs2015 express, python 2.x will not. c++ time zone related variables changes. But I am not able to compile pv with python 3.....  I even tried to fix the time zone related compile but end up with linking error at the very end.

because of this, i think win7 or win10 pv will only work with vs2013 express.....

hth
-s

________________________________
From: ParaView [paraview-bounces at paraview.org < Caution-mailto:paraview-bounces at paraview.org > ] on behalf of Mega Mind [123megamind at gmail.com < Caution-mailto:123megamind at gmail.com > ]
Sent: Saturday, August 13, 2016 5:00 PM
To: Shawn Waldon
Cc: ParaView list
Subject: [Non-DoD Source] Re: [Paraview] Qt version support update 2016

All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser.

________________________________

Have you or anyone successfully built and installed on Win7 64 with Visual Studio 2015? I always get errors when building or opening the paraview.exe. For Qt the 4.x versions seem to have only x86 installs but I installed 4.8 anyway. When trying Qt 5.7 I get a failed build with 3 errors and over 350 warnings. Also noted that in Cmake configure it would still reference Qt 4 even after setting Qt5_DIR Qt5Core_DIR Qt5Widgets_DIR  etc and changing all paths to proper reference directories. The only fix was to uninstall Qt 4 but I was able to get a build with no errors when it was using both Qt 4 & 5 strangely but when opening paraview,exe the 'system error' message was Qt5Widgets.dll does not exist. It does though and is in "C:\Program Files (x86)\Qt\5.7\msvc2015_64\bin\" so I tried to manually change that in any Cmake config file I could find but nothing worked out. I've tried hundreds of things over the past three days and read and followed the wiki many times and I'm coming to the conclusion no one is using Win 64 which seems strange to me but I guess everyone is using Unix.

On Fri, Aug 12, 2016 at 5:18 AM, Shawn Waldon <shawn.waldon at kitware.com < Caution-mailto:shawn.waldon at kitware.com >  < Caution-Caution-mailto:shawn.waldon at kitware.com < Caution-mailto:shawn.waldon at kitware.com >  > > wrote:
To use Qt5, you have to set the PARAVIEW_QT_VERSION variable to 5 (it still defaults to 4, which is why cmake is complaining).  Note that some things may be buggy when building against Qt5, I don't know the full list of current issues, just that there are some.  Also note that you have to specify the location of Qt5 differently to CMake.  CMake doesn't use the QT_QMAKE_EXECUTABLE variable for Qt5, instead it uses Qt5_DIR.  This should point to .../lib/cmake/Qt5 inside your Qt5 install.

HTH,
Shawn

On Fri, Aug 12, 2016 at 5:09 AM, Mega Mind <123megamind at gmail.com < Caution-mailto:123megamind at gmail.com >  < Caution-Caution-mailto:123megamind at gmail.com < Caution-mailto:123megamind at gmail.com >  > > wrote:
Has the Qt version support advanced close to 5.7 yet?
Cmake throws error that Qt 4.x required but read on mailing list some guys are using Qt 5.x.
I'm installing Qt 4.8.1 but the only option seems to be x86 and for Visual Studio 2010. Trying to build on Win7 64bit with MSVisual Studio 2015 install.

_______________________________________________
Powered by Caution-Caution-www.kitware.com < Caution-http://Caution-Caution-www.kitware.com >  < Caution-Caution-http://www.kitware.com < Caution-http://www.kitware.com >  >

Visit other Kitware open-source projects at Caution-Caution-http://www.kitware.com/opensou < Caution-http://www.kitware.com/opensou > rce/opensource.html < Caution-Caution-http://www.kitware.com/opensource/opensource.html < Caution-http://www.kitware.com/opensource/opensource.html >  >

Please keep messages on-topic and check the ParaView Wiki at: Caution-Caution-http://paraview.org/Wiki/ParaV < Caution-http://paraview.org/Wiki/ParaV > iew < Caution-http://paraview.org/Wiki/ParaView < Caution-http://paraview.org/Wiki/ParaView >  >

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

Follow this link to subscribe/unsubscribe:
Caution-Caution-http://public.kitware.com/mail < Caution-http://public.kitware.com/mail > man/listinfo/paraview < Caution-Caution-http://public.kitware.com/mailman/listinfo/paraview < Caution-http://public.kitware.com/mailman/listinfo/paraview >  >

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160816/fa7e6a3b/attachment.html>