Re: [Paraview] [EXTERNAL] Building Catalyst for Albany

2017-08-02 Thread Ibanez, Daniel Alejandro 
Ah, that’s the magic flag.
Thanks, Andy!

From: Andy Bauer <andy.ba...@kitware.com>
Date: Wednesday, August 2, 2017 at 10:27 AM
To: "Ibanez, Daniel Alejandro" <daib...@sandia.gov>
Cc: "paraview@paraview.org" <paraview@paraview.org>
Subject: Re: [Paraview] [EXTERNAL] Building Catalyst for Albany

Hi Dan,
In order to work with an install directory you need to enable 
PARAVIEW_INSTALL_DEVELOPMENT_FILES during your CMake configuration. I 
personally just use my build directory for linking simulations with Catalyst 
though.
Best,
Andy

On Wed, Aug 2, 2017 at 11:19 AM, Ibanez, Daniel Alejandro 
<daib...@sandia.gov<mailto:daib...@sandia.gov>> wrote:
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-boun...@paraview.org<mailto:paraview-boun...@paraview.org>> on behalf 
of "Ibanez, Daniel Alejandro" <daib...@sandia.gov<mailto:daib...@sandia.gov>>
Date: Wednesday, August 2, 2017 at 9:14 AM
To: "paraview@paraview.org<mailto:paraview@paraview.org>" 
<paraview@paraview.org<mailto:paraview@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

___
Powered by www.kitware.com<http://www.kitware.com>

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] [EXTERNAL] Building Catalyst for Albany

2017-08-02 Thread Andy Bauer 
Hi Dan,

In order to work with an install directory you need to enable
PARAVIEW_INSTALL_DEVELOPMENT_FILES during your CMake configuration. I
personally just use my build directory for linking simulations with
Catalyst though.

Best,
Andy

On Wed, Aug 2, 2017 at 11:19 AM, Ibanez, Daniel Alejandro <
daib...@sandia.gov> wrote:

> 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-boun...@paraview.org> on behalf of "Ibanez,
> Daniel Alejandro" <daib...@sandia.gov>
> *Date: *Wednesday, August 2, 2017 at 9:14 AM
> *To: *"paraview@paraview.org" <paraview@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
>
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] [EXTERNAL] Building Catalyst for Albany

2017-08-02 Thread 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-boun...@paraview.org> on behalf of "Ibanez, Daniel 
Alejandro" <daib...@sandia.gov>
Date: Wednesday, August 2, 2017 at 9:14 AM
To: "paraview@paraview.org" <paraview@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
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview