Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
ParaView
ParaView
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,670
    • Issues 1,670
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 61
    • Merge Requests 61
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ParaView
  • ParaViewParaView
  • Issues
  • #18751

Closed
Open
Created Feb 04, 2019 by Mathieu Westphal@mwestphalDeveloper

Installation conflict between VTK and ParaView

When installing ParaView with Python enabled in the default directory, it contains a lot of python related files in : lib64/python3.7/site-packages/vtkmodules

which includes, for example : vtkCommonDataModel.py

These files are conflicting with files generated by VTK installation.

There are two possible fixes imo :

  • Adding the possibility to build ParaView with an external VTK. This has been requested but it seems to be quite hard to do.
  • Adding a suffix to all these files

@ben.boeckel: this is not related to the current changes to the module system, but if you have an idea how to fix this that would be great.

@michael.migliore @mike.rye

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