visit through spack

[markcmiller86]

Date: Tue, 23 Mar 2021 09:26:26 -0700
From: cessenat at free.fr (Olivier Cessenat)
This post was imported from the [email protected] email archive

---

Dear VisIt developers,

I'm very interested in VisIt being installed using 'spack' as an
alternative to the 'build_visit' script.

With 'spack', pre-requisites to building VisIt can be reduced to
practically none, and applying patches to third party libs remains
possible at the expense of modifying the third_party/package.py setting.
I have in view a private plugin that depends on a private software and
of course on VisIt. My sources can be compiled in many different
manners, and this is where 'spack' is such a potential paradise. I can
use VisIt as an external package to 'spack', but having it inside
'spack' as well would be great (for HDF5, MPI, Python...). In this way,
in my use case, VisIt would be installed with the minimum number of
plugins, and they would be added later on, such as for 'octave' or 'perl'.

The question at last:

When installing 3.1.1, and using xml2cmake from it, I get an error about
not finding 'PluginVsInstall.cmake'. Would this be hard to configure
visit/package.py so that it gets added ?

Thanks,

Olivier Cessenat.

BTW: I managed to build visit 3.1.4 on CentOS 7.8 through spack, but I
failed on Ubuntu 18.04 (Python not found..) while build-visit

---

[markcmiller86]

Date: Tue, 23 Mar 2021 10:23:20 -0700
From: biagas2 at llnl.gov (Biagas, Kathleen)
This post was imported from the [email protected] email archive

---

Hello Olivier,

PluginVsInstall.cmake is only installed if 'VISIT_INSTALL_THIRD_PARTY' cmake var is set to true.
So , '-DVISIT_INSTALL_THIRD_PARTY=ON' would need to be added to 'args'.

Kathleen

-----Original Message-----
From: Olivier Cessenat via visit-developers <visit-developers at elist.ornl.gov>
Sent: Tuesday, March 23, 2021 9:26 AM
To: VisIt Developers <visit-developers at elist.ornl.gov>
Cc: Olivier Cessenat <cessenat at free.fr>
Subject: [visit-developers] [EXTERNAL] VisIt through spack

Dear VisIt developers,

I'm very interested in VisIt being installed using 'spack' as an alternative to the 'build_visit'
script.

With 'spack', pre-requisites to building VisIt can be reduced to practically none, and applying
patches to third party libs remains possible at the expense of modifying the third_party/package.py
setting.
I have in view a private plugin that depends on a private software and of course on VisIt. My
sources can be compiled in many different manners, and this is where 'spack' is such a potential
paradise. I can use VisIt as an external package to 'spack', but having it inside 'spack' as well
would be great (for HDF5, MPI, Python...). In this way, in my use case, VisIt would be installed
with the minimum number of plugins, and they would be added later on, such as for 'octave' or
'perl'.

The question at last:

When installing 3.1.1, and using xml2cmake from it, I get an error about not finding
'PluginVsInstall.cmake'. Would this be hard to configure visit/package.py so that it gets added ?

Thanks,

Olivier Cessenat.

BTW: I managed to build visit 3.1.4 on CentOS 7.8 through spack, but I failed on Ubuntu 18.04
(Python not found..) while build-visit

---

[markcmiller86]

Date: Tue, 23 Mar 2021 10:52:56 -0700
From: harrison37 at llnl.gov (Harrison, Cyrus D.)
This post was imported from the [email protected] email archive

---

Hi Olivier,

We are supportive of spack + we can get this option added to the VisIt spack package when we add the
3.2.0 release.

-Cyrus

?On 3/23/21, 10:23 AM, 'Biagas, Kathleen via visit-developers' <visit-developers at elist.ornl.gov>
wrote:

Hello Olivier,

PluginVsInstall.cmake is only installed if 'VISIT_INSTALL_THIRD_PARTY' cmake var is set to true.
So , '-DVISIT_INSTALL_THIRD_PARTY=ON' would need to be added to 'args'.

Kathleen

-----Original Message-----
From: Olivier Cessenat via visit-developers <visit-developers at elist.ornl.gov>
Sent: Tuesday, March 23, 2021 9:26 AM
To: VisIt Developers <visit-developers at elist.ornl.gov>
Cc: Olivier Cessenat <cessenat at free.fr>
Subject: [visit-developers] [EXTERNAL] VisIt through spack

Dear VisIt developers,

I'm very interested in VisIt being installed using 'spack' as an alternative to the 'build_visit'
script.

With 'spack', pre-requisites to building VisIt can be reduced to practically none, and applying
patches to third party libs remains possible at the expense of modifying the third_party/package.py
setting.
I have in view a private plugin that depends on a private software and of course on VisIt. My
sources can be compiled in many different manners, and this is where 'spack' is such a potential
paradise. I can use VisIt as an external package to 'spack', but having it inside 'spack' as well
would be great (for HDF5, MPI, Python...). In this way, in my use case, VisIt would be installed
with the minimum number of plugins, and they would be added later on, such as for 'octave' or
'perl'.

The question at last:

When installing 3.1.1, and using xml2cmake from it, I get an error about not finding
'PluginVsInstall.cmake'. Would this be hard to configure visit/package.py so that it gets added ?

Thanks,

Olivier Cessenat.

BTW: I managed to build visit 3.1.4 on CentOS 7.8 through spack, but I failed on Ubuntu 18.04
(Python not found..) while build-visit

---

[markcmiller86]

Date: Wed, 24 Mar 2021 06:44:59 -0700
From: cessenat at free.fr (Olivier Cessenat)
This post was imported from the [email protected] email archive

---

Thanks very much for the hint Katleen and the proposal Cyrus.

I have a remaining small trick when +mpi:

- when I use VisIt as an external package (the 3.1.3 for Ubuntu with
mpich that you provide as file visit3_1_3.linux-x86_64-ubuntu18.tar.gz)
engine_par is built and works fine ; compilation line is :

/home/cessenat/Softs/spack/lib/spack/env/gcc/g++ -DENGINE
-DESophieDatabase_par_EXPORTS ...bla bla bla? -DMPICH_SKIP_MPICXX
-DOMPI_SKIP_MPICXX -DMPI_NO_CPPBIND -DPARALLEL -DMPICH_IGNORE_CXX_SEEK
-I/opt/visit/3.1.3/linux-x86_64/include/mpich/include -fPIC -std=gnu++11
-o CMakeFiles/ESophieDatabase_par.dir/SophieEnginePluginInfo.C.o ... bla
bla bla

and link line includes '/opt/visit/3.1.3/linux-x86_64/lib/libmpi.so'.

- when I use VisIt as I just built with spack+mpi and
'-DVISIT_INSTALL_THIRD_PARTY=ON', there is no ' -I/path_tompi.h -fPIC '
and no '/pathto_libmpi.so' even though I add (or not) an explicit mpi
dependency in my visit-plugin.

What should I do ?

Just for info I compiled VisIt on Ubuntu 18.04 x86_64 with

spack install visit at 3.1.1+gui+silo+mpi+python ^glib at 2.56.3
^py-setuptools at 44.1.0 ^llvm at 10.0.1~flang ^vtk at 8.1.0+opengl2+python
^mpich? ^python at 2.7+shared

Olivier Cessenat

Le 23/03/2021 ? 18:52, Harrison, Cyrus D. a ?crit?:
> Hi Olivier,
>
> We are supportive of spack + we can get this option added to the VisIt spack package when we add
the 3.2.0 release.
>
> -Cyrus
>
> ?On 3/23/21, 10:23 AM, 'Biagas, Kathleen via visit-developers' <visit-developers at
elist.ornl.gov> wrote:
>
>      Hello Olivier,
>
>      PluginVsInstall.cmake is only installed if 'VISIT_INSTALL_THIRD_PARTY' cmake var is set to
true.
>      So , '-DVISIT_INSTALL_THIRD_PARTY=ON' would need to be added to 'args'.
>
>      Kathleen
>
>
>      -----Original Message-----
>      From: Olivier Cessenat via visit-developers <visit-developers at elist.ornl.gov>
>      Sent: Tuesday, March 23, 2021 9:26 AM
>      To: VisIt Developers <visit-developers at elist.ornl.gov>
>      Cc: Olivier Cessenat <cessenat at free.fr>
>      Subject: [visit-developers] [EXTERNAL] VisIt through spack
>
>      Dear VisIt developers,
>
>      I'm very interested in VisIt being installed using 'spack' as an alternative to the
'build_visit' script.
>
>      With 'spack', pre-requisites to building VisIt can be reduced to practically none, and
applying patches to third party libs remains possible at the expense of modifying the
third_party/package.py setting.
>      I have in view a private plugin that depends on a private software and of course on VisIt. My
sources can be compiled in many different manners, and this is where 'spack' is such a potential
paradise. I can use VisIt as an external package to 'spack', but having it inside 'spack' as well
would be great (for HDF5, MPI, Python...). In this way, in my use case, VisIt would be installed
with the minimum number of plugins, and they would be added later on, such as for 'octave' or
'perl'.
>
>      The question at last:
>
>      When installing 3.1.1, and using xml2cmake from it, I get an error about not finding
'PluginVsInstall.cmake'. Would this be hard to configure visit/package.py so that it gets added ?
>
>      Thanks,
>
>      Olivier Cessenat.
>
>      BTW: I managed to build visit 3.1.4 on CentOS 7.8 through spack, but I failed on Ubuntu 18.04
(Python not found..) while build-visit
>
>
>
>
>

---