[Paraview] Relocatable Mac plugins saga ends in VICTORY

[Samuel Crow]

Hello again,

I've attached a .zip file containing my fixer.sh BASH script and an example CMakeLists.txt file that uses it.  It requires that CMAKE_SHARED_LINKER_FLAGS be set to -headerpad_max_install_name so that there will be enough space for the new longer file paths.  Feel free to use them in any external plugins you wish.  The install path is assumed to be in paraview.app/Contents/MacOS/plugins/ so it will automatically load at startup.  Once installed, the ParaView bundle can be dragged to wherever you need it installed.

Thanks to everybody who helped my with this project and especially Mike Jackson who knew all the Mac specifics of ParaView that I needed to know.

Good bye everyone,

--Sam Crow

--- On Fri, 9/19/08, Samuel Crow <samuel_crow_work at rocketmail.com> wrote:

> From: Samuel Crow <samuel_crow_work at rocketmail.com>
> Subject: Re: [Paraview] Relocatable Mac plugins saga continues
> To: "ParaView" <paraview at paraview.org>, "Mike Jackson" <mike.jackson at bluequartz.net>
> Date: Friday, September 19, 2008, 9:10 PM
> Hi,
> 
> I think I've got the problem nearly solved.  I just had
> to set CMAKE_SHARED_LINKER_FLAGS to
> -headerpad_max_install_name in order to allocate more space
> for the names in the plugin's .dylib files.  Then I was
> able to prepend @executable_path/../Framework/ to the
> beginning of the Qt framework files with my Bash script.
> 
> I'll give it one last test and then I'll post my
> results.
> 
> --Sam Crow
> 
> 
> --- On Thu, 9/18/08, Mike Jackson
> <mike.jackson at bluequartz.net> wrote:
> 
> > From: Mike Jackson <mike.jackson at bluequartz.net>
> > Subject: Re: [Paraview] Relocatable Mac plugins saga
> continues
> > To: "ParaView" <paraview at paraview.org>
> > Date: Thursday, September 18, 2008, 8:44 PM
> > There was some work going on in the CMake CVS (not
> committed
> > yet) but  
> > I don't think that it would help you. For some
> reason
> > your Qt  
> > Libraries don't even have an install_name equal to
> > their installed  
> > path. Can you rebuild the Qt libraries and try again?
> > 
> > 
> > ---
> > Mike Jackson - Principal Software Engineer
> > www.bluequartz.net
> > 
> > 
> > 
> > 
> > On Sep 18, 2008, at 4:15 PM, Samuel Crow wrote:
> > 
> > > Greetings,
> > >
> > > In our quest to find out why my plugins don't
> work
> > on other people's  
> > > ParaView installs on the Mac version, my boss and
> I
> > have identified  
> > > a problem with the Qt frameworks in the ParaView
> > package.  They  
> > > don't list an @executable_path/../Frameworks/
> in
> > front of them or  
> > > even an absolute path to the Frameworks
> directory. 
> > This means that  
> > > when I'm trying to relocate the plugins they
> find
> > invalid symbolic  
> > > links from the Qt Frameworks that are clearly
> visible
> > as not having  
> > > a path in otool -L .
> > >
> > > Is this a known bug or should somebody file a bug
> > report?  Is there  
> > > a quick fix that I can use in the meantime? 
> I'll
> > need to know soon  
> > > because my contract is about to expire and I must
> get
> > this done  
> > > before that happens.
> > >
> > > --Sam Crow
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > ParaView mailing list
> > > ParaView at paraview.org
> > > http://www.paraview.org/mailman/listinfo/paraview
> > 
> > _______________________________________________
> > ParaView mailing list
> > ParaView at paraview.org
> > http://www.paraview.org/mailman/listinfo/paraview
> 
> 
>       
> 
> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview


      
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Fixer.zip
Type: application/zip
Size: 1206 bytes
Desc: not available
URL: <http://www.paraview.org/pipermail/paraview/attachments/20080919/51c3c193/attachment.zip>