<div dir="ltr">Sure. Compile ParaView (make sure that RPATH is on). Run Applications/Client/CreateBundle.sh in your build tree which will hopefully create a bundle that works. Copy your plugins under (I think) Contents/MacOS inside the bundle. Run install_name_tool to fix the paths of your plugins.<div>
<br></div><div>-berk</div><div><br><br><div class="gmail_quote">On Thu, Aug 14, 2008 at 12:32 PM, Samuel Crow <span dir="ltr"><<a href="mailto:samuel_crow_work@rocketmail.com">samuel_crow_work@rocketmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">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?<br>
<div class="Ih2E3d"><br>
<br>
--- On Thu, 8/14/08, Berk Geveci <<a href="mailto:berk.geveci@kitware.com">berk.geveci@kitware.com</a>> wrote:<br>
<br>
> From: Berk Geveci <<a href="mailto:berk.geveci@kitware.com">berk.geveci@kitware.com</a>><br>
> Subject: Re: [Paraview] Will using RPath interfere with CPack on a Mac?<br>
> To: <a href="mailto:samuel_crow_work@rocketmail.com">samuel_crow_work@rocketmail.com</a><br>
> Cc: <a href="mailto:paraview@paraview.org">paraview@paraview.org</a><br>
</div>> Date: Thursday, August 14, 2008, 12:15 PM<br>
<div><div></div><div class="Wj3C7c">> I think you will have to run install_name_tool. I can't<br>
> think of<br>
> another way of making your libraries find the paraview<br>
> libraries. We<br>
> discussed in the past installing the ParaView libraries as<br>
> a<br>
> framework. That would fix your issue but would require more<br>
> than a<br>
> drag and drop on the user part to install ParaView.<br>
><br>
> On Wed, Aug 13, 2008 at 5:28 PM, Samuel Crow<br>
> <<a href="mailto:samuel_crow_work@rocketmail.com">samuel_crow_work@rocketmail.com</a>> wrote:<br>
> ><br>
> > I think I'll have the Mac version install in the<br>
> Paraview package itself so that the developer releases will<br>
> automatically scan for them on startup.<br>
> ><br>
> > Likewise I think I'll have the Windows version<br>
> install in the same directory as the Paraview executable.<br>
> That's another discussion though.<br>
> ><br>
> > --- On Wed, 8/13/08, Berk Geveci<br>
> <<a href="mailto:berk.geveci@kitware.com">berk.geveci@kitware.com</a>> wrote:<br>
> ><br>
> >> From: Berk Geveci <<a href="mailto:berk.geveci@kitware.com">berk.geveci@kitware.com</a>><br>
> >> Subject: Re: [Paraview] Will using RPath interfere<br>
> with CPack on a Mac?<br>
> >> To: <a href="mailto:samuel_crow_work@rocketmail.com">samuel_crow_work@rocketmail.com</a><br>
> >> Cc: <a href="mailto:paraview@paraview.org">paraview@paraview.org</a><br>
> >> Date: Wednesday, August 13, 2008, 8:29 PM<br>
> >> Hmmm. Tricky. Where will the users insall the<br>
> plugin?<br>
> >><br>
> >> On Wed, Aug 13, 2008 at 4:04 PM, Samuel Crow<br>
> >> <<a href="mailto:samuel_crow_work@rocketmail.com">samuel_crow_work@rocketmail.com</a>> wrote:<br>
> >> > I remember seeing a note somewhere in the<br>
> ParaView<br>
> >> build files that there was a problem associated<br>
> with<br>
> >> installation of dynamic libraries that were<br>
> installed using<br>
> >> RPath. Does that mean that I can't distribute<br>
> my reader<br>
> >> plugins using CPack without having to manually<br>
> execute<br>
> >> install_name_tool -change on all of the library<br>
> dependencies<br>
> >> internally used by the reader .dylib files?<br>
> >> ><br>
> >> > What I'm trying to do is make my readers<br>
> work on<br>
> >> user systems that have a binary install of<br>
> ParaView on them.<br>
> >> I'd like to use CPack to generate a .dmg file<br>
> for the<br>
> >> readers as a package.<br>
> >> ><br>
> >> ><br>
> >> ><br>
> >> ><br>
> >> ><br>
> _______________________________________________<br>
> >> > ParaView mailing list<br>
> >> > <a href="mailto:ParaView@paraview.org">ParaView@paraview.org</a><br>
> >> ><br>
> <a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
> >> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
<br>
<br>
<br>
<br>
</div></div></blockquote></div><br></div></div>