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,858
    • Issues 1,858
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 97
    • Merge requests 97
  • 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
  • #19320
Closed
Open
Created Sep 11, 2019 by Cornelis Bockemühl@coboContributor

Expose VTK modules cmake option in ParaView cmake advanced option

When building ParaView, it not possible to trigger the build of VTK modules that are not needed by ParaView.

It would be very practical to expose the VTK_MODULE_ENABLE_VTK_* VTK cmake option in ParaView cmake options.

Anyone would have the liberty to enable any VTK modules and Provide them in their own ParaView based application without needing to patch ParaView in any way.

Edited Sep 12, 2019 by Mathieu Westphal
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking