On MacOS. I had an old paraview in my path that I removed prior to this.
Perhaps that was it...changed too much now
On 8 December 2017 at 07:38, Utkarsh Ayachit
wrote:
> > I had previously configured paraview with ccmake and set build type to
> > Release and enabled Python.
> > Any idea how
> I had previously configured paraview with ccmake and set build type to
> Release and enabled Python.
> Any idea how that may impact this?
Not entirely sure how, unless some incorrect libraries are getting
loaded. Are you on Windows? Is your PATH sane?
Utkarsh
___
OK I have it working on my end.
I had previously configured paraview with ccmake and set build type to
Release and enabled Python.
Any idea how that may impact this?
Chris Marsh
PhD Candidate
chrismarsh.ca
121 Research Drive
University of Saskatchewan
On 7 December 2017 at 13:41, Chris Marsh w
Hi,
Thanks for trying this. Good call on the removal of the extra CMake stuff.
It was there because I started this filter before I knew about things like
setting ParaView_DIR and forgot to update this!
Interesting that works for you. I just rebuilt with the change to use
ParaView_DIR
(on the off
Hi, I have a filter that decodes a posix string from a pvd file into a
datetime format. This has worked well, however with the newest paraview I
get the error
ERROR: In
ParaView-v5.4.1/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line
672
vtkPVCompositeDataPipeline (0x60c0001ad9e0): Alg