[Paraview] build pv5.3 on windows 10 with visual studio 15 2017

[Claire Guilbaud]

Thanks Utkarsh and Aron.

I already have the QT bin directory in my path, and effectively Qt has not
provided binaries for the latest VisualStudio.
Using Dependancy walker, some qt5 dll are in my qt bin dir but others
(those defined in cmake options like qt5widgets) are in the cmake bin dir.
Is it nolmal ? I'm currently using cmake 3.8 rc4.

So what's the simplest thing to have paraview running: compile qt from
sources with the patch on cmake file or go back to a previous version of
visual studio (it will be sad because I'm using the cmake capabilities of
the new version for other projects).

Thanks

Claire


2017-04-19 14:18 GMT-06:00 Aron Helser <aron.helser at kitware.com>:

> Claire,
> To launch ParaView that I build on Windows, I had to explicitly add the QT
> bin directory to my path, for example C:/Qt/Qt5.8.0/5.8/msvc2015_64/bin
> I'm not sure QT has provided binaries for the latest VisualStudio, have
> they? I'm using VS2015, which is VS 14.0, I believe. You may have to match
> your VS version to the one used to build the QT binaries.
> BTW, the fix for QT 5.8.0 is one line in one cmake file, so it's easy to
> fix after you install it.
> Regards,
> Aron
>
> On Wed, Apr 19, 2017 at 3:59 PM, Utkarsh Ayachit <
> utkarsh.ayachit at kitware.com> wrote:
>
>> I suspect your environment is messed up with mutliple Qt versions
>> showing up. Use Dependency Walker (http://www.dependencywalker.com/)
>> to make sure the dlls loaded are indeed the dlls you expect for Qt and
>> other external dependencies.
>>
>> On Wed, Apr 19, 2017 at 3:45 PM, Claire Guilbaud
>> <claire.guilbaud at gmail.com> wrote:
>> > Hi all,
>> >
>> > I'm struggling to launch paraview build on the last version of visual
>> studio
>> > (15.1 26407.3).
>> > I follow this documentation
>> > http://www.paraview.org/Wiki/ParaView:Build_And_Install.
>> >
>> > I use Qt 5, and just enable paraview python (miniconda2).
>> >
>> > I tried first to build with the last Qt 5 version (5.8.0), it failed
>> due to
>> > const expr error in qt (it's a known issue). So I switch to Qt 5.6.2.
>> >
>> > I follow the instructions from the documentation: set path variable,
>> modify
>> > environment variable in the configuration properties for paraview
>> project.
>> > The Debug generation failed: qt and paraview don't have the same
>> debugging
>> > level …
>> >
>> > The RefWithDebInfo generation succeeds. But I'm not able to launch
>> paraview
>> > (from visual studio - start without debugging or from file explorer).
>> > There are missing symbols in paraview.exe :
>> > ?toLatin1 at QString@@QEGBA?AVQByteArray@@XZ (same with toLower, toUtf8).
>> >
>> > Does anyone have an idea on how to fix it ?
>> >
>> > For information:
>> > - I don't use the cmake capabilities of visual studio: I use cmake-gui,
>> > configure, and generate.Then I open the paraview solution.
>> > - I try with Qt4 version, it failed. I reinstall Qt several times.
>> > - All my environment is in french
>> >
>> >
>> > Thanks for help.
>> >
>> > Claire
>> >
>> >
>> >
>> > _______________________________________________
>> > Powered by 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
>>
>> 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
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170419/85b20e09/attachment.html>