Utkarsh Ayachit a écrit :
The offending line is:
find library=libQtSvg.so.4 [0]; searching
7785: trying file=/usr/lib64/qt4/lib64/libQtSvg.so.4
Try the following. If that works, I'll update the binaries:
Remove files ./lib/paraview-3.14/iconengines/libqsvgicon.so and
Paul McIntosh a écrit :
My 2 cents (sorry for butting in without actually reading the full thread) -
I have noticed that states from earlier version of PV are not compatible
with 3.14 for some reason. If you resave the state then it works.
Hello.
For me, the state files from PV312 are
Oh my freaking god :)
After 3 hours of building Qt from sources and then 1 hour for Paraview I
finally got pvserver to work. My longest linux software installation challenge
so far :)
My only concern is each pvserver consumes 100% of CPU when no clients connected
and it's idle. Is it normal?
Hello,
I am currently trying to compile a rather simple reader plugin so that
it works with the binary release (Linux, 64 Bit, 3.12).
To this end I compiled the paraview sources with the SuperBuild function,
which seams to have worked just fine. But when I compile any plugins
using this build
Can you post the CMakeCache.txt file you're using for building the
plugin? For linux which super build did you use? The linux binaries
were built using the following repo (checkout tag v3.14.0) :
https://gitorious.org/paraview-collaboration/paraview-binaries-superbuild
To influence the search
For me, the state files from PV312 are almost compatible with PV 314: when
opening an earlier version state file, PV 314 just proposes to create an
additional view that may be canceled and I recover the full saved state.
Maybe this is due to the new Layout feature ?
That shouldn't affect it.
I have attached the CMakeCache.txt. I am using the SuperBuild
directory of the ParaView 3.12 source release from the ParaView
website, since we are still using version 3.12.
I will try the new version though, if I can make that work that
will probably suffice.
Thanks for the RPATH hint, that is
To speed up Qt compilation, compile without example and demos and remember
to use the j switch with the number of cores you want to build with.
On Fri, Feb 24, 2012 at 5:12 AM, Kaster Might kastermi...@gmail.com wrote:
Oh my freaking god :)
After 3 hours of building Qt from sources and then 1
I think I know the problem. Qt was built with libpng 1.2 and ParaView
superbuild is building paraview with libpng 1.5 and hence the issue.
You'lll have to build Qt telling it to link against libpng1.5. The new
superbuild I used for ParaView 3.14 takes care of that, but I'm not
sure it'll work out
Utkarsh Ayachit a écrit :
For me, the state files from PV312 are almost compatible with PV 314: when
opening an earlier version state file, PV 314 just proposes to create an
additional view that may be canceled and I recover the full saved state.
Maybe this is due to the new Layout feature ?
Richard,
A state file without data would help too. Let's start there and see if
we can address the issues.
Thanks,
Utkarsh
On Fri, Feb 24, 2012 at 9:11 AM, Richard GRENON richard.gre...@onera.fr wrote:
Utkarsh Ayachit a écrit :
For me, the state files from PV312 are almost compatible with PV
Thanks Richard, I could reproduce both the issue. I've pushed a fix
for the first and I'll track the second one down as well.
FYI: http://paraview.org/Bug/view.php?id=12964
Utkarsh
___
Powered by www.kitware.com
Visit other Kitware open-source
Thank you Utkarsh. Removing these libraries makes PV 314 able to open data
files or load pvsm states.
Please, let me know when the updated binaries will be available and I will
make tests.
Richard, the new binaries have now been uploaded.
Utkarsh
Utkarsh Ayachit a écrit :
Thank you Utkarsh. Removing these libraries makes PV 314 able to open data
files or load pvsm states.
Please, let me know when the updated binaries will be available and I will
make tests.
Richard, the new binaries have now been uploaded.
Utkarsh
Utkarsh
From your description, I'm not entirely sure what you are intending to do.
What do you mean by plot the distances? Do you mean use the ruler filter?
At any rate, what you want to do might not be very straightforward. First,
there is an intentional disconnect between filter operations and
Hello all,
I am trying to compile Paraview 3.12 on my x86_64 Fedora 15 workstation.
My main interest is in offscreen rendering so I had to build my own Mesa
libraries (7.5.2) with OSMesa. The system OSMesa libraries are not set up
properly (or the wrong version) and so if I link to them,
Hello all,
I am trying to compile Paraview 3.12 on my x86_64 Fedora 15 workstation.
My main interest is in offscreen rendering so I had to build my own Mesa
libraries (7.5.2) with OSMesa. The system OSMesa libraries are not set up
properly (or the wrong version) and so if I link to them,
On 02/24/2012 01:22 PM, Peter Brady wrote:
If I set my LD_LIBRARY_PATH to include my 7.5.2 Mesa libraries then
offscreen rendering works fine. However, I don't want my system as a
whole to use my separate Mesa libraries; only Paraview.
Hi Peter,
I don't know the rpath settings but I have a
I am a very new user of Paraview - and am just learning its capabilities. I
am importing a series of CSV files - creating points and Delaunay polygons
- and then using the Calculator filter to create vectors to plot with the
Glyph tool. But when I use the calculator - one of the Point Data
19 matches
Mail list logo
