Cleanup ParaView installations on Linux.
disable shared forwarding by default and use rpaths. All relevant linux systems now support rpath. ParaView executables should have rpath set to
$ORIGIN/../lib. This will affect how we presently support
--mesa-llvmetc. Need a workaround for that.
don't put libraries under
<prefix>/lib/paraview-$version, instead just use
<prefix>/lib. This will make it easier with putting together ParaView-based application packages. Those other apps, don't need to separately deal with locating ParaView libraries under the version specific directory.
all libraries installed under
<prefix>/libshould be versioned.
all plugins are installed under
sos are not versioned i.e. don't have ParaView version suffix on them. The plugins configuration file (currently
.plugins) should be under this directory as well.
all shared resources e.g. PDFs, config files, icons, appdata etc. should be installed
Python modules including Python-C libraries are installed under
<prefix>/lib/python$pyversion/site-packages(note the absence of ParaView version number).
- make build and install directories as consistent as possible. It's annoying to have to determine if we are running from the build dir or the install location and then do tasks accordingly. Why can't we have them be the same?
- add documentation for what goes where so that we can refer developer to it when adding any new install rules.
make|ninja installtarget works when
- Xdmf install rules are bad (#16871 (closed))
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information