[Paraview] Fwd: Amazon EC2 Cluster + Paraview

Fabian, Nathan ndfabia at sandia.gov
Mon Feb 14 12:37:41 EST 2011


Actually, the error I saw was related to it trying to include a wrong renderwindow.h ..

However, your error is similar.  It looks like it's got the wrong directory for including exodus headers, since it includes

${CMAKE_SOURCE_DIR}/Utilities/exodusii/include

when it should probably be

${CMAKE_SOURCE_DIR}/VTK/Utilities/exodusii/include

if it's building inside Paraview.  I'm not knowledgeable enough to say what the true answer is, since I think it's not always built inside paraview.

The shorter answer may be just to disable XDMF_BUILD_UTILS in your CMake config.

On 2/12/11 11:51 AM, "Matthew Dillon" <mrdillon at alaska.edu> wrote:

I am guessing that this error is related to the error you mentioned below...

/home/ubuntu/ParaView-3.8.1/Utilities/Xdmf2/libsrc/utils/XdmfExodusReader.cxx:27:22: error: exodusII.h: No such file or directory

I have no need for the exodusii reader, I didn't see anywhere that I could disable it in cmake

On Fri, Feb 11, 2011 at 4:37 PM, Fabian, Nathan <ndfabia at sandia.gov> wrote:
The OSMESA_LIBRARY should also point to libOSMesa.so

(btw you can also compile leaving OPENGL_gl_LIBRARY and OPENGL_glu_LIBRARY empty.  I found I needed to do this when compiling static to avoid link errors in, I think, the XDMF library).


On 2/11/11 6:32 PM, "Matthew Dillon" <mrdillon at alaska.edu <http://mrdillon@alaska.edu> > wrote:

Nathan,
Thanks for the reply. That cleared out most of the warnings. I am left with:

 WARNING: Target "vtkRendering" requests linking to directory "/home/ubuntu/osmesa/lib".  Targets may link only to libraries.  CMake is dropping the item.
 WARNING: Target "vtkRendering" requests linking to directory "/home/ubuntu/osmesa/lib".  Targets may link only to libraries.  CMake is dropping the item.
 WARNING: Target "vtkVolumeRendering" requests linking to directory "/home/ubuntu/osmesa/lib".  Targets may link only to libraries.  CMake is dropping the item.

which seems kind of critical to me... I am sure i am missing something else, but not sure what:



More information about the ParaView mailing list