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,846
    • Issues 1,846
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 87
    • Merge requests 87
  • 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
  • #19134
Closed
Open
Created Jun 27, 2019 by Joshua Levine@jalevine

pvpython support for plugins in .app layouts and classic unix-style layouts

This issue is about the default search path for plugins on pvpython, particularly when compiled on MacOS

It seems the standard behavior is for pvpython to look for plugins using linux-style paths (e.g. lib/paraviewX.Y/plugins). By comparison, when ParaView is compiled as a .app, the default location for plugins is embedded in the .app (e.g. paraview.app/Contents/MacOS/plugins is reported by Tools->Manage Plugins). Plugins installed and working correctly for ParaView thus are not seen by pvpython.

I understand the build system for ParaView master is changing, but it would be useful to enable a consistent location for plugins across paraview/pvpython and across operating systems.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking