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

[Aron Helser]

That definitely makes me think it was due to compatibility between the
compiler used for QT and the compiler used for ParaView - they need to be
the same. I'm surprised you got ParaView to link with the newer version of
VisualStudio - there may be a way to make that work which is eluding us.
Glad you are up and running,
Aron

On Thu, Apr 20, 2017 at 10:14 AM, Claire Guilbaud <claire.guilbaud at gmail.com
> wrote:

> unfortunately I don't have cmake in my path …
>
> I just re-install visual studio 2015, I didn't change anything in my
> environment (same qt5.6, same path). And now I'm able to launch paraview
> (in debug mode). That's great !
>
> I don't know which component put the environment in such a mess, but there
> is one (or more).
>
> Thank for your help
>
> Claire
>
>
>
> 2017-04-19 20:21 GMT-06:00 Utkarsh Ayachit <utkarsh.ayachit at kitware.com>:
>
>> > 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.
>>
>> That's bad. I'd stay away from putting CMake in the PATH, if that's the
>> case.
>>
>> > 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).
>>
>> Both are reasonably simple, depends on  your comfort level with
>> building Qt really. However, the issue you have with your current
>> build with Qt 5.6 seems to be only environment related. I'd suggest
>> cleaning your PATH (using dependency walker as a guide to remove
>> unnecessary/conflicting PATHs)  and you may be able to get your
>> existing build working without any issues.
>>
>> Utkarsh
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170420/fd72ad7f/attachment.html>