[Paraview] Building Paraview 5.2.1 on Windows (Visual Studio)

[Charles Boivin]

Utkarsh,

Thanks for your reply. 

I eventually managed to get something working, but I had to turn off shared libraries. Is there any reason why switching to shared libs would break things (aside from the obvious -- i.e. wrong DLL being picked up)? Does Qt have to be built with shared libs as well for this to work (Qt is built statically -- which I wouldn't think would be a problem)?

Thanks again,

Charles

-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: Tuesday, September 06, 2016 9:04 AM
To: Charles Boivin
Cc: paraview at paraview.org
Subject: Re: [Paraview] Building Paraview 5.2.1 on Windows (Visual Studio)

Are you building Debug ParaView with Release Qt? That won't work. If not, make sure your PATH is clean and is not bringing in other versions of Qt, ParaView. We build/test with VS2013 with no issues. I personally have built with VS2015 with no issues to report either -- although in both cases we use Ninja as the generator rather than the VS project files.

On Fri, Sep 2, 2016 at 10:43 AM, Charles Boivin <charles.boivin at mayahtt.com> wrote:
> Trying to build PV 5.2.1 on Windows 7. I have tried with both VS2015 
> and
> VS2013 and facing the same issue.
>
>
>
> Using Qt 4.8.6 (compiled in ‘Release’ mode – no debugging info)
>
>
>
> I point CMake to the Qt folder and easily get VS projects and 
> solutions. I can compile without any issue (had missing libs with one 
> project, but turned off VTK_BUILD_QT_DESIGNER_PLUGIN to avoid that issue for now).
>
>
>
> It builds and links fine. However, Paraview crashes when I try to run 
> it, without any kind of message whatsoever. Debugging in VS, I can see 
> that it gets to pqApplicationCore::createOutputWindow(), and it 
> crashes when it tries to execute the following line:
>
>
>
>   this->OutputWindow = new pqOutputWindow(0);
>
>
>
> (it doesn’t even reach the interior of 
> pqOutputWindow::pqOutputWindow() – looks like it crashes in the SuperClass maybe? Hard to say).
>
>
>
> Has someone ever encountered something similar? If not, is there any 
> way to get more info as to what might be going on here in order to fix 
> this in some way (maybe some log file)? As mentioned before, I tried 
> with both VS2013 and
> VS2015 (and corresponding builds of Qt 4.8.6), and I get the same problem.
>
>
>
> Thank you,
>
>
>
>
>
> Charles Boivin
>
>
> _______________________________________________
> 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
>