[Paraview] error in X86_64: libvtkalglib.so

[Olesen, Mark]

Hi Berk,

While we're somewhat on the topic of installing, I would like to get some tips about the correct means of building/installing a portable version of paraview.

I currently have "make", "make HTMLDocumentation", "make install" with the build directories and install directories being different (same issue as Ricardo). I would like to be able to move all the sources about later, but also need to retain the build directory (to build plugins at a later stage).

Is it safe to have identical build/install directories?
If I wish to move my files about after the initial compilation (eg from a local disk to an NFS-share), what is the best means of doing this without recompiling everything? I tried editing the *.cmake files to use environment variables. This helps find relocated things (I think), but also provokes an unnecessary remake.

How do you go about bundling things like this?

/mark


Dr. Mark Olesen
Principal Engineer Thermofluids Analysis
EMCON Technologies Germany (Augsburg) GmbH
Biberbachstr. 9
D-86154 Augsburg, GERMANY
tel: +49 (821) 4103 - 862
fax: +49 (821) 4103 - 7862
--
Aufsichtsrat: Gary Strickland (Vors.)
Geschäftsführung: Michael Bleidt (Vors.), Dr. Martin Funk, Martin Stüttem
Eintrag: Registergericht Augsburg HRB 20757

> -----Original Message-----
> From: Berk Geveci [mailto:berk.geveci at kitware.com]
> Sent: Tuesday, December 16, 2008 3:12 PM
> To: Ricardo Reis
> Cc: Olesen, Mark; paraview at paraview.org
> Subject: Re: [Paraview] error in X86_64: libvtkalglib.so
> 
> Ricardo,
> 
> Update your cvs and try again please. This is a new library that was
> missing install rules. It should be fixed.
> 
> -berk
> 
> 
> 
> On Tue, Dec 16, 2008 at 8:48 AM, Ricardo Reis <rreis at aero.ist.utl.pt>
> wrote:
> > On Tue, 16 Dec 2008, Olesen, Mark wrote:
> >
> >> Since bin/paraview finds paraview-real, it would seem that the
> >> lib/paraview-X.X directory is actually there.
> >>
> >> Did you attempt to install to the same directory as your build
> >> directory?  This is where I've encounter the same problem before.
> >
> > No, I'm using a diferent dir and when I do "make install" he puts
> stuff
> > there.
> >
> >> If you just edit the CMAKE_INSTALL_PREFIX:PATH in CMakeCache.txt
> (in the
> >> build dir) and try 'make install' again.
> >
> > I have this in my CMAKE_INSTALL_PREFIX
> >
> > CMAKE_INSTALL_PREFIX:PATH=/usr/local/paraviewcvs.shared
> >
> > so this is not the problem, it seems...
> >
> > Should I atach my CMakeCache.txt ?
> >
> >  Ricardo Reis
> >
> >  'Non Serviam'
> >
> >  PhD student @ Lasef
> >  Computational Fluid Dynamics, High Performance Computing,
> Turbulence
> >  http://www.lasef.ist.utl.pt
> >
> >  &
> >
> >  Cultural Instigator @ Rádio Zero
> >  http://www.radiozero.pt
> >
> >  http://www.flickr.com/photos/rreis/
> > _______________________________________________
> > ParaView mailing list
> > ParaView at paraview.org
> > http://www.paraview.org/mailman/listinfo/paraview
> >
> >
This e-mail message and any attachments may contain 
legally privileged, confidential or proprietary Information, 
or information otherwise protected by law of EMCON 
Technologies, its affiliates, or third parties. This notice 
serves as marking of its "Confidential" status as defined 
in any confidentiality agreements concerning the sender 
and recipient. If you are not the intended recipient(s), 
or the employee or agent responsible for delivery of this 
message to the intended recipient(s), you are hereby 
notified that any dissemination, distribution or copying 
of this e-mail message is strictly prohibited. 
If you have received this message in error, please 
immediately notify the sender and delete this e-mail 
message from your computer.