Hi,
it seems that these errors resulted from the fact, that I set an absolute
install
path. However, now I have the problem that the packaging fails to find
cpack/paraview/TGZ/build/install.manifest, which is nonexistent. At least this
is my guess. The error message is:
[...]
1: CPack:
Hi
ArchLinux user here.
Your CMakeCache.txt looks like a QT4 configuration, no occurence of libQt5.
I can build with Qt4 without any problem.
You may want to :
- CleanUp your build directory and configure and build again. Unless
specific needs, i suggest you only set PARAVIEW_QT_VERSION to 4
Rick,
Interesting. I would think that should have worked, assuming you are
on the 'master' branch, and my local testing suggests it would.
What I usually do these days to be be more explicit in my git updates is:
git checkout master
git fetch origin
git merge origin/master
'git pull' does
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
Once again...
so the old two problems seem to still exist. I made some changes in the camke
files to circumvent them, but forgot that they are still there.
Stefan
Am Mittwoch, 22. Februar 2017, 12:33:53 CET schrieb Stefan Vater:
> Hi,
>
> it seems that these errors resulted from the fact,
Hi,
This is Arch Linux user again. Parview no longer opens for me. It just ends
with a core dump (attached). It seems it's something to do with Arch Linux
forward looking policy of favouring QT5. I have specified in the compilation
to build with QT4 (see attached CMakeCache.txt), but on run it
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 was convinced I attached stack trace too. Please see core.dump file. It may
be a red herring but there are several references to libQt5Core there. I am
rebuilding with Qt5 now, but will also try a more minimal build with Qt4 later.
Thanks for quick reply.
Robert
--
Tropics in Cornwall:
Utkarsh,
Thank you very much! I made mistake by casting vtkScalarsToColors to
vtkLookupTable always, without inspecting of other branches! When I put
conditional checking if it is maybe
vtkPVDiscretizableColorTransferFunction, it started working! Thank you very
much for your help!
Nenad.
On
You are right, i did not check the core dump.
Let me know how it goes.
Mathieu Westphal
On Wed, Feb 22, 2017 at 2:36 PM, Robert Sawko wrote:
> I was convinced I attached stack trace too. Please see core.dump file. It
> may
> be a red herring but there are several
I am not sure of this, but I believe I also saw this (i.e., git pull and git
submodule update not updating Superbuild) a week ago. Will pay more attention.
Alan
> -Original Message-
> From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of Cory
> Quammen
> Sent: Wednesday,
Hello,
I recently encountered issues related to the OpenGL2 support for off-screen
Mesa. Up to at least ParaView V5.1.2, I could use ParaView/Catalyst built with
OSMesa with no specific issues (I mostly used OSMesa compiled without LLVM, as
rendering did not represent a huge portion of my
I have a pipeline setup, with a good renderview. I want to then make a split
view, that is identical, except for the camera angle. When I try to split my
view, or create a new view, they show up empty. I can then start manually
turning on, and coloring everything how I want it. But, it
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
Stefan,
Are you building from the v5.2.0 tag in paraview-superbuild? If so, I
recommend building from current master instead. ParaView 5.2.0 is
still the default version in master, but there have been some fixes in
the superbuild that may address the problems you have run into since
v5.2.0 was
Thanks for looking into it, Mathieu.
>- Is your system up to date ?
It's quite up to date. See below.
$ uname -a
Linux avignon 4.9.9-1-ARCH #1 SMP PREEMPT Thu Feb 9 19:07:09 CET 2017 x86_64
GNU/Linux
>- Are you running X ? Wayland ?
Yes, for X. Never heard of Wayland.
>- What
Hi
Well, you found it yourself, looks like you have some problem with OpenGL
and x windows.
Can't help you much more here, let me know when you are able to fix it if
paraview still crashes.
Also, if glxinfo does not work, i would expect all x application to crash
as well.
Regards,
Mathieu
Hi
Please make sure ParaView is compiled in Debug, run it with gdb, then
forward the backtrace.
Mathieu Westphal
On Wed, Feb 22, 2017 at 5:49 PM, Robert Sawko wrote:
> Unfortunately even a minimal compilation of ParaView (no options). I am
> attaching the stack trace.
Looks like a Xorg problem.
Please specify :
- Is your system up to date ?
- Are you running X ? Wayland ?
- What DE/WM are you running ?
- What graphic card do you have ? With which drivers version ?
- What version of opengl is installed ? please provide glxinfo output.
- There should be some
Hi
Thanks for the reply. Did someone else manage to get this approach based on
the superbuilder machinery on a Centos 7 node? As I wrote it previously the
installation works nicely on Ubuntu but fails on CentOS.
I will appréciateur any feedback about it.
Thanks
On Tuesday, February 21, 2017, Ben
20 matches
Mail list logo