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

[Samuel Crow]

I thought that "make install" just called that script internally.  It has been working on the stable release source.  Does the stable release do more that doesn't get done when invoking the script from the terminal?  Also, whether you do "make install" or invoke the script you have to be logged in as the administrator or neither of them will work.


--- 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: "Mike Jackson" <mike.jackson at imts.us>
> Cc: samuel_crow_work at rocketmail.com, paraview at paraview.org
> Date: Thursday, August 14, 2008, 7:40 PM
> "make install" will probably work in 3.4 but until
> then we are stuck with
> the script. By the way, I make the paraview binaries using
> that same script
> on Tiger. I think it makes some assumptions that may not
> work for you. How
> does it fail? I cannot imagine it failing such that the
> bundle is not even
> created. It is more likely that the bundle is incomplete if
> the script
> fails. Note that the script is a hack and it does produce
> bunch of errors
> that can be ignored.
> 
> On Thu, Aug 14, 2008 at 3:08 PM, Mike Jackson
> <mike.jackson at imts.us> wrote:
> 
> > This does NOT work on my 10.4.11/Xcode 2.5 system.
> There are lots and lots
> > of errors during that script and the paraview.app
> never gets created.
> > I do "make install", which is the way I
> _thought_ I was supposed to build
> > the .app bundle.
> >
> > --
> > Mike Jackson   Senior Research Engineer
> > Innovative Management & Technology Services
> >
> >
> > On Aug 14, 2008, at 12:51 PM, Berk Geveci wrote:
> >
> > Run Applications/Client/CreateBundle.sh in your build
> tree which will
> > hopefully create a bundle that works.
> >
> >
> >