[prev in list] [next in list] [prev in thread] [next in thread] 

List:       paraview
Subject:    Re: [Paraview] Is the ParaView Directory Hardcoded?
From:       Berk Geveci <berk.geveci () gmail ! com>
Date:       2004-10-19 20:01:57
Message-ID: a2ab21560410191301425f1f14 () mail ! gmail ! com
[Download RAW message or body]

A few things:

1. Paraview install path is specified with CMAKE_INSTALL_PREFIX. The
installation path cannot be changed after compilation.
2. You should always use the VTK distributed with ParaView because a.
we branch VTK specially for each paraview release b. we build vtk
differently (special wrapping for example) in paraview


On Tue, 19 Oct 2004 15:49:54 -0400, Kent Eschenberg <eschenbe@psc.edu> wrote:
> Is the ParaView 1.6.3 directory hardcoded? I get hundreds of error messages
> from cmake when I try to install ParaView under Redhat Fedora in
> /usr/local/PV (the source is in /usr/local/PVdev) using my own copy of VTK
> (its already installed elsewhere on the system so I removed the copy in
> ParaView). I expected the cmake system to adapt or ask me where things are
> located but it did neither.
> 
> Kent
> 
> _______________________________________________
> ParaView mailing list
> ParaView@paraview.org
> http://www.paraview.org/mailman/listinfo/paraview
>

[prev in list] [next in list] [prev in thread] [next in thread]