Hi David, I¹m trying to install the paraview bundle in CMAKE_INSTALL_PREFIX but am not having any luck. If I set DESTDIR it just prepends that to CMAKE_INSTALL_PREFIX for the stuff the goes in lib,bin,... and trys to put the bundle in DESTDIR/Applications. What I would like is to put the paraview.app in CMAKE_INSTALL_PREFIX along with the standard lib/bin/include setup. This is how Cmake.app gets installed. If I just try to run make install¹ with CMAKE_INSTALL_PREFIX set, it trys to put the bundle in /Applications, which doesn¹t seem right to me. Is there an easy way to make everything get installed in CMAKE_INSTALL_PREFIX?
Thanks, Chris On 10/31/08 8:58 AM, "David Cole" <[EMAIL PROTECTED]> wrote: > You need to do a "make install" to produce the standalone bundle. > > I recommend using...: > DESTDIR=pvinst make install > > ...and then getting the standalone bundle out of the pvinst directory... > > Why do you say the build directory is needed to launch it? What happens if you > move/rename the build directory and try to launch the standalone bundle? > > > On Fri, Oct 31, 2008 at 7:00 AM, Pierre-Olivier Dallaire > <[EMAIL PROTECTED]> wrote: >> Good morning, >> >> with the latest version of Paraview (3.5.0), I understand that there is a new >> script >> (paraview_OSX_MakeStandAloneBundle.sh) to create the Mac OS X application >> bundle. >> However, the application only weights now 15 M and in fact is not standalone >> as before -> >> the build directory is needed to launch it. Any thoughts on how to solve this >> problem ? >> >> Best regards, >> >> PO >> _______________________________________________ >> ParaView mailing list >> ParaView@paraview.org >> http://www.paraview.org/mailman/listinfo/paraview > > > > _______________________________________________ > ParaView mailing list > ParaView@paraview.org > http://www.paraview.org/mailman/listinfo/paraview
_______________________________________________ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
