[Paraview] Relocatable plugins on ParaView CVS for Mac?

[Mike Jackson]

Couple things come to mind that need to be checked.
    Where exactly in relation to the paraview.app bundle are you  
trying to load the plugins from?
    Also, what is the output of running "otool -L  [plugin]".

I have some ideas but let's see the answers to those first..

  _________________________________________________
| Mike Jackson - Principal Software Engineer      |
| BlueQuartz Software                             |
| mike.jackson at bluequartz.net                     |
| www.bluequartz.net                              |
---------------------------------------------------


On Sep 8, 2008, at 12:17 PM, Samuel Crow wrote:

> Hello again,
>
> I've written a BASH script that translates the paths of any  
> libraries that have been accessing from the ParaView executable to  
> use @executable_path but unfortunately the GUI plugins don't work on  
> the destination computer.  I am using the RPath feature of MaxOSX to  
> generate the .Dylib files.  My goal is to make my plugins work on  
> any Mac running the 3.3.1 version of ParaView downloaded from the  
> ParaView website.
>
> On the build computer I'm getting the error message  
> "QObject::setParent: Cannot set parent, new parent is in a different  
> thread".  The plugins still work on this computer but if I copy them  
> to another machine that doesn't have the build environment, the  
> readers won't work.  The source plugin works since it only has a  
> server-manager plugin anyway.  I suspect the filter would work also  
> for similar reasons.
>
> My build machine is a MacPro with 2 quad-cord Xeon processors and 4  
> Gigs of RAM running MacOSX 10.5.4 .
>
>
>
>
> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview