> 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
Hi Tom and Utkarsh,
I finally had time to take a closer look.
There is a corresponding merge-request
https://gitlab.kitware.com/vtk/vtk/merge_requests/2716
Cheers,
/mark
From: Tom Fahner
Sent: Monday, April 3, 2017 3:24:19 PM
To:
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
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
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
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
My work to compile paraview 5.3 is in progress but on the cluster (no GPU) I
fail to compile osmesa.
The downloaded tarball is mesa-17.0.1.tar.xz
The message is about invalid instructions:
CXXLD libswrAVX.la
CXXlibswrAVX2_la-swr_clear.lo
/tmp/ccDsR3FF.s: Assembler messages: