[Paraview] CVS not installing pvpython

[Berk Geveci]

How are you creating this package? First creating an installation with the
default paths and then moving them? It looks like, by modifying one CMake
file, you can have ParaView generate the right sort of build AND set the
right forwarding path without worrying about RPATHs. In
CMake/ParaViewCommon.cmake, the forwarding path seems to be set here:
IF(NOT PV_INSTALL_LIB_DIR)
  SET(PV_INSTALL_LIB_DIR
${PV_INSTALL_ROOT}/lib/paraview-${PARAVIEW_VERSION})
ENDIF(NOT PV_INSTALL_LIB_DIR)

It sound like, if you change that to

IF(NOT PV_INSTALL_LIB_DIR)
  SET(PV_INSTALL_LIB_DIR
${PV_INSTALL_ROOT}/lib/paraview-${PARAVIEW_VERSION})-mpi
ENDIF(NOT PV_INSTALL_LIB_DIR)

everything should work. Of course, take my word with a pinch of salt since I
am only a novice when it comes to writing CMake files.

-berk

On Thu, Aug 14, 2008 at 4:55 PM, Orion Poplawski <orion at cora.nwra.com>wrote:

> Berk Geveci wrote:
>
>> Do you have 2 different paraview executables as well?
>>
>>
> Yup.
>
> --
> Orion Poplawski
> Technical Manager                     303-415-9701 x222
> NWRA/CoRA Division                    FAX: 303-415-9702
> 3380 Mitchell Lane                  orion at cora.nwra.com
> Boulder, CO 80301              http://www.cora.nwra.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20080815/54b77a1f/attachment.htm>