Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • VTK VTK
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 833
    • Issues 833
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 236
    • Merge requests 236
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VTKVTK
  • VTKVTK
  • Issues
  • #17604
Closed
Open
Issue created May 16, 2019 by Ben Boeckel@ben.boeckel⛰Owner

The new autoinit CMake API doesn't support header-only libraries

The way that autoinit gets compiled today with vtk_module_autoinit generates private headers and then injects it via private compile definitions. This doesn't work for header-only libraries exposing VTK classes because:

  • it's a private header
  • only going to work in real TU compilations
  • the header doesn't get installed

I'm not sure of the best way to actually fix this, but it should be documented at least that publicly depending on VTK from header-only components requires that consumers call vtk_module_autoinit with…some set of modules defined by the consumed library somewhere. It can't come exclusively from there because using two header-only VTK things should also be supported.

Cc: @brad.king @dzenanz

Assignee
Assign to
Time tracking