[Paraview] Will using RPath interfere with CPack on a Mac?

[Samuel Crow]

Would it be possible to make a custom build of Paraview with the plugins built in so that my coworkers could just download it from the network and unpack it to somewhere and run it?


--- On Thu, 8/14/08, Berk Geveci <berk.geveci at kitware.com> wrote:

> From: Berk Geveci <berk.geveci at kitware.com>
> Subject: Re: [Paraview] Will using RPath interfere with CPack on a Mac?
> To: samuel_crow_work at rocketmail.com
> Cc: paraview at paraview.org
> Date: Thursday, August 14, 2008, 12:15 PM
> I think you will have to run install_name_tool. I can't
> think of
> another way of making your libraries find the paraview
> libraries. We
> discussed in the past installing the ParaView libraries as
> a
> framework. That would fix your issue but would require more
> than a
> drag and drop on the user part to install ParaView.
> 
> On Wed, Aug 13, 2008 at 5:28 PM, Samuel Crow
> <samuel_crow_work at rocketmail.com> wrote:
> >
> > I think I'll have the Mac version install in the
> Paraview package itself so that the developer releases will
> automatically scan for them on startup.
> >
> > Likewise I think I'll have the Windows version
> install in the same directory as the Paraview executable. 
> That's another discussion though.
> >
> > --- On Wed, 8/13/08, Berk Geveci
> <berk.geveci at kitware.com> wrote:
> >
> >> From: Berk Geveci <berk.geveci at kitware.com>
> >> Subject: Re: [Paraview] Will using RPath interfere
> with CPack on a Mac?
> >> To: samuel_crow_work at rocketmail.com
> >> Cc: paraview at paraview.org
> >> Date: Wednesday, August 13, 2008, 8:29 PM
> >> Hmmm. Tricky. Where will the users insall the
> plugin?
> >>
> >> On Wed, Aug 13, 2008 at 4:04 PM, Samuel Crow
> >> <samuel_crow_work at rocketmail.com> wrote:
> >> > I remember seeing a note somewhere in the
> ParaView
> >> build files that there was a problem associated
> with
> >> installation of dynamic libraries that were
> installed using
> >> RPath.  Does that mean that I can't distribute
> my reader
> >> plugins using CPack without having to manually
> execute
> >> install_name_tool -change on all of the library
> dependencies
> >> internally used by the reader .dylib files?
> >> >
> >> > What I'm trying to do is make my readers
> work on
> >> user systems that have a binary install of
> ParaView on them.
> >>  I'd like to use CPack to generate a .dmg file
> for the
> >> readers as a package.
> >> >
> >> >
> >> >
> >> >
> >> >
> _______________________________________________
> >> > ParaView mailing list
> >> > ParaView at paraview.org
> >> >
> http://www.paraview.org/mailman/listinfo/paraview
> >> >
> >
> >
> >
> >
> >