[Paraview] [EXTERNAL] Building Catalyst for Albany

[Ibanez, Daniel Alejandro]

It seems I can point Albany at my build directory of Catalyst, although I wonder why these things aren’t available in the install directory.

From: ParaView <paraview-bounces at paraview.org> on behalf of "Ibanez, Daniel Alejandro" <daibane at sandia.gov>
Date: Wednesday, August 2, 2017 at 9:14 AM
To: "paraview at paraview.org" <paraview at paraview.org>
Subject: [EXTERNAL] [Paraview] Building Catalyst for Albany

Hello,

I’m trying to revive the integration of Catalyst into the Albany application.
I’ve grabbed the Catalyst-v5.4.1-RC2-Base-Enable-Python tarball and configured like this:

#!/bin/bash -ex
$HOME/src/Catalyst-v5.4.1-RC2-Base-Enable-Python/cmake.sh $HOME/src/Catalyst-v5.4.1-RC2-Base-Enable-Python \
-DCMAKE_INSTALL_PREFIX:PATH=$HOME/install/gcc/catalyst \
-DCMAKE_CXX_COMPILER:FILEPATH=$HOME/install/gcc/mpich/bin/mpicxx \
-DCMAKE_C_COMPILER:FILEPATH=$HOME/install/gcc/mpich/bin/mpicc \
2>&1 | tee config_log

But the install directory doesn’t contain any headers or ParaViewConfig.cmake files.
In Albany, the following is done:

find_package(ParaView REQUIRED COMPONENTS vtkPVPythonCatalyst)
include("${PARAVIEW_USE_FILE}")

target_link_libraries(albanyCatalyst LINK_PRIVATE vtkPVPythonCatalyst)


Where am I going wrong? What is it I should be installing?

Thanks!

Dan Ibanez
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170802/3255f35e/attachment.html>