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
oec...@kitware.com>
Sent: Monday, February 13, 2017 3:23:41 PM
To: Cory Quammen
Cc: Michel Rasquin; paraview@paraview.org
Subject: Re: [Paraview] PVSB 5.2: missing modules and plugins after "make
install"
On Sat, Feb 11, 2017 at 17:48:27 -0500, Cory Quammen wrote:
> Will upda
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,
Ben,
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.
Thanks,
Cory
On Thu, Feb 9, 2017 at 5:08 AM, Michel Rasquin
Hi everyone,
I could successfully build and run (to some extend) PVSB 5.2 (thanks Andy and
Chuck for your help!) but I have now noticed an issue with the installation of
the PVSB project. Concretely, "make install" in the PVSB 5.2 build directory
does not install properly all the expected
