Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • ParaView ParaView
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,848
    • Issues 1,848
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 93
    • Merge requests 93
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ParaView
  • ParaViewParaView
  • Issues
  • #16870

Closed
Open
Created Aug 31, 2016 by Utkarsh Ayachit@utkarsh.ayachit⛰Owner7 of 10 tasks completed7/10 tasks

Cleanup ParaView installations on Linux.

Refactoring tasks:

  • 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-llvm etc. 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>/lib should be versioned.
  • all plugins are installed under <prefix>/lib/paraview-$version/plugins. Plugins 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 <prefix>/share/paraview-$version.
  • 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.
  • ensure that make|ninja install target works when BUILD_DOCUMENTATION is ON.

Other issues:

  • Xdmf install rules are bad (#16871 (closed))
Edited Jun 01, 2020 by Ben Boeckel
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking