Re: [Paraview] paraview-superbuild Qt5 not found

[Ben Boeckel]

On Thu, Feb 08, 2018 at 15:46:27 +, Hermitte Luc (CS SI) wrote:
> I'm calling cmake with the following options?:
> cmake -Dqt5_enabled=On -DUSE_SYSTEM_qt5=On(/Off) 
> -DQt5_DIR=/path/to/qt/5.9.1/lib/cmake/Qt5 ..

The input setting is `ENABLE_qt5`. The `qt5_enabled` variable indicates
whether Qt5 is being built or not (either by request or because of a
dependency). It's value is set internally and the cache value is not
used.

--Ben
___
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:
https://paraview.org/mailman/listinfo/paraview

Re: [Paraview] python mismatch with superbuild on os x

[Ben Boeckel]

On Thu, Jan 25, 2018 at 11:40:40 +0100, Nicolas Vuaille wrote:
> I don't know if there is a proper fix but there is a CMake option to bypass
> this check:
>  set PYTHON_I_KNOW_WHAT_IM_DOING to true may solve the problem.

Indeed, this is the workaround. The problem is that we've had folks with
Homebrew Python where we end up finding `/usr/bin/python`, the library
from the SDK, and the headers from Homebrew. This, to say the least,
tends not to work out too well. However, you usually don't know until
your `pvpython` ends up busted, so instead we put the logic in the
superbuild. That escape hatch is there to avoid the check, but you
really should be using Python bits which agree on their version.

--Ben
___
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:
https://paraview.org/mailman/listinfo/paraview

Re: [Paraview] Parview Build Faulure on Mac OS 10.12.6

[Ben Boeckel]

On Thu, Dec 21, 2017 at 23:37:55 +, Beach, Timothy A. (GRC-LTE0)[Vantage 
Partners, LLC] wrote:
> Helo,  I’ve been working through some issues compiling on a new MAC
> but this one has me stuck.   I used CMAKE 3.10 to generate xcodebuild
> files for paraview 5.4. Any ideas?

Yep, Working on a fix right now actually :) . Progress can be seen here:

https://gitlab.kitware.com/paraview/paraview/merge_requests/2113

Using the Ninja generator is a workaround for right now.

--Ben
___
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:
https://paraview.org/mailman/listinfo/paraview

Re: [Paraview] Python shell, os.environ

[Ben Boeckel]

On Thu, Dec 21, 2017 at 15:14:01 +, Heiland, Randy wrote:
> Thanks Ben.  You’re right, of course. Moreover, my idea for having
> (non-admin) users install additional Python modules (e.g., scipy) into
> PV’s dir, is a not going to go well.

Well, if `sys.path` or `PYTHONPATH` can be pointed to it, it *should*
work (though the `numpy` in the package may not be configured properly
for `scipy`).

> Do we at least agree that if I ask users to start PV from the
> Terminal, PV’s Python will then pick up the user’s env vars?

It should, but ParaView doesn't do anything to stop it. If it doesn't
work, it's probably some Apple framework thing that needs to be told not
to do silly things.

--Ben
___
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:
https://paraview.org/mailman/listinfo/paraview

Re: [Paraview] Python shell, os.environ

[Ben Boeckel]

On Wed, Dec 20, 2017 at 22:50:50 +, Heiland, Randy wrote:
> Ah, I see ‘os’ has been hijacked by PV. But something like this seems
> to accomplish what I want, maybe…
> 
> Create a new module for PV:
> 
> /Applications/ParaView-5.4.1.app/Contents/Python$ more envs.py
> import os
> os.environ['PHYSICELL_DATA']=‘/fill_in_path’
> 
> and then in the PV Python shell, the os.environ will indeed contain
> this new env var.

This can't be part of the package though since if it is installed
globally, users may not have write access to the .app directory.

It seems the way to do this is along these lines (in short, Apple isn't
making what you want to do easy):


https://superuser.com/questions/476752/setting-environment-variables-in-os-x-for-gui-applications#541068

https://stackoverflow.com/questions/135688/setting-environment-variables-in-os-x/32405815#32405815

There seems to have been something like `~/.launchd.conf` at some point
and `~/.MacOSX/environment.plist` before that, but those has been
deprecated and no longer work.

--Ben
___
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:
https://paraview.org/mailman/listinfo/paraview

Re: [Paraview] cygwin installation

[Ben Boeckel]

On Tue, Dec 05, 2017 at 10:20:50 +1300, Zohar Levi via ParaView wrote:
> To be more specific, I'm building paraview 5.4.1 (gcc on cygwin), and I 
> get the following errors:
> 
> $ make
> [� 0%] Built target vtkWrappingTools
> [� 0%] Built target vtkWrapHierarchy
> [� 0%] Building CXX object 
> VTK/Utilities/KWSys/vtksys/CMakeFiles/vtksys.dir/EncodingCXX.cxx.o
> /c/prj-lib-cyg/paraview/VTK/Utilities/KWSys/vtksys/EncodingCXX.cxx: In 
> constructor 
> 'vtksys::Encoding::CommandLineArguments::CommandLineArguments(int, const 
> char
> * const*)':
> /c/prj-lib-cyg/paraview/VTK/Utilities/KWSys/vtksys/EncodingCXX.cxx:66:34: 
> error: 'strdup' was not declared in this scope

kwsys should certainly be supported on cygwin. It has 
included at the top. Brad?

> On 25/11/17 18:06, Zohar Levi wrote:
> > The doc says that cygwin isn't supported:
> >
> > https://www.paraview.org/Wiki/ParaView:Build_And_Install

It's not a platform we test on nor hold back releases for if it is
broken. It's on a "if it works, great." support basis. But, if there are
patches that fix it, we'll take a look at them.

--Ben
___
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

Re: [Paraview] OpenGL inside VMWare virtual machine

[Ben Boeckel]

On Wed, Nov 15, 2017 at 11:40:43 -0500, Ken Martin wrote:
> Basically there is a bug in Qt on windows where it refuses to see the 3.2
> context from Mesa because it is not a compatibility context.

On startup, Qt makes a context without a profile. Mesa gives it the best
compatibility profile it can: 2.0. Qt then interprets this as the
highest OpenGL version available and clamps all requests to this
version. The entire behavior is mystifying to me, but the issue has been
filed here:

https://bugreports.qt.io/browse/QTBUG-60742

--Ben
___
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

Re: [Paraview] [EXTERNAL] Re: pvbatch

[Ben Boeckel]

On Mon, Nov 13, 2017 at 22:04:19 +, Scott, W Alan wrote:
> I believe this is a change from the past.  Here is what I desire – how
> do I get it?
> 
> I want to run pv(pythonScript).  I want it to produce output.  I want
> it to run off screen, not showing on the console display or current
> display.  This is especially important on classified systems.  MPI is
> not available.
> 
> Not too long ago, my understanding was this was pvbatch.  pvpython
> used either the console display or current display as it’s rendering
> space.  This does not catch my needs.

Yeah, it seems I was mistaken. pvbatch is not conditional on MPI. If the
superbuild is built with mesa and Python and without MPI, pvbatch should
be there. I've filed an MR to fix the packaging/install step in the
superbuild:

https://gitlab.kitware.com/paraview/paraview-superbuild/merge_requests/388

--Ben
___
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

Re: [Paraview] pvbatch

[Ben Boeckel]

On Sun, Nov 12, 2017 at 22:42:29 +, Scott, W Alan wrote:
> What are the magic cmake switches, for superbuild, that are used to
> build a non MPI, Mesa version of pvbatch?  Where is this documented?

pvpython is the non-MPI version of pvbatch. The superbuild docs could
probably be improved here. Currently, the mention is:

ParaView supports multiple rendering engines including `egl`,
`mesa`, `osmesa`, and `qt5`. All of these are incompatible with each
other. If none of these are chosen, a UI-less ParaView will be built
(basically just `pvpython`). On Windows and macOS, only the `qt5`
rendering engine is available.

--Ben
___
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

Re: [Paraview] No module named paraview.simple on MacOs sierra

[Ben Boeckel]

On Fri, Nov 03, 2017 at 19:49:26 +, the lily wrote:
> export PYTHONPATH=$PYTHONPATH:/Applications/ParaView-5.4.1.app/Contents/bin

The modules should be in /path/to/.app/Contents/Python. Try:

export 
PYTHONPATH=$PYTHONPATH:/Applications/ParaView-5.4.1.app/Contents/Python

--Ben
___
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

Re: [Paraview] superbuild: fontconfig too old to compile (current does)

[Ben Boeckel]

On Sun, Oct 29, 2017 at 20:10:26 +0100, Fabian Wein wrote:
> I could not find the build error in the link.
> 
> The earliest version that builds for my gcc 7.2.1 is
> fontconfig-2.12.4, maybe this is a „compromise“?

Ah, sorry, I forgot to report back here. The issue is fixed on master.
It required an update to freetype as well.

--Ben
___
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

Re: [Paraview] superbuild: fontconfig too old to compile (current does)

[Ben Boeckel]

On Wed, Oct 25, 2017 at 13:35:51 +0200, Fabian Wein wrote:
> thank you! So the current master will have the upgrade within a few days?

It's not so simple :( . There's a build failure with older compilers:

https://open.cdash.org/viewNotes.php?buildid=5114526

--Ben
___
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

Re: [Paraview] superbuild: fontconfig too old to compile (current does)

[Ben Boeckel]

On Wed, Oct 25, 2017 at 13:35:51 +0200, Fabian Wein wrote:
> thank you! So the current master will have the upgrade within a few days?

Hopefully. I need to get `gperf` onto the build machine since it is a
new build dependency of fontconfig.

--Ben
___
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

Re: [Paraview] superbuild: fontconfig too old to compile (current does)

[Ben Boeckel]

On Tue, Oct 24, 2017 at 16:51:09 +0200, Fabian Wein wrote:
> fontconfig  2.12.1 does not compile with the error at the end of this 
> mail.
> 
> Building the current fontconfig 2.12.6 works for me, maybe the version
> could be upgraded?

I've pushed an MR for the common-superbuild here:

https://gitlab.kitware.com/paraview/common-superbuild/merge_requests/196

Followup paraview-superbuild fix here:

https://gitlab.kitware.com/paraview/paraview-superbuild/merge_requests/377

--Ben
___
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

Re: [Paraview] Problem compiling ParaView with NMake

[Ben Boeckel]

On Fri, Oct 20, 2017 at 08:40:34 -0400, Cory Quammen wrote:
> I strongly recommend using the Ninja generator for building ParaView with
> Superbuild on Windows. It will build much faster than if you use other
> build generators, and will take care of the particular problem you are
> seeing as -j is a Ninja option that controls the level of build parallelism.

Yes, the superbuild is currently only known to support Ninja on Windows.
Visual Studio is certainly out for various reasons, but NMake is
probably possible; patches would be welcome if NMake is required for
some reason. Some conditional should probably guard this section and not
do it for NMake:


https://gitlab.kitware.com/paraview/common-superbuild/blob/master/cmake/SuperbuildExternalProject.cmake#L94

but that may not be sufficient either.

--Ben
___
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

Re: [Paraview] Paraview 5.4.1 FTBS on Debian/Testing with gcc 7.2 when -DPARAVIEW_USE_VISITBRIDGE=ON

[Ben Boeckel]

On Thu, Oct 12, 2017 at 09:39:29 -0400, Ben Boeckel wrote:
> Hmm, my browser history says I searched for this back in July… looking
> around there finds:
> 
> https://gitlab.kitware.com/paraview/paraview/issues/17456
> 
> which seems to have dropped off our radar. Is the Vs reader necessary?
> If not, feel free to disable it, otherwise the reader will need fixed
> (it seems it has never worked though since it did this since its
> addition to visit upstream).

Further investigation shows that the code in the class isn't used at all
anyways. You can just remove the VsStaggeredField.C line from the
Vs/CMakeLists.txt file to fix the build error.

https://gitlab.kitware.com/paraview/visitbridge/merge_requests/45
https://gitlab.kitware.com/paraview/paraview/merge_requests/1965

--Ben
___
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

Re: [Paraview] Paraview 5.4.1 FTBS on Debian/Testing with gcc 7.2 when -DPARAVIEW_USE_VISITBRIDGE=ON

[Ben Boeckel]

On Thu, Oct 12, 2017 at 11:41:46 +0200, Christophe Trophime wrote:
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -g -O2 
> -fdebug-prefix-map=/build/paraview-5.4.1=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC -fPIC -std=c++11 -o 
> CMakeFiles/vtkPVVTKExtensionsRenderingPythonD.dir/vtkZlibImageCompressorPython.cxx.o
>  -c 
> /build/paraview-5.4.1/obj-x86_64-linux-gnu/VTK/Wrapping/Python/vtkZlibImageCompressorPython.cxx
>  
> /build/paraview-5.4.1/Utilities/VisItBridge/databases/readers/Vs/VsStaggeredField.C:
>  In constructor 'VsStaggeredField::VsStaggeredField(size_t)': 
> /build/paraview-5.4.1/Utilities/VisItBridge/databases/readers/Vs/VsStaggeredField.C:30:24:
>  error: 'class std::valarray' has no member named 'clear' 
> this->oriCellDimProd.clear(); 
> ^ 

Hmm, my browser history says I searched for this back in July… looking
around there finds:

https://gitlab.kitware.com/paraview/paraview/issues/17456

which seems to have dropped off our radar. Is the Vs reader necessary?
If not, feel free to disable it, otherwise the reader will need fixed
(it seems it has never worked though since it did this since its
addition to visit upstream).

> extra_flags += -Wno-dev \ 
> -DCMAKE_C_COMPILER=mpicc \ 
> -DCMAKE_CXX_COMPILER=mpic++ \ 

This probably isn't related, but this is not the typical way to use MPI
with CMake projects. They discover and use the information from the
wrappers themselves when they find MPI.

--Ben
___
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

Re: [Paraview] Segmentation fault in protobuf

[Ben Boeckel]

On Tue, Aug 15, 2017 at 17:59:47 +0300, u.utku.turunco...@be.itu.edu.tr wrote:
> I solved the problem and i am able to run the simulation code with
> Catalyst support by installing PV (5.4.0 rc4 and 5.3.0) with newer version
> of protobuf library (3.3.0) and compiling the model code with this version
> of PV (using gcc).
> 
> Now, the problem is that the code gives following warnings and do nothing
> with standard allinputsgridwriter.py script. Do you think that it is
> related with protobuf library. The same setup is working without any
> problem in an other system using Intel compiler.

It'd be better to try with one MPI process rather than…I count 10 to get
the error? Not sure what's up though, Andy?

> "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py",
> line 305, in CreateProducer
> grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0)
> grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0)
> if grid.IsA("vtkImageData") == True or \
>   File
> "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py",
> line 305, in CreateProducer
> AttributeError: 'NoneType' object has no attribute 'IsA'
>   File
> "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py",
> line 305, in CreateProducer
> if grid.IsA("vtkImageData") == True or \
> if grid.IsA("vtkImageData") == True or \
> AttributeError: 'NoneType' object has no attribute 'IsA'
> grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0)
>   File
> "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py",
> line 305, in CreateProducer
> grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0)
> if grid.IsA("vtkImageData") == True or \
> if grid.IsA("vtkImageData") == True or \
> AttributeError: 'NoneType' object has no attribute 'IsA'
> AttributeError: 'NoneType' object has no attribute 'IsA'
> if grid.IsA("vtkImageData") == True or \
> AttributeError: 'NoneType' object has no attribute 'IsA'
>   File
> "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py",
> line 305, in CreateProducer
> if grid.IsA("vtkImageData") == True or \
> AttributeError: 'NoneType' object has no attribute 'IsA'
> [PERFLOG] :: COPROC  2 0.01404021SEC.
>  Running COP Component: 2005-08-27T00:12:00 --> 2005-08-27T00:18:00 Time
> Step: 2 [ 720.00]
> ATM-TO-COP: redist mask [CROSS] to mask [CROSS]
> ATM-TO-COP: redist topo [CROSS] to topo [CROSS]
> AttributeError: 'NoneType' object has no attribute 'IsA'
> grid = adaptorinput.GetClientSideObject().GetOutputDataObject(0)
>   File
> "/home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/site-packages/paraview/coprocessing.py",
> line 305, in CreateProducer
> if grid.IsA("vtkImageData") == True or \

--Ben
___
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

Re: [Paraview] Segmentation fault in protobuf

[Ben Boeckel]

On Mon, Aug 14, 2017 at 20:45:41 +0300, u.utku.turunco...@be.itu.edu.tr wrote:
> Again thanks for your help. I tried to use protobuf 3.3.0 with PV 5.4.0rc4
> but i am getting following error
> 
>  CMake Warning at
>  
> /usr/local/software/spack/develop-290617/spack/opt/spack/linux-rhel7-x86_64/gcc-5.4.0/cmake-3.8.1-hvzxbkmal
>  ie677klawvpwyipv7giycyh/share/cmake-3.8/Modules/FindProtobuf.cmake:387
> (message):
>Protobuf compiler version doesn't match library version 3.3.0
>  Call Stack (most recent call first):
>VTK/CMake/vtkModuleMacros.cmake:888 (find_package)
>ThirdParty/protobuf/CMakeLists.txt:40 (vtk_module_third_party)
> 
> I have also version 2.5 in the system but I am getting lots of error (see
> attached log.txt) related with undefined references.

It looks like it's finding the compiler for 2.5 with the 3.3 library.
Set them both so that they match first.

--Ben
___
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

Re: [Paraview] Segmentation fault in protobuf

[Ben Boeckel]

On Mon, Aug 14, 2017 at 16:49:55 +0300, u.utku.turunco...@be.itu.edu.tr wrote:
> Thanks for your help. The server is Scientific Linux release 7.3
> (Nitrogen) and yes i install PV from source using NVIDIA EGL libraries. In
> this case, I set USE_X OFF and also QT_GUI OFF. I tried both Intel (2017)
> and gcc and result is same. I also installed PV 5.4.1RC4 and still same.
> It is very annoying, the same setup is working in an other system which
> has Centos and Intel 2014.

Hmm. Using an external Protobuf should work as long as it's new enough.
I also remember making it work with 3.0, but maybe that broke again?
What errors are you getting when trying to use an external protobuf?

--Ben
___
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

Re: [Paraview] Segmentation fault in protobuf

[Ben Boeckel]

On Sun, Aug 13, 2017 at 21:44:41 +0300, u.utku.turunco...@be.itu.edu.tr wrote:
> I am trying to install a code with support ParaView, Catalyst (version
> 5.3) to a new system. In this case, the code crash (seg. fault) at the
> beginning without giving any valuable hint about the problem. If I run the
> code under gdb I am getting following error messages,
> 
> ---Type  to continue, or q  to quit---
> Program received signal SIGSEGV, Segmentation fault.
> 0x7fffce45aee7 in _GLOBAL__sub_I_wire_format_lite.cc ()
>from
> /home/ext-dell-guest1/rds/hpc-work/progs/paraview-5.3.0/egl/lib/libprotobuf.so
> 
> It seems that the error triggered by paraview, protobuf component. I used
> both Intel and gcc compiler and both of them has same error. I also try to
> set VTK_USE_SYSTEM_PROTOBUF = ON but in this case I am getting bunch of
> error related with protobuf library. I also tried to compile my own

Care to paste these?

> protobuf library but ParaView complains about the version and I think that
> ParaView is compatible with version 2.5 but I installed 3.0. It is weird
> but I could able to run CFullExample without any problem. At this point I
> need your suggestion. Is there anybody faced similar problem? Do you think
> that upgrading 5.4 will help?

Are you on Ubuntu? What version? Did you compile this ParaView yourself?

--Ben
___
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

Re: [Paraview] Using python IDLE 3.6 with VTK and paraview.simple

[Ben Boeckel]

On Thu, Jul 20, 2017 at 13:03:12 +, Amine Aboufirass wrote:
> It appears that the module is defined but it has trouble with some of
> the VTK submodules. I tried to import VTK on its own but since the
> modules inside make use of the old print statement (no parentheses)
> there is not a way to do this free from error. How do I get this stuff
> to import properly?

The ParaView binaries only support Python2. If you want Python3 support,
you'll need to compile ParaView yourself (unfortunately, the superbuild
is not set up to do this yet, so anything in there you need will need to
be managed manually). We do test ParaView with Python3 though, so it
should work once you have a Python3-compatible build.

--Ben
___
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

Re: [Paraview] Paraview segfaults on CentOS 7.2

[Ben Boeckel]

On Fri, Jul 14, 2017 at 18:57:18 +, Martin Cuma wrote:
> Program received signal SIGSEGV, Segmentation fault.
> 0x in ?? ()

Run `bt` (short for `backtrace`) to get a trace. Though if this frame is
`NULL`, I suspect something went really badly somewhere :/ .

> So, as you can see, not much of use. We did do a source build of 5.3
> as well which also crashes (though I was not the one who did it), so,
> let me see if I can do something with that and get back to you.

OK.

--Ben
___
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

Re: [Paraview] Paraview segfaults on CentOS 7.2

[Ben Boeckel]

On Fri, Jul 14, 2017 at 12:11:38 -0600, Martin Cuma wrote:
> I tried the backtrace but it does not show anything useful since there are 
> no symbols in the binary. Do you have a binary build that includes symbols 
> that I could download and try to run?

Not on hand, sorry. The backtrace might help a bit since it would at
least show the libraries involved in the traceback.

--ben
___
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

Re: [Paraview] Paraview segfaults on CentOS 7.2

[Ben Boeckel]

On Thu, Jul 13, 2017 at 14:38:08 -0600, Martin Cuma wrote:
> I have been having trouble running the release binary of Paraview on 
> relatively stock CentOS 7.2 using
> the OpenGL. It segfaults before it loads up the GUI window.. If I start 
> Paraview with the --mesa option,
> it works fine.
> 
> This happens with the 2.3 and 2.4 Paraview binaries, i.e. 
> ParaView-5.3.0-Qt5-OpenGL2-MPI-Linux-64bit and
> ParaView-5.4.0-Qt5-OpenGL2-MPI-Linux-64bit, as well as the latest build,
> ParaView-5.4.0-233-g9952b9f-Qt5-MPI-Linux-64bit.
> 
> The same executables start fine both in CentOS6, and in an Ubuntu 16.10 
> Singularity container that runs
> on the CentOS7 host.
> 
> Before I dig further, I am wondering what is the experience on running 
> Paraview on CentOS7.

The binaries are built in a CentOS 6 container, but CentOS 7 should
still work. Is there any other output? Can you get a backtrace from
running paraview under gdb?

--Ben
___
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

Re: [Paraview] pvserver and mpi

[Ben Boeckel]

On Wed, Jul 12, 2017 at 19:23:20 +, Scott, W Alan wrote:
> I remember a thread from a few weeks ago that the current Linux
> distribution has built in MPI.  Is this correct?  Does this mean a
> user can use the Kitware binaries on a cluster, without rebuilding?

Theoretically, yes? Though I'd expect most clusters to have their own,
better-tuned MPI builds you'd want to prefer to a stock mpich build.

--Ben
___
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

Re: [Paraview] COMPILE AND RUN pvBatch with h5py support errors

[Ben Boeckel]

On Thu, Jul 13, 2017 at 14:54:11 +0200, Nabil Ghodbane wrote:
> dear experts,
> on a CentOS6.8 x86_64 node, I used the Superbuild to compile Paraview
> 5.3.0-1 with dev tool 4 (which provides gcc 5.3 )
> 
> As shown on the attached screen captures, In the CCMAKE configuration, I
> enabled Python with Matplot, Scipy, Numpy.
> 
> Once the compilation finished, I successfully added the h5py package
> but if I start pvBatch or pvpython, i can see some error messages about the
> hashlib module.
> 
> 
> *ValueError: unsupported hash type sha384ERROR   : code for hash sha512 was
> not found.*
> 
> This issue seems to be more a Python bug, than a Paraview issue. But maybe
> someone on this mailing list did experience the issue. In case, I will be
> grateful, if he or she could share his experience on how he/she solved this
> issue.

I think this is usually an issue with openssl headers not being
available when compiling Python. Does installing openssl-devel and
forcing a rebuild of Python (cd $builddir; rm -rf superbuild/python) fix
the issue?

--Ben
___
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

Re: [Paraview] pvpython vtkMPIController usage? rank is always 0

[Ben Boeckel]

On Tue, May 16, 2017 at 19:07:14 +0200, Ephraim Obermaier wrote:
> $ mpirun -n 2 pvpython test.py

I believe you want to use pvbatch for MPI-enabled Python scripts.

--Ben
___
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

Re: [Paraview] paraview-superbuild fails to buiild osmesa

[Ben Boeckel]

On Wed, May 03, 2017 at 16:59:18 +0200, Patrick Begou wrote:
> Even with v5.3.0-1  the problem remains. It seams related to the OSMESA 
> config 
> as a QT4 config on my desktop is successfull (same compilers and OpenMPI 
> version 
> but CentOS 6.9 instead of 6.7 on the cluster).
> 
> On the cluster frontend:
> 
> [begou@kareline paraview-superbuild]$ git describe
> v5.3.0-1

Hmm, could you send your CMakeCache.txt?

> > [ 27%] Linking CXX shared library 
> > ../../../lib/libvtkAcceleratorsVTKm-pv5.3.so
> > CMakeFiles/vtkAcceleratorsVTKm.dir/vtkmLevelOfDetail.cxx.o: In function 
> > `void 
> > vtkm::cont::DynamicArrayHandleBase > tovtkm::PointListInVTK>::CastAndCall(vtkm::cont::internal::ComputeRange
> >  
> > const&) const':
> > vtkmLevelOfDetail.cxx:(.text._ZNK4vtkm4cont22DynamicArrayHandleBaseINS_20TypeListTagFieldVec3EN6tovtkm14PointListInVTKEE11CastAndCallINS0_8internal12ComputeRangeEEEvRKT_[_ZNK4vtkm4cont22DynamicArrayHandleBaseINS_20TypeListTagFieldVec3EN6tovtkm14PointListInVTKEE11CastAndCallINS0_8internal12ComputeRangeEEEvRKT_]+0x160):
> >  
> > undefined reference to `vtkm::cont::ArrayHandle > vtkm::cont::StorageTagBasic> 
> > vtkm::cont::ArrayRangeCompute, 
> > tovtkm::vtkAOSArrayContainerTag> >(vtkm::cont::ArrayHandle > 3>, tovtkm::vtkAOSArrayContainerTag> const&, 
> > vtkm::cont::RuntimeDeviceTracker)'
> > vtkmLevelOfDetail.cxx:(.text._ZNK4vtkm4cont22DynamicArrayHandleBaseINS_20TypeListTagFieldVec3EN6tovtkm14PointListInVTKEE11CastAndCallINS0_8internal12ComputeRangeEEEvRKT_[_ZNK4vtkm4cont22DynamicArrayHandleBaseINS_20TypeListTagFieldVec3EN6tovtkm14PointListInVTKEE11CastAndCallINS0_8internal12ComputeRangeEEEvRKT_]+0x228):
> >  
> > undefined reference to `vtkm::cont::ArrayHandle > vtkm::cont::StorageTagBasic> 
> > vtkm::cont::ArrayRangeCompute, 
> > tovtkm::vtkAOSArrayContainerTag> 
> > >(vtkm::cont::ArrayHandle > 3>, tovtkm::vtkAOSArrayContainerTag> const&, 
> > vtkm::cont::RuntimeDeviceTracker)'
> > collect2: error: ld returned 1 exit status

Rob, thoughts?

--Ben
___
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

Re: [Paraview] paraview-superbuild fails to buiild osmesa

[Ben Boeckel]

On Wed, May 03, 2017 at 11:55:15 +0200, Patrick Begou wrote:
> My git commit is:
> 
> commit 8c380916ea13198b8912bef78971a71bba6d7147
> Merge: e75a492 84ebd63
> Author: Ben Boeckel <ben.boec...@kitware.com>
> Date:   Tue May 2 12:33:58 2017 +

Are you building 5.3.0? If so, please use the v5.3.0-1 tag. VTK-m has
since introduced API breaks against the VTK in 5.3.0.

--Ben
___
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

Re: [Paraview] Color legend not working properly

[Ben Boeckel]

On Thu, Apr 27, 2017 at 17:04:24 +, Lawson, Joel M. wrote:
> It worked! Thank you very much.
> Out of curiousity, what does the --mesa option do?

We build Mesa as part of our packages and place the required libraries
under `lib/paraview-5.3/mesa`. The `--mesa` flag just adds that
directory to `LD_LIBRARY_PATH` before executing the real ParaView
binary and potentially sets `GALLIUM_DRIVER` if you use one of the
`--mesa-*` flags:


https://gitlab.kitware.com/paraview/paraview/blob/master/CMake/pv-forward.c.in#L113

--ben
___
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

Re: [Paraview] problem freezing python

[Ben Boeckel]

On Fri, Apr 21, 2017 at 12:10:36 -0700, Burlen Loring wrote:
> That file lives in: lib/python2.7/config/config.c.in

OK, it looks like the freeze_paraview.py file can't find it. Could you
debug around line 250 to see what it is actually doing?

> -set(ENV{PYTHONPATH} "${PACKAGE_ROOT}")
> +set(ENV{PYTHONPATH} "${PACKAGE_ROOT} $ENV{PYTHONPATH}")

I don't see how this is valid (unless breaking the first entry in
`PYTHONPATH` is the goal); it should be separated by a colon.

> "/usr/common/software/ParaView/python/2.7.12/lib/python2.7/struct.py", 

What Python is this? Where did it come from?

> line 1, in 
>  from _struct import *
> ImportError: No module named _struct

Can you import it in the interpreter living in the above directory?

--Ben
___
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

Re: [Paraview] problem freezing python

[Ben Boeckel]

On Thu, Apr 20, 2017 at 14:44:47 -0700, Burlen Loring wrote:
> [100%] Freezing Python and ParaView Python packages and modules
> Removing 
> /usr/common/software/ParaView/builds/ParaView-5.3.0/Utilities/PythonInitializer/FrozenPython
> Error: could not find python lib directory
> Use 
> ``/usr/common/software/ParaView/builds/ParaView/ThirdParty/FreezePython/freeze/freeze_paraview.py
>  
> -h'' for help
> CMake Error at 
> /usr/common/software/ParaView/builds/ParaView/ThirdParty/FreezePython/vtkFreezePython.cmake:64
>  
> (message):
>freeze_paraview failed (2)

Looking at the code, it seems that there is not a `config.c.in` in your
`lib/python2.x` directory. It seems that it only searches `lib`. Are you
on a platform which uses `/usr/lib64`, `/usr/lib/x86_64-linux-gnu`, or
similar? Can you find a `config.c.in` near your Python installation?

--Ben
___
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

Re: [Paraview] paraview-superbuild fails to buiild osmesa

[Ben Boeckel]

On Thu, Apr 20, 2017 at 15:33:30 +0200, Patrick Begou wrote:
> This could be solved with disabling swr gallium driver and selecting only 
> swrast, even if my cpu is from intel family and provides AVX :
> 
> --with-gallium-drivers=swrast

You should be able to unset the `mesa_USE_SWR` option (it's advanced, so
you may need to toggle that flag to see it) to disable the `swr` driver.

--Ben
___
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

Re: [Paraview] paraview-superbuild hdf5 not found

[Ben Boeckel]

On Tue, Apr 18, 2017 at 13:23:36 -0400, Ben Boeckel wrote:
> We can fix this in the superbuild by setting that in `paraview.cmake`.
> I'll make that change.

https://gitlab.kitware.com/paraview/paraview-superbuild/merge_requests/308

--Ben
___
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

Re: [Paraview] paraview-superbuild hdf5 not found

[Ben Boeckel]

On Tue, Apr 18, 2017 at 18:15:00 +0200, Patrick Begou wrote:
> Something additionnal to set ?

This was fixed in VTK here:


https://gitlab.kitware.com/vtk/vtk/commit/641fc17e5e63f7ae5c3654f86a4ac97a33a2c63a

HDF5 can be found with targets or with library paths. The VTK module
system does not cope well with imported targets, so it needs to force
CMake to not use the target mode.

We can fix this in the superbuild by setting that in `paraview.cmake`.
I'll make that change.

--Ben
___
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

Re: [Paraview] Python not found in paraview-superbuild cmake

[Ben Boeckel]

On Tue, Apr 18, 2017 at 09:57:49 +0200, Patrick Begou wrote:
> I've posted this email last week but I did not reveive it via the list. May 
> be a 
> mistake of myself. I appologize if some one reveive it twice.
> 
> I'm trying to compile Paraview 5.3 on CentOS6 because I use a modified 
> OpenMPI 
> version witch is interfaced with my batch scheduler.
> I've started with :
> I've installed cmake-3.8.0 (in /opt) as CentOS cmake is only 2.8.12... it 
> works
> I've installed python 3.6 in /opt as CentOS6 python is only 2.6.6, and numpy, 
> matplotlib... it works

The superbuild is only tested with Python 2.7 at the moment; Python3 is
planned, but isn't something that I'd be able to get to until later in
the year at the earliest. There should be an SCL for CentOS which
contains python27:

https://wiki.centos.org/AdditionalResources/Repositories/SCL

which should work (we use it to build our binaries).

--Ben
___
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

Re: [Paraview] error when building ffmpeg

[Ben Boeckel]

On Thu, Apr 13, 2017 at 08:26:22 -0400, David E DeMarle wrote:
> Turn on paraview_FROM_SOURCE_DIR

Note that the `master` and `5.3.0` branches now have
`paraview_SOURCE_SELECTION` and it should be set to `source`.

--Ben
___
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

Re: [Paraview] [SuperBuild] Docker ?

[Ben Boeckel]

On Mon, Apr 10, 2017 at 16:18:21 +0200, Nabil Ghodbane wrote:
> it is not clear to me what you did. Did you build your own docker with
> Paraview on top of it and if this is the case could you share the
> Dockerfile you implemented to build the docker image?

The Dockerfile (and associated files) we use to build the image are
attached. It also does buildbot stuff rather than building ParaView
directly, but it has all the bits necessary to build the binaries we
make.

I'd have to extract the systemd configuration used to inject the
Xauthority and VNC bits into the container from the machine though if
you need that (if you're using Mesa for offscreen rendering, you
shouldn't need it).

--Ben


pvbinsdash-docker.tar.bz2
Description: BZip2 compressed data
___
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

Re: [Paraview] [SuperBuild] Docker ?

[Ben Boeckel]

On Fri, Apr 07, 2017 at 18:30:11 +0200, Florian Hoffmann wrote:
> does anybody out there would like to share some experience with a recent 
> ParaView Superbuild (>=version 5.2) with *Docker* ?
> 
> - Suggestions/recommendations for existing Dockerfiles ?
> 
> - Suggestions for settings like: Qt version, Mesa3D vs. OpenGL, ... ?

For building or running within a Docker image? We use a Docker image to
build it and to do some rudimentary testing (using a VNC server plumbed
in from the host).

--Ben
___
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

Re: [Paraview] Program received signal SIGFPE, Arithmetic exception.

[Ben Boeckel]

On Mon, Mar 20, 2017 at 11:31:28 -0700, Burlen Loring wrote:
> I had to apply to clang-format manually. it's up there now. changes were 
> minimal so I squashed them into the patch.

The fixes would have had to had been squashed in anyways; the robot
checks each commit individually.

> System has yet to acknowledge and re check. I assume it will
> eventually.

The new robot is silent on successful checks, so if it's silent, you're
(likely) good.

> Try as I may the clang-format script you guys are using doesn't work for 
> me.  here are the errors:
> Fedora 24:
> 
> smic:~/work/ParaView$Utilities/Scripts/clang-format.bash --amend
> YAML:4:24: error: invalid boolean
> AlignAfterOpenBracket: DontAlign
> ^
> Error reading /home/bloring/work/ParaView/.clang-format: Invalid
> argument
> 
> Maybe this is due to clang-format --version == 3.7? not sure but I won't 
> have time to re-install clang on this system, so I also tried on a newer 
> system.

Yeah, I think it requires 3.8. There is a new `Do: reformat` command
coming soon (this week ideally) to do the reformatting of your branch
for you since not everyone has a suitable clang-format just laying
around.

--Ben
___
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

Re: [Paraview] Program received signal SIGFPE, Arithmetic exception.

[Ben Boeckel]

On Fri, Mar 17, 2017 at 12:36:10 -0700, Burlen Loring wrote:
> fyi, https://gitlab.kitware.com/paraview/paraview/merge_requests/1476
> 
> it complains about clang-format, but it seems that the source file was 
> not formatted in that way to begin with.

When I enabled clang-format checking, I did a sweep of the repo with
clang-format.

I think the problem is that your headers aren't sorted:

#include 
#include 

--Ben
___
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

Re: [Paraview] ParaView 5.3.0 released

[Ben Boeckel]

On Tue, Mar 14, 2017 at 17:58:18 -0400, Cory Quammen wrote:
> The superbuild was tagged with v5.3.0 this morning.

That may be, but it seems you missed pushing it to the main repository
:) .

--Ben
___
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

Re: [Paraview] ParaView Web - module twisted.internet error

[Ben Boeckel]

On Tue, Mar 14, 2017 at 12:01:32 -0300, Rodnei Couto wrote:
> Python modules are different from 5.2 to 5.3
> 
> For example, inside* lib/python2.7/site-packages, *the version 5.2 has the
> modules *autobahn, zope and twisted*, and the version 5.3 does not.
> 
> I tried to copy the twisted and zope modules from version 5.2 to version
> 5.3, but a got others errors.
> 
> By now, I reverted to release 5.2 in production environment.

Looking at the superbuild, it appears that when ParaViewWeb got moved
from ParaView into its own repository, the flags that turned on pvweb
got removed and now there's nothing enabling those modules in ParaView's
build anymore. Do those packages need to be shipped with ParaView at all
now? If so, we'll need to add them to the superbuild specifically. If
not, some flag will need to be used to turn them on.

--Ben
___
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

Re: [Paraview] Issues viewing PV5.0.0 Filters/Alphabetical submenu

[Ben Boeckel]

On Tue, Feb 28, 2017 at 19:02:50 +0900, kenichiro yoshimi wrote:
> Has this issue been resolved?
> 
> I think that this might be caused by a bug in Qt 4.8.6:
> https://bugreports.qt.io/browse/QTBUG-54921

I think we came to the same conclusion. Windows has used Qt4 4.8.4 since
then to avoid the issue. However, as Cory said, Qt5 is now in use, so
the bug might have been avoided that way now.

--Ben
___
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

Re: [Paraview] Compiling Paraview 5.2 GCC 4.8 vtkOpenGLRenderWindow.cxx, line 641

[Ben Boeckel]

On Wed, Feb 22, 2017 at 09:37:47 +0100, Nabil Ghodbane wrote:
> - I am requesting USE_SYSTEM_hdf5 = OFF
> but looking as you suggested in superbuild/paraview/build/CMakeCache.txt, I
> can see that VTK_USE_SYSTEM_HDF5:BOOL=TRUE
> Shouldn't this be FALSE ?

>From ParaView's point of view, it is using a "system" HDF5, but it is
being provided by the superbuild itself. It looks like it is finding the
superbuild's HDF5, so something else is going wrong here :( .

> Find attached, the CMakeCache.txt, How can I workaround this issue?

It will need investigation. I'll try and get to it this week.

> Find below some additional informations:
> -  it works on Ubuntu (I tried my own Python), but I need to stick to an
> older glibc :(
> - on a Debian node, it fails if I use my local Python installation, while
> trying to compile numpy: "/usr/lib/python2.7/distutils/sysconfig.py"

More information is needed to help with this.

--Ben
___
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

Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?

[Ben Boeckel]

On Wed, Feb 22, 2017 at 13:10:04 +, Angelini, Richard C (Rick) CIV USARMY 
RDECOM ARL (US) wrote:
> Cory - so I did a “git pull” and “git submodule update” in my existing
> paraview-superbuild repository directory and that 5.3.0-RC1 information
> was not in the versions.cmake file. I did a clean “git clone” and I
> then received the correct files.I’m not a git expert - so I’m not
> sure why I had to do a clean “git clone”.   I thought I “git pull” should
> have done a proper update.  I must be missing something with my
> repository update commands …..

What is the output of the following commands:

  - git config branch.master.remote
  - git remote show $output_from_previous_command
  - git remote show origin

--Ben
___
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

Re: [Paraview] Compiling Paraview 5.2 GCC 4.8 vtkOpenGLRenderWindow.cxx, line 641

[Ben Boeckel]

On Tue, Feb 21, 2017 at 17:57:37 +0100, Nabil Ghodbane wrote:
> many thanks for the prompt reply. I should have hit the toggle option :).

It's fine, that bug is elusive and a pain to deal with.

> No i did not give it a try yet. I will try it and send feedback (I am using
> miniconda)
> Does this mean that using non embedded python is still experimental ?

Using a system Python is fine, it's just that the one in the superbuild
hasn't been bumped.

--Ben
___
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

Re: [Paraview] Compiling Paraview 5.2 GCC 4.8 vtkOpenGLRenderWindow.cxx, line 641

[Ben Boeckel]

> > On Tue, Feb 21, 2017 at 9:25 AM, Nabil Ghodbane
> >  wrote:
> > > OK many thanks,; I am trying to use the Superbuild now.
> > > I can see that it is downloading Python 2.7.11. Is there a particular
> > reason
> > > to use this version instead of the 2.7.12?

Haven't gotten around to updating to 2.7.12 (we're behind in updating
dependencies).

On Tue, Feb 21, 2017 at 16:18:48 +0100, Nabil Ghodbane wrote:
> ok thanks for the hint. I obviously missed this point. I will try again.
> I tried with the Python which is downloaded by the Paraview builder and i
> am hiting a new issue about libQtLucene.so
> Is this a known issue ?

There's a flag qt4_WORK_AROUND_BROKEN_ASSISTANT_BUILD you can set (it's
marked as advanced, so it is hidden by default). Details are here if
you're interested:


https://gitlab.kitware.com/paraview/common-superbuild/blob/master/projects/qt4.common.cmake#L5

--Ben
___
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

Re: [Paraview] PVSB 5.2: missing modules and plugins after "make install"

[Ben Boeckel]

On Fri, Feb 17, 2017 at 13:17:37 +, Michel Rasquin wrote:
> Has anybody already tested successfully PVSB 5.2 from the install
> directory without loosing plugins and other module down the road?

Oh, running from the install directory? That's not really fully
supported. The reason is that we have 3 places ParaView ends up during
the superbuild:

  - the build tree
  - the install tree
  - the package

Getting it to work in all three on all platforms is not really feasible,
so we prioritize them as:

  - the package (because this has to work)
  - the build tree (so that tests can be run)
  - the install tree

It is best to make the package (ctest -R cpack-paraview-TGZ) and then
either run from _CPack_Packages/... or extract the generated tarball
somewhere else and run that. There is also `make install`, which should
also work just fine (it basically just does the packaging step to a
given directory and then doesn't actually make the package).

--Ben
___
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

Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?

[Ben Boeckel]

On Fri, Feb 17, 2017 at 12:43:17 +, Angelini, Richard C (Rick) CIV USARMY 
RDECOM ARL (US) wrote:
> Cmake was complaining about CMAKE_OSX_SDK not being set …
> I’m not sure if I needed to set both variables, but I recalled seeing this
> in a mail thread, so I just set it!   8-)

Ah, then you just set it to what you had. That's fine :) . I just saw
"10.9" and assumed you were setting it to an older version.

--Ben
___
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

Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?

[Ben Boeckel]

On Thu, Feb 16, 2017 at 16:53:55 +, Angelini, Richard C (Rick) CIV USARMY 
RDECOM ARL (US) wrote:
> Fabian - thank you - that was enough of a hint to get me over the hump.
> Switched my build to qt5 AND based on some information from a previous
> email thread, I added the following to my CMAKE command:
> 
> -DCMAKE_OSX_SDK="macosx10.9" \
> -DCMAKE_OSX_SYSROOT="/Applications/Xcode.app/Contents/Developer/Platforms/M
> acOSX.platform/Developer/SDKs/MacOSX10.9.sdk"

That shouldn't be necessary for Qt5 (though if it works, that's great).

--Ben
___
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

Re: [Paraview] Superbuild repo change?

[Ben Boeckel]

On Wed, Feb 15, 2017 at 13:50:13 +, Angelini, Richard C (Rick) CIV USARMY 
RDECOM ARL (US) wrote:
> I did a fresh pull of the ParaView superbuild repository, and now I can’t do
> a clean build of PV 5.2.0 on my Mac (OSX 10.9.5).
> 
> First, I had to remove the entries for “qt” and “scipy" in the
> CMakeLists.txt:

You need to run `git submodule update` to update the common-superbuild
bits.

> After removing those entries, the cmake completes and the build starts and
> passes out in qt4. 
> I’m not sure why it’s complaining about OS X 10.7 or later?)

What version of Xcode are you using?

--Ben
___
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

Re: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download

[Ben Boeckel]

On Tue, Feb 14, 2017 at 10:04:50 -0500, Utkarsh Ayachit wrote:
> Chuck, is this a CMake version related issue? Ufuk, which cmake
> version are you using?

It likely is. VTK is now using CMake's C++11 support detection and older
versions of CMake do not have the required bits for Intel 16. These
appear to have been introduced in 3.8.0, but may have been in 3.7.0 (I'm
not completely sure).

--Ben
___
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

Re: [Paraview] (no subject)

[Ben Boeckel]

On Mon, Feb 13, 2017 at 14:16:03 -0500, Bishwajit Dutta wrote:
> http://midas3.kitware.com/midas/api/rest?method=midas.bitstream.download=b10bd3f7136ef809f1df7ad5c94c553f=MD5
> ("Couldn't connect to server")
> 
> http://www.paraview.org/files/ExternalData/MD5/b10bd3f7136ef809f1df7ad5c94c553f
> ("Couldn't connect to server")

This indicates that you can't contact the host. Does it work if you
change the URLs to use `https` in CMake/vtkExternalData.cmake?

> Also I wanted to run a paraview python script with CPU acceleration. Will
> this compilation generate
> pvpython and can I pass it  --mesa-llvm for running the script (I assume by
> default it will use GPU acceleration as I have NVIDIA GPU on my system)?

5.0.0 did not have support for that flag (I think). That flag also
assumes certain things about the way ParaView was built (namely that
Mesa is available under `lib/paraview-5.x/mesa`).

--Ben
___
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

Re: [Paraview] PVSB 5.2: missing modules and plugins after "make install"

[Ben Boeckel]

On Sat, Feb 11, 2017 at 17:48:27 -0500, Cory Quammen wrote:
> Will updating to the current superbuild master address the missing
> plugins issue Michel is seeing? It looks like there have been some
> minor changes on plugin handling in linux since
> 4ec37480a6f1ad39c9aa3168c2f0e6a1b0147b16.

Yes, it's possible. If you look at the output of the packaging step,
there is probably some set of system libraries being pulled into the
package which should not be there.

--Ben
___
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

Re: [Paraview] Query on ccmake for building Paraview

[Ben Boeckel]

On Wed, Feb 08, 2017 at 02:10:27 -0500, Bishwajit Dutta wrote:
> I had the below query. Thanks to pls help out.
> 
> I wanted to build Paraview 4.0.1 source on my 64 bit ubuntu system. I need
> to
> configure options to build with mesa and I read that this is to be done
> with ccmake.
> 
> Now I compiled cmake 2.8.8 and 3.7.0 but I cannot see any ccmake getting
> compiled in bin folder.
> Thanks for letting me know a proper version of cmake which has ccmake.

You need to set BUILD_CursesDialog=ON.

--Ben
___
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

Re: [Paraview] Windows plugin compatibility with Paraview

[Ben Boeckel]

On Wed, Jan 25, 2017 at 11:08:00 -0600, Chris Marsh wrote:
> I would like to build and make available a pre-compiled windows binary for
> a filter I have developed. I would like to avoid the (windows) user having
> to compile the filter as well as paraview. Therefore I am wondering what
> compiler is used to produce the official Paraview builds so-as to avoid ABI
> issues with my pre-compiled .dll. Is there anything else I need to be aware
> of?

We use Visual Studio 2013 Community to build the binaries from the
superbuild:

https://gitlab.kitware.com/paraview/paraview-superbuild

If you want to be compatible with the paraview.org downloads, there are
two packages built, one with MPI and one without. You can see the
command lines used to build the superbuild here:

https://open.cdash.org/viewConfigure.php?buildid=4740356 (no MPI)
https://open.cdash.org/viewConfigure.php?buildid=4740247 (with MPI)

Only MSMPI is supported (but cannot be redistributed, so we rely on it
being available on the target machine already).

If you want to build your own package with the plugin pre-packaged, you
can use the documentation here:

https://gitlab.kitware.com/paraview/paraview-superbuild/#external-plugins

to support building your plugin and then extract it from the install/
tree and distribute it to your users. We currently do not ship an SDK
for Windows, so it is easiest to build 5.2.0 locally and then
redistribute your plugin (though building your own package is also
easy). Note that your plugin is built as part of ParaView in this
configuration, so there is no need to do a `find_package(ParaView)`. You
can see how the PointSpritePlugin deals with this here:


https://gitlab.kitware.com/paraview/paraview/blob/4897676d1cdc764f933a9fac22149dadf6dd5cb2/Plugins/PointSprite/CMakeLists.txt#L14

--Ben
___
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

Re: [Paraview] packing superbuild 5.2 fails on openSUSE due to ldconfig

[Ben Boeckel]

On Tue, Jan 17, 2017 at 11:19:40 +0100, Fabian Wein wrote:
> ldconfig is on openSUSE and Ubuntu /sbin/ldconfig but sbin in on 
> openSUSE not in the user path. For me a link in $HOME/bin helped but 
> maybe using the full path
> would work on all unix systems?!

I guess we'll go with the full path. PR is making its way to the
superbuild via:

https://gitlab.kitware.com/paraview/common-superbuild/merge_requests/136

Thanks,

--Ben
___
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

Re: [Paraview] Problem reading a numpy NPZ file in ParaView 5.2.0 on Windows

[Ben Boeckel]

On Fri, Jan 06, 2017 at 14:36:53 -0500, Cory Quammen wrote:
> Thanks for the report. I looked into this and I think I know what is going on.
> 
> In ParaView 5.2.0, we reduced the number of Python modules that
> shipped with the ParaView binaries. One of the modules not included
> was the "compiler" module. Now, Numpy checks to see if the "compiler"
> module is available, and if it isn't, uses the "ast" module instead to
> parse some file header data. However, Numpy doesn't correctly handle
> the results produced by using ast.parse to parse the header data.
> 
> ParaView 5.1.2 shipped with the "compiler" module, which is why it
> worked for you in the past. We'll have to add it back for the next
> release. I've added an issue to track here:
> 
> https://gitlab.kitware.com/paraview/paraview-superbuild/issues/43

Sorry about that, I missed the packages (foo/__init__.py) from the
standard distribution. The nightlies will have it next week at the
latest.

--Ben
___
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

Re: [Paraview] ParaViewConfig.cmake created too late with ENABLE_paraviewpluginsexternal

[Ben Boeckel]

On Thu, Jan 05, 2017 at 13:07:32 +0100, Fabian Wein wrote:
> I think there is still an issue building plugins via 
> -DENABLE_paraviewpluginsexternal:BOOL=ON when building 
> paraview-superbuild.
> 
> cmake ../paraview-superbuild -DCMAKE_BUILD_TYPE:STRING=Release 
> -DBUILD_TESTING=OFF -DENABLE_cxx11=ON -DENABLE_qt5=ON 
> -DENABLE_boost:BOOL=ON -DENABLE_hdf5:BOOL=ON -DENABLE_zlib:BOOL=ON 
> -DENABLE_png:BOOL=ON 
> -Dsuperbuild_download_location=$HOME/code/cfsdepscache/paraview 
> -DENABLE_paraviewpluginsexternal:BOOL=ON 
> -Dparaview_PLUGINS_EXTERNAL:STRING=CFSReader 
> -Dparaview_PLUGIN_CFSReader_PATH:PATH=$METABUILD/../plugins/CFSReader
> 
> results in the error
> 
> CMake Error at ~/code/cfs_paraview/plugins/CFSReader/CMakeLists.txt:43 
> (FIND_PACKAGE):
>By not providing "FindParaView.cmake" in CMAKE_MODULE_PATH this 
> project has
>asked CMake to find a package configuration file provided by 
> "ParaView",
>but CMake did not find one.
> 
>Could not find a package configuration file provided by "ParaView" 
> with any
>of the following names:
> 
>  ParaViewConfig.cmake
>  paraview-config.cmake
> 
>Add the installation prefix of "ParaView" to CMAKE_PREFIX_PATH or set
>"ParaView_DIR" to a directory containing one of the above files.  If
>"ParaView" provides a separate development package or SDK, be sure 
> it has
>been installed.
> 
> And indeed ParaViewConfig.cmake does not exist yet in 
> ParaView_DIR=~/code/cfs_paraview/metabuild/build/superbuild/paraview/build
> 
> It works when I do the cmake ../paraview-superbuild first without 
> -DENABLE_paraviewpluginsexternal:BOOL=ON ...
> and then a second time with (as shown above).
> 
> However, we want to build the paraview-superbuild with our plugin 
> automatically (e.g. in our nightly builds) with an own cmake project 
> where paraview-superbuild is an external project.
> 
> Do I something wrong? Is this a bug? Any hint on how to do a workaround?

The external plugins bit builds the plugin as part of ParaView's build,
not after it is built. You can detect this the same way the PointSprite
plugin in ParaView itself does so:

if (ParaView_SOURCE_DIR)
  # Within the source tree already.
else ()
  find_package(ParaView REQUIRED)
  # ...
endif ()
___
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

Re: [Paraview] Question on compiling external plugins with 5.2

[Ben Boeckel]

On Mon, Jan 02, 2017 at 21:36:51 +0100, Fabian Wein wrote:
> Then I do something wrong:
> 
> cmake ../paraview-superbuild -DCMAKE_BUILD_TYPE:STRING=Release 
> -DBUILD_TESTING=OFF -DENABLE_cxx11=ON -DENABLE_qt5=ON -DENABLE_boost:BOOL=ON 
> -DENABLE_hdf5:BOOL=ON -DENABLE_zlib:BOOL=ON -DENABLE_png:BOOL=ON 
> -Dsuperbuild_download_location=$HOME/code/cfsdepscache/paraview 
> -DCMAKE_OSX_SDK=macosx10.12 -DENABLE_paraviewexternalplugins:BOOL=ON 
> -Dparaview_PLUGINS_EXTERNAL:STRING=CFSReader 
> -Dparaview_PLUGIN_CFSReader_PATH:PATH=$METABUILD/../plugins/CFSReader
> 
> …
> CMake Warning:
>   Manually-specified variables were not used by the project:
> 
> ENABLE_paraviewexternalplugins
> …
> 
> I should have written, that I tried some variants before. 

Oops, something even more fundumental was wrong; it is actually:

ENABLE_paraviewpluginsexternal

MR updated. Thanks,

--Ben
___
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

Re: [Paraview] Question on compiling external plugins with 5.2

[Ben Boeckel]

On Fri, Dec 30, 2016 at 23:48:52 +0100, Fabian Wein wrote:
> • enable_paraviewexternalplugins:BOOL=ON: Enables building using external 
> plugins.

Sorry, that should be ENABLE_paraviewexternalplugins. PR pushed:

https://gitlab.kitware.com/paraview/paraview-superbuild/merge_requests/253

--Ben
___
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

Re: [Paraview] git question on paraview-superbuild master

[Ben Boeckel]

On Thu, Dec 22, 2016 at 21:10:04 +0100, Fabian Wein wrote:
> What is the relationship of paraview-superbuild and common-superbuild?

The common superbuild is updated via merge requests in
paraview-superbuild; it does not track master automatically. I'll make a
merge request here today.

You can update locally by going into the superbuild/ directory and
checkout out `origin/master`.

--Ben
___
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

Re: [Paraview] Multiprocessing doesn't work on windows for pvpython

[Ben Boeckel]

On Fri, Dec 09, 2016 at 01:23:29 -0500, Luo Han wrote:
> I have a script to post processing data. It needs pvpython to call it. The
> script import multiprocessing module. But when I import the package, it
> shows:

Yeah, it isn't a full Python; I had tried stripping it down, but that
turns out to have been a bad decision. 5.2.1 will have a complete
Python.

--Ben
___
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

[Paraview] [ANN] Dropping 32bit binaries for 5.3 and beyond

[Ben Boeckel]

Hi,

We're planning on dropping 32bit binaries (currently only provided on
Windows) for post-5.2 development.

Any objections?

--Ben
___
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

Re: [Paraview] ParaView 5.2 Release Candidate 2 available for download

[Ben Boeckel]

On Fri, Oct 21, 2016 at 10:31:00 -0400, David Thompson wrote:
> Your attempt to set CMAKE_OSX_SDK=10.12 was probably on the superbuild
> project, and it is not passed to the Qt subproject as QT_MAC_SDK. Try
> passing the proper value to CMAKE_OSX_SDK (i.e., the full path which
> is usually
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk)
> and see if the superbuild properly determines the value of
> QMAKE_MAC_SDK from that.

No, CMAKE_OSX_SDK is the name of the SDK. The path is CMAKE_OSX_SYSROOT.

--Ben
___
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

Re: [Paraview] ParaView 5.2 Release Candidate 2 available for download

[Ben Boeckel]

On Thu, Oct 20, 2016 at 15:13:51 +0300, Gena Bug via ParaView wrote:
> Now, with RC2, fontconfig warns me about blank section:
> 
> Fontconfig warning: line 160: blank doesn't take any effect anymore. 
> please remove it from your fonts.conf

We're now using a newer fontconfig, so the fontconfig may be newer than
your system, so this is just fontconfig being more pedantic than your
distro. Looking at fontconfig, there's no environment variable to
suppress these warnings.

> However, that all -- no more new folder "fontconfig" in the running 
> directory. Thank you, that was really annoying!
> 
> Also, lib-dynload is still missing in the lib/python2.7

Ah, the superbuild didn't get bumped for that fix yet. I'll do that
today.

--Ben
___
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

Re: [Paraview] ParaView 5.2 Release Candidate 2 available for download

[Ben Boeckel]

On Thu, Oct 20, 2016 at 16:03:05 +0200, Fabian Wein wrote:
> Are you interested in superbuild tests, too? Or do you want to skip
> that issue for the time 5.2 is released?

We're interested :) .

> On macOS 10.12 Sierra I have problems building qt5:

Hmm, we haven't done 10.12 yet; upgrading it usually breaks things :( .

> superbuild fails with the output below but building qt5 manually seems
> to work (at least it builds for a longer time up to now)

We don't build the Qt5 bits yet for ParaView, but it is used with other
projects. (Though even for Qt4 is built once and reused to avoid an
extra 45+ minutes per build.)

Please open an issue here:

https://gitlab.kitware.com/paraview/common-superbuild

to help track this.

> On Linux (openSUSE tumbleweed with gcc 6.2.1) hdf5 fails the rest is still 
> building …

Could you post a bug at the same place for this? I use 6.2.1 from Fedora
and HDF5 is fine here. More details would be nice too.

Thanks,

--Ben
___
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

Re: [Paraview] ParaView 5.2 Release Candidate 1 available for download

[Ben Boeckel]

On Wed, Oct 12, 2016 at 10:42:43 -0400, Ben Boeckel wrote:
> Oh, you're compiling 5.1.2 with the new superbuild; yes, that'd have the
> same thing. I'll look to see if there's a way to get FONTCONFIG_PATH
> default to the right place. Thanks for the hint.

Looks like updating to the latest fontconfig release solves the problem
with both the config file warnings and the cache files being dropped in
the wrong place; rc2 should be better.

--Ben
___
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

Re: [Paraview] ParaView 5.2 Release Candidate 1 available for download

[Ben Boeckel]

On Thu, Oct 13, 2016 at 13:57:58 +0300, Gena Bug via ParaView wrote:
> I'm slightly confused with background color for the screenshots when 
> trying to override palette. If I set Background to a Single color in the 
> Properties tab (gray by default) then nothing can change it -- 
> background will always be gray on the screenshots. If I set Gradient for 
> the Background then:
> 1. current palette: works as expected
> 2. black bg: works
> 3. default bg: don't know what's default but it looks like 1... OK
> 4. gradient bg: like 1.
> 5. gray bg: like 1.
> 6. print bg: it looks like Color 1 is set to white in Background settings
> 7. white bg: same as 6.
> 
> So now there is no way to set white background for the screenshots 
> (previously it was possible when Single Color background was used but 
> not Gradient).

Not sure if you're aware, but there is also the option to write out a
screenshot where the background is transparent using an alpha channel.
It also takes into account translucent geometry. It's under the Advanced
settings in the General tab in Settings (search will also find it).

--Ben
___
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

Re: [Paraview] ParaView 5.2 Release Candidate 1 available for download

[Ben Boeckel]

On Wed, Oct 12, 2016 at 16:05:28 +0200, Albina, Frank wrote:
> Issue being configuration messages.

Oh, you're compiling 5.1.2 with the new superbuild; yes, that'd have the
same thing. I'll look to see if there's a way to get FONTCONFIG_PATH
default to the right place. Thanks for the hint.

--Ben
___
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

Re: [Paraview] ParaView 5.2 Release Candidate 1 available for download

[Ben Boeckel]

On Wed, Oct 12, 2016 at 15:36:24 +0200, Albina, Frank wrote:
> I have been having similar issue when compiling ParaView 5.1.2 from
> source with QT4 support, which depends on the fontconfig project. 
> I could get rid of it by setting FONTCONFIG_PATH to /etc/fonts on my
> system.

"Issue" being the crappy font rendering or the configuration messages?

--Ben
___
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

Re: [Paraview] ParaView 5.2 Release Candidate 1 available for download

[Ben Boeckel]

On Tue, Oct 11, 2016 at 23:30:16 +0300, Gena Bug via ParaView wrote:
> I've just tried the 5.2rc and noticed this in the console:
> 
> $ Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 
> 72: non-double matrix element
> Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 
> 72: non-double matrix element
> Fontconfig warning: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 
> 80: saw unknown, expected number

This is due to the way we now package fontconfig. We used to have it
just use the (non-existent) config files from the package, so you got
crappy fonts usually. Now, we use the system configuration and you
should get the same fonts as the system, but it seems that we probably
need to update our fontconfig. Other than that, the messages are
harmless as far as we've been able to tell.

> And a fontconfig folder is created in the run directory with a bunch of 
> cache-files.

Yeah, not sure how to fix this; I had tried putting them into /var/cache
like the system, but it seems that that flag is insufficient :( .

--Ben
___
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

Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR.

[Ben Boeckel]

On Wed, Sep 28, 2016 at 17:54:53 +0200, Albina, Frank wrote:
> I had to recompile from scractch, which took a bit of time. Actually,
> the GNU compiler requirement is coming from building the OSPRAY
> project, as shown hereafter:
> 
> [...]
> CMake Error at cmake/gcc.cmake:48 (MESSAGE):
>   GCC version 4.8.0 or greater is required to build OSPRay.
> Call Stack (most recent call first):
>   cmake/ospray.cmake:97 (INCLUDE)
>   common/CMakeLists.txt:17 (CONFIGURE_OSPRAY)

This makes sense; ospray requires C++11 support for which GCC 4.8 was
the first release with viable support (4.7.x had some, but not enough).

> If the new superbuild has support for building mesa 12.0.3, I would be
> interested in trying this out. Are there any instructions I can follow
> to do that?

It's on my list to improve docs here. I'd welcome feedback where the
existing docs are deficient (they're in README.md on the master branch)
so I can improve those parts.

> My intention is to compile paraview without GUI to run it in batch on
> our cluster. This is the main reason why I am using a specific test
> suite to check the performance of mesa-llvm vs. mesa-swr vs. GPU. At
> the moment, on CPUs supporting AVX2 instruction set, mesa-swr shows a
> very decent performance. Hence, my interest also to try out the latest
> mesa 12.0.3 version, which I have downloaded today and started
> compiling. In this regard, do you have any configuration options you
> can share for use in offscreen mode? If this is handled already by the
> latest superbuild version, then please disregard the questions above.

Chuck (Cc'd) does this quite a bit. There are scripts he has committed
which are used to build for specific platforms which you may be able to
start using, but he's the best source of instructions for those.

--Ben
___
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

Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR.

[Ben Boeckel]

On Wed, Sep 28, 2016 at 10:06:15 +0200, Albina, Frank wrote:
> In this regard, I would like to point out a few things I have found
> while performing the build process on the aforementioned Linux
> distribution. Note that my incentive is to help improve the ParaView
> software suite as well as helping others to be able to build and use
> the software.

Thanks for the feedback. Responses inline.

> 2. You definitely need cmake at least cmake v3.5 (and not v3.3) to
> compile ParaView from SuperBuild.

Ah, ParaView is 3.3, but the superbuild is 3.5. As a heads up, the new
superbuild which will be used for ParaView 5.2 will require at least
3.6.1.

> 3. You need a GNU compiler v4.8.0 or above to build. My Linux
> distribution comes with gcc v4.7.2. Fortunately, I had gcc v4.9.2
> installed with which I could perform a successful build.

What subproject required this?

> 4. Dependencies such libsz, libxml, libbzip2 are built and stored
> in the /install/lib64 directory on my platform. This creates
> linking issues which I could partly resolve by pushing the missing
> libraries into the /install/lib directory. This is not ideal
> but could be solved by forcing the lib directory to
> /install/lib using the --libdir option.

Hrm. I'm on Fedora (which also uses lib64) and though I had gotten all
the lib64-isms out of the superbuild. Maybe I had missed some before
5.1.2 (the superbuild now uses common infrastructure shared between
other similar superbuilds).

> 5. The vistrails plugin cannot be built. After 3 attempts, the git
> clone from https://kwgitlab.kitware.com/paraview/vistrails.git fails.
> Either the link is wrong or the server is unreachable.

vistrails should be hidden behind a "USE_NONFREE_COMPONENTS" flag.
vistrails (and acusolve) are not FOSS, so their git repos are on our
internal server.

> 6. The mesa libraries are pre-compiled and downloaded to
> /mesa-downloads. They are unpacked and moved into the ParaView
> installation directory when performing “make install”. These libraries
> are dating from May 3rd, hence prior to the release of Mesa 12.0 which
> embeds OpenSWR as a build option. Is there a way to build new libGL.so
> and libOSMesa.so libraries based on Mesa3D v12.0 and replace the
> currently pre-compiled binaries? If so,what are the typical
> configuration options used in this case?

The new superbuild has support for building mesa 12.0.3 as part of the
build. We used prebuilt binaries before because our build machine was
Debian 6 which was not easily capable of compiling the LLVM -> Mesa
chain without a self-compiled compiler and such, so it was built once
and that was it. I think it did contain SWR since it was a git snapshot.
Utkarsh?

--Ben
___
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

Re: [Paraview] [vtk-developers] Which Compilers and Operating Systems to you require for VTK and / ParaView?

[Ben Boeckel]

On Mon, Sep 26, 2016 at 14:01:38 -0400, Chuck Atkins wrote:
> Just as a follow-up, I will be leaving this survey open all week and stop
> accepting responses on Friday, October 30.

I assume you mean September 30?

--Ben
___
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

Re: [Paraview] [vtkusers] Testing ITK/VTK/PV contributions with (kitware) Gitlab-CI

[Ben Boeckel]

On Thu, Sep 08, 2016 at 12:36:40 +0200, Grothausmann, Roman Dr. wrote:
> Just getting to know Gitlab-CI, I am wondering whether it is possible to test 
> contributions to ITK/VTK/PV with Gitlab-CI from gitlab.com or 
> gitlab.kitware.com. As far as I understand, this basically needs runners, in 
> this case specific to ITK/VTK/PV. Since kitware has done CI even before the 
> use 
> of gitlab, I wonder if the former testing environments are available for use 
> with Gitlab-CI and if so how to use them.

We're (VTK and ParaView) using buildbot to manage our testing. The
number of settings we test across machines is hard to specify in YAML
files (machines also have different settings based on what you're
testing, e.g., load up a different compiler or Qt4 or Qt5 and the paths
they live in, etc.). We're working on improving the hardware situation
buildbot is currently in; things should be getting better over the next
few months on that front.

> For example, none of my contributions to the ITK/VTK/Midas Journals got into 
> the 
> testing phase even though marked for testing during submission. So a 
> possibility 
> to use Gitlab-CI to test the compilation and to run the project test would be 
> really great, especially for continued development and testing on other OSs.
> Specifically, for e.g. testing my FacetAnalyser contribution 
> (http://www.midasjournal.org/browse/publication/951 
> https://gitlab.com/romangrothausmann/FacetAnalyser) I would need a runner 
> environment with PV, VTK and ITK ideally for Linux, MacOS and Windows.

ITK is using Gerrit and Jenkins, not Gitlab.

--Ben
___
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

Re: [Paraview] [EXTERNAL] Symbol WinMain missing when compiling with Visual Studio

[Ben Boeckel]

On Thu, Jun 30, 2016 at 19:20:58 +, Scott, W Alan wrote:
> Try building without Ninja?  If that also fails, I could try a build
> of my own.  Haven't done so in 6 months, but it seems to work.
> 
> By the way, what version of Visual Studio?

Also relevant: version of CMake and Qt.

--Ben
___
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

Re: [Paraview] Required CMake version 3.5

[Ben Boeckel]

On Fri, Jun 24, 2016 at 09:28:29 -0400, Jim wrote:
> Can you let me know how it goes?  I just pulled the latest versions of 
> Paraview & cmake and want to build under VS2015. I'm going to work on it 
> over the weekend. If you're doing the same, I could use any 
> configuration tricks you discover.

I thought we had a VS2015 dashboard, but I see it is just VS2013
(thinking back, probably because there isn't a Qt4 build against 2015 on
that machine). They're not that different for setup though. I'll look at
getting the other Windows machine onto the dashboard setup here today.

I don't expect any issues, but if you find any, feel free to email the
list or open issues.

Thanks,

--Ben
___
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

Re: [Paraview] Required CMake version 3.5

[Ben Boeckel]

On Fri, Jun 24, 2016 at 15:50:45 +0200, Christoph Grüninger wrote:
> I don't think it is a good idea to ask for the latest version. Only 
> developers like us have
> a current version of CMake installed. From already released distributions 
> nobody
> provides CMake 3.5.

My thought here is that building ParaView is much harder than CMake, so
it's not a super high barrier to require a custom-built CMake to build a
custom ParaView build.

> > Though I question the distro update policies surrounding where ParaView
> > is aggressively pushed forward when CMake isn't. CMake is *much* better
> > with its backwards compatibility, but I guess it's down to maintainer
> > style to some extent.
> 
> Sorry, there is a misunderstanding. We provide packages for already released
> distributions. We cannot change the CMake version shipped with them. By
> requesting a too recent version, there won't be updated versions of
> ParaView for users of released openSuses any more.
> I know they can download the binaries you provide or get a more recent
> CMake and compile it themselves. You have to weight your inconveniences
> against the ones of your users.

Ah, so this is more like a PPA? Yeah, I guess overriding the CMake from
those wouldn't be a great thing to recommend.

Talking with Utkarsh, we can move the version down since that's our
actual minimum version. However, if things get added to ParaView's build
that require newer CMake support, bumping the minimum version would not
be a huge blocker.

--Ben
___
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

Re: [Paraview] Required CMake version 3.5

[Ben Boeckel]

On Fri, Jun 24, 2016 at 00:25:00 +0200, Cory Quammen wrote:
> @Utkarsh, any foreseeable problems reducing the CMake required version to 3.3?

I think we'll want 3.5 in the (hopefully) near future, so if
distributions don't have a new enough CMake, they can patch it down to
3.3 in the meantime. A comment might be worthwhile.

Though I question the distro update policies surrounding where ParaView
is aggressively pushed forward when CMake isn't. CMake is *much* better
with its backwards compatibility, but I guess it's down to maintainer
style to some extent.

> @Ben, I assume all the dashboard machines are running CMake 3.5. Do
> you think we should downgrade one to CMake 3.3?

I was actually going to upgrade them to 3.6's rc today to test it out.

--Ben
___
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

Re: [Paraview] Required CMake version 3.5

[Ben Boeckel]

On Wed, Jun 22, 2016 at 05:21:33 +0200, Christoph Grüninger wrote:
> thanks for link to the developer mailing list discussion. I think CMake 3.3 
> is better then
> 3.5, because at least the last Leap 42.1 release provides that.
> I patched ParaView to require CMake 3.0 and it builds fine. I will package 
> ParaView 5.1
> that way and hope you reduce the requirement to CMake 3.3 for the next time.

I think the easiest way to check this would be to set the minimum to 3.3
and run against 3.5 to see if any POLICY warnings are triggered for the
way openSUSE builds ParaView. If they are, the old version is probably
silently doing something wrong.

--Ben
___
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

Re: [Paraview] ANN: ParaView 5.1.0-RC1 available for download

[Ben Boeckel]

On Mon, Jun 13, 2016 at 12:11:29 -0400, 曹智选 wrote:
> It turned out that the operating system on my machine does not have the
> library: GLIBCXX_3.4.15. And the linux system on my machine does not allow
> me upgrading the library to GLIBCXX_3.4.15.
> Is there any other way that I can still use the new version of paraview
> without GLIBCXX_3.4.15? I only want to use the SPH interpolation feature of
> the new paraview.

This is a "symbol version". It basically means that your libstdc++ is
too old for the build we created. What Linux distribution and version
are you using?

--Ben
___
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

Re: [Paraview] compiling mdf error

[Ben Boeckel]

On Tue, Feb 02, 2016 at 10:06:25 +, mersad mostaghimi via ParaView wrote:
> Dear Cory Quammenthe first problem is solved but there is an other
> problem  which is again an MD5 problem. this time is in VTK
> installation during installing Paraview from source files.

If you don't need testing data, you can disable it with:

-DBUILD_TESTING:BOOL=OFF

or toggling it in either ccmake or cmake-gui.

--Ben
___
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

Re: [Paraview] Troubles building mathstuf/qhull subproject using PV 4.4.0 superbuild with Intel >14.x compilers

[Ben Boeckel]

On Tue, Jan 19, 2016 at 19:05:38 -0700, Giovanni A. Cone wrote:
> I'm attempting to get PV 4.4.0 builds of Paraview 
> against Intel 14 and 15 on our HPC systems.  One item that 
> some users have asked us for was the Cosmotools integration. 
> This ultimately needs the Qhull library to be built.  Builds 
> against GCC 4.8.2 went through without a hitch.  However the 
> Intel builds all failed with an odd cryptic syntax error 
> message that I do not fully comprehend (sorry I'm still 
> stuck in Fortranistan).
> 
> Building CXX object 
   ^^^

See below.

> CMakeFiles/qhullcpp.dir/src/libqhullcpp/Coordinates.cpp.o
> In file included from 
> /tmp/conega/BUILD/lightshow/paraview-4.4.0-osmesa/intel-15_openmpi-1.6.5/BUILD01/qhull/src/qhull/src/libqhull/poly2.c(16):
> /tmp/conega/BUILD/lightshow/paraview-4.4.0-osmesa/intel-15_openmpi-1.6.5/BUILD01/qhull/src/qhull/src/libqhull/qhull_a.h(106):
>  
> warning #77: this declaration has no storage class or type 
> specifier
>template 
>^
> 
> In file included from 
> /tmp/conega/BUILD/lightshow/paraview-4.4.0-osmesa/intel-15_openmpi-1.6.5/BUILD01/qhull/src/qhull/src/libqhull/poly2.c(16):
> /tmp/conega/BUILD/lightshow/paraview-4.4.0-osmesa/intel-15_openmpi-1.6.5/BUILD01/qhull/src/qhull/src/libqhull/qhull_a.h(106):
>  
> error: expected a ";"
>template 
> ^
>  From what little I understand of C and C++, I believe that 
> "templates" are a C++ construct.  I'm thinking the Intel 
> compiler is attempting to digest the above as "straight-up 
> C" and failing.

Marked above, it is compiling as C++, but it appears that it is trying
to parse template as an identifier rather than a keyword. My guess is
that it is something like:

struct foo {
int member;
} // no semicolon
template ...

which parses into a function returning a foo struct (declared there as
well) named 'template'.

> The error messages put the blame on 
> QHULL_SRC_ROOT/src/libqhull/qhull_a.h  around line 105
> 
> I then decided to snoop on github.com for another qhull 
> repo.  I found one
> at
> 
> https://github.com/qhull/qhull
> 
>  From which I believe the "https://github.com/mathstuf/qhull 
> next branch" repo that Paraview wants to use was forked from.

Not originally, but it is now that qhull has moved from sourceforge to
github (it was originally forked from George Zegaris' clone which he
mirrored from sourceforge to github, but I recently re-forked the proper
repo).

> Point being that the mainline non-forked Qhull has something 
> different in the preprocessor conditional surrounding the 
> above offensive line of source:
> 
> #if defined(__cplusplus) && defined(__INTEL_COMPILER) && 
> !defined(QHULL_OS_WIN)
> 
> while the mathstuf/qhull repo DOES NOT have the above 
> "defined(__cplusplus)" preproc conditional.

My 'next' branch is based off an old release, so differences to upstream
are not surprising.

> I tested to see if the addition would at least allow the 
> 'mathstuf/qhull next branch' source to properly build with 
> Intel 14 and 15.  It got about to 36% and then failed with 
> the error message:

All my branch does is fix an Xcode compilation errors where std::
iterator tags are forward declared improperly.

> In file included from 
> /tmp/conega/qhull_SRC/src/libqhullcpp/QhullIterator.h(13),
> from /tmp/conega/qhull_SRC/src/libqhullcpp/Coordinates.h(13),
> from /tmp/conega/qhull_SRC/src/libqhullcpp/Coordinates.cpp(11):
> /tmp/conega/qhull_SRC/src/libqhull/qhull_a.h(106): error: 
> this declaration may not have extern "C" linkage
>template 
>^

It appears that something is doing

extern "C" {
#include "qhull.h"
}

which won't work since qhull is a C++ header. Are there any 'extern "C"'
bits around? Passing -E (or whatever Intel's equivalent is) to dump the
preprocessed source would help to see. The __cplusplus check may be
guarding against that line in upstream.

> So at least the conditional helped a bit for what I believe 
> is the "straight up C" part of the build.
> 
> 
> I'll CC the author of the fork Ben Boeckel about this.

That's me too :) . Seems I forgot to change the author setting for that
clone :/ . Rewrote the commit with the proper email.

--Ben
___
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

Re: [Paraview] [Non-DoD Source] ANN: ParaView 5.0.0-RC1 is available for download

[Ben Boeckel]

On Wed, Jan 13, 2016 at 16:50:59 +, Angelini, Richard C (Rick) CIV USARMY 
RDECOM ARL (US) wrote:
> Has anyone tried or been able to build ParaView 5.0 on RHEL5?Looks
> like there may be compiler dependencies which exclude a successful build
> on RHEL5?  So far, I’ve not had any luck …..

Doesn't Red Hat provide a gcc44 package? Or was that EPEL?

--Ben
___
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

Re: [Paraview] [Non-DoD Source] ANN: ParaView 5.0.0-RC1 is available for download

[Ben Boeckel]

On Wed, Jan 13, 2016 at 18:50:21 +, Angelini, Richard C (Rick) CIV USARMY 
RDECOM ARL (US) wrote:
> gcc on our RHEL5 systems is 4.1 and seemingly cannot be upgraded.

I think there is also a "gcc44" package which contains a gcc4.4 binary
(and is parallel installable). But I don't remember if it is Red
Hat-provided or EPEL which did so.

--Ben
___
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

Re: [Paraview] What is the difference between pvbatch and pvpython ?

[Ben Boeckel]

On Thu, Jan 07, 2016 at 16:50:16 +0100, houssen wrote:
> What is the difference between pvbatch and pvpython ? (general purpose 
> question)
> 
> My understanding is that one can always use python scripts (from 
> paraview, pvbatch, pvpython), paraview has the GUI, pvbatch is "paraview 
> in batch mode" (that is paraview without the gui). But what is the 
> purpose of pvpython ? When is it needed to use pvbatch or pvpython 
> instead of the other one ? Or what can do pvbatch that pvpython can not 
> do ?

pvbatch and pvpython are both ParaView-aware Python interpreters (sets
sys.path to work with ParaView). pvbatch is the MPI-enabled version of
pvpython.

--Ben
___
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

Re: [Paraview] How to stop a paraview python script on error (try-catch-ing) ?

[Ben Boeckel]

On Sat, Jan 02, 2016 at 16:12:49 +0100, houssen wrote:
> How to stop a paraview python script on error (try-catch-ing) ?
> 
> I have a filter (which calls vtkErrorMacro when an error occurs). I 
> have a python script that uses this filter from paraview: how to stop 
> this script when an error occurs ? I tried to add "try/except" in core 
> part of the script but it does not work as expected (keep running, don't 
> stop).

VTK errors are not Python exceptions, so there's nothing to catch. See
this post from David Gobbi:

http://public.kitware.com/pipermail/vtkusers/2012-June/074703.html

--Ben
___
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

Re: [Paraview] Differences between OpenGL and OpenGL2 versions of ParaView

[Ben Boeckel]

On Wed, Dec 16, 2015 at 13:22:09 -0600, Adam Lyon wrote:
> I'm curious as to why I didn't have any of these problems in v4.4 -- or is
> this two path multiblock rendering code all new for v5?  Thanks again!! --

4.4 defaults to the OpenGL1 backend (glBegin/glEnd); 5.0 is using the
OpenGL2 backend (shaders and VBOs).

--Ben
___
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

Re: [Paraview] Paraview v5.0.0-RC1 with OpenGL2 backend not running using OSMESA v10.5.5

[Ben Boeckel]

On Thu, Dec 10, 2015 at 17:20:35 +0100, Albina, Frank wrote:
> Thank you for the reply. My idea was to run PV-5.0.0-RC1 in parallel on our 
> cluster, 
> therefore the need to recompile as the binaries do not usually ship with this 
> feature
>  and I guess that you do not necessarily know either which parallel 
> communication 
> library is going to be used  on the end user's compute platform.
> 
> If the binaries ship with SWR using prebuilt mesa  binaries, is there any 
> documentation
> on how to build the mesa binaries with SWR support? I might eventually figure 
> it out by
> myself (or not) but I would be grateful for any hints.

Here's the relevant subset of the Dockerfile Utkarsh used:

#--
WORKDIR /opt/tools/src/openswr-mesa
RUN git clone https://github.com/OpenSWR/openswr-mesa.git src-avx2 --depth 1 -b 
11.0-openswr
WORKDIR /opt/tools/src/openswr-mesa/src-avx2
RUN scons build=release texture_float=yes swr_arch=core-avx2 libgl-xlib

WORKDIR /opt/tools/mesa-swr-avx2
RUN cp 
/opt/tools/src/openswr-mesa/src-avx2/build/linux-x86_64/gallium/targets/libgl-xlib/libGL.so.1.5
 . && \
ln -s libGL.so.1 libGL.so && \
ln -s libGL.so.1.5 libGL.so.1

#--
WORKDIR /opt/tools/src/openswr-mesa
RUN git clone https://github.com/OpenSWR/openswr-mesa.git src-avx --depth 1 -b 
11.0-openswr

WORKDIR /opt/tools/src/openswr-mesa/src-avx
RUN scons build=release texture_float=yes swr_arch=avx libgl-xlib

WORKDIR /opt/tools/mesa-swr-avx
RUN cp 
/opt/tools/src/openswr-mesa/src-avx/build/linux-x86_64/gallium/targets/libgl-xlib/libGL.so.1.5
 . && \
ln -s libGL.so.1 libGL.so && \
ln -s libGL.so.1.5 libGL.so.1

--Ben
___
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

Re: [Paraview] Paraview v5.0.0-RC1 with OpenGL2 backend not running using OSMESA v10.5.5

[Ben Boeckel]

On Thu, Dec 10, 2015 at 09:18:44 -0500, Ken Martin wrote:
> people on this list are more familiar with the specifics of setting up SWR
> and Mesa on a cluster but I wanted to at least give you a quick response to
> let you know we are working on it :-)

The binaries built by our buildbots (and uploaded to the website) have
SWR available using prebuilt mesa binaries. If you have AVX CPU
extensions available, passing:

--mesa-swr-avx

should enable it. There's also --mesa-swr-avx2 if you have AVX2
extensions available.

--Ben
___
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

Re: [Paraview] OpenGL Backend Identification

[Ben Boeckel]

On Thu, Dec 10, 2015 at 09:29:27 -0500, Ken Martin wrote:
> Maybe vtkRenderingOpenGLConfigure.h ?
> 
> That header is configured from a .in file for both the old and new backend.
> We could define VTK_OPENGL2 in that header and applications could include
> it as needed.  That header appears to get installed. The only issue I see
> is that if someone built VTK with no rendering then that header file might
> not exist.

The library to link to doesn't either for that matter…

> Does that work? If so I can put the VTK_OPENGL2 definition in there.

It looks like a good location to me.

--Ben
___
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

Re: [Paraview] OpenGL Backend Identification

[Ben Boeckel]

On Thu, Dec 10, 2015 at 10:08:14 -0500, David E DeMarle wrote:
> And it should appear in a wrapped class so that we can get it at runtime
> from python.

In that case, there should probably be an enum in RenderingCore:

enum vtkRenderingBackend {
...
};

class vtkRenderingSomething {
static vtkRenderingBackend getRenderingBackend();
};

--Ben
___
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

Re: [Paraview] OpenGL Backend Identification

[Ben Boeckel]

On Mon, Dec 07, 2015 at 14:49:51 -0500, Tim Thirion wrote:
> I'm looking to provide run-time identification of the current OpenGL
> backend in use. Some questions:
> 
> 1. VTK #defines VTK_OPENGL2, but ParaView #defines VTKGL2. Is there a
> particular reason we have both?

VTK used to have both. VTKGL2 should be migrated to VTK_OPENGL2 (as VTK
did).

> 2. Is there an ideal place to define such a constant? Perhaps on the render
> window?

The About dialog has a list of information already (versions of Python,
matplotlib, numpy, Qt, etc.).

--Ben
___
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

Re: [Paraview] rpath error when compiling ParaView 5.0

[Ben Boeckel]

On Sat, Dec 05, 2015 at 20:53:49 +0200, Armin Wehrfritz wrote:
> I'm building ParaView (version 5.0 RC1) for openSUSE Tumbleweed (using
> gcc 5.2.1) and get an error related to rpath (see below). I cannot say
> much more about this, since don't really understand what's going wrong here.
> 
> Does anybody have some hints how to solve this?

Are you giving any rpath-related settings to CMake? What is the
configure line?

> Please let me know if you need more information.

What version of CMake are you using?

--Ben
___
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

Re: [Paraview] passing argument to pvpython script

[Ben Boeckel]

On Wed, Nov 25, 2015 at 15:11:43 +0300, Gena Bug wrote:
> And this works fine untill I tried new version. In 5rc1 I always get 
> Segmentation Fault:
> Error running 
> "~/ParaView-5.0.0-RC1-Qt4-OpenGL2-Linux-64bit/lib/paraview-5.0/pvpython" 
> "myscript.py" "filename"Segmentation fault
> 
> Seems, sys module couldn't be imported... Is it problem with rc-version? 
> How can I correctly pass arguments to a script?

What distro? I ran into something with similar symptoms and fixed it
here (no one else could reproduce it, so we didn't delay RC1 for it):

https://gitlab.kitware.com/paraview/paraview/merge_requests/478

Do the lastest binaries work for you?


http://www.paraview.org/paraview-downloads/download.php?submit=Download=nightly=all=all=ParaView-5.0.0-RC1-18-g7560de5-Qt4-OpenGL2-Linux-64bit.tar.gz

Thanks,

--Ben
___
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

Re: [Paraview] ParaView 5.0.0-RC1: two minor problems

[Ben Boeckel]

On Fri, Nov 20, 2015 at 11:23:02 -0500, Hom Nath Gharti wrote:
> In Linux 64-bit binary
> 1) error while loading shared libraries: libbz2.so.1.0: cannot open
> shared object file: No such file or directory
> 
> ln -s /lib64/libbz2.so.1 libbz2.so.1.0 fixed the problem.

Hmm, interesting. It seems to be popping into binaries and back out
randomly. RC1 doesn't have it, RC1+5 and RC1+7 (5 and 7 commits later)
has the .so (but not the .1.0 version), and the RC1+10 and RC1+16
binaries don't have it again. I'll try and take a look today or early
next week.

Thanks for the report,

--Ben
___
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

[Paraview] ANN: ParaView 5.0.0-RC1 is available for download

[Ben Boeckel]

Folks,

ParaView 5.0.0-RC1 is now available for download. Checkout the release
notes on the Kitware blog [1].

As always, we look forward to your feedback [2].

Also stay tuned to the Kitware Blog [3] for upcoming features and
enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much
more!

- The ParaView team

[1] http://kitware.com/blog/home/post/998
[2] http://paraview.uservoice.com
[3] http://www.kitware.com/blog/
___
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