[Paraview] ParaView on Intel Mac

[Mike Jackson]

So you are saying that you can actually BUILD and RUN paraview  
successfully on a MacBook? What sources are you using? CVS or  
release? How are you building it?
   I have been completely unsuccessful are running Paraview on my  
MacBook Pro. I can build it, but it bombs part way through startup. I  
thought I tried building with static libs, but I will try again.

   I have no idea on the rest of your questions, sorry. Maybe Andy  
can help? Andy?
--------
Mike Jackson
imikejackson <at> gmail <dot> com



On May 3, 2006, at 2:51 PM, Randy Hudson wrote:

>
> I've built paraview 2.4.3 on my MacBook, and want it to recognize  
> the three custom readers I've written and the vtkGaussianSplatter  
> filter I've added.  (BTW, I was only able to do this by setting  
> BUILD_SHARED_LIBS to OFF.)
>
> I've written the XML files for the user interfaces (and the server  
> manager as well), and set PV_INTERFACE_PATH to point to the  
> directory on the Mac where they reside (and have set things up  
> likewise on the server cluster).
>
> However, when I run "paraview" as a single process under X11 on the  
> Mac, it will only add entries in the filter and file dialog menus  
> for the splatting filter and readers (the readers aren't on the  
> Mac, but this was a test) if I use the "Import Package" submenu of  
> the "File" menu.
>
> And, "pvclient" can't find them via PV_INTERFACE_PATH or "Import  
> Package" -- or finds them but doesn't use them -- when I run in  
> client-sever mode.
>
> (These XML files, readers and filter all worked when I ran the  
> paraview client (in this case, 2.4.2) on my Thinkpad under XP --  
> and when I ran "paraview.exe" as a single process there.)
>
> FYI:  I left the OpenGL and GLU CMake parameters in their default  
> settings, pointing to the frameworks, rather than pointing them at  
> the /usr/X11 directories, where it looks as though there are other  
> headers and lib's.
>
> AND:  weird:  when paraview fails to find/use the XML files, the  
> file dialog menu fills my 1400x900-pixel screen, and beyond (about  
> 14 file types are off-screen and inaccessible), but when the XML  
> files are used, this problem seems not to arise.
>
>
> Any ideas?
>
>
> Thanks.
>
>
> Randy Hudson.
>
> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview