Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • VTK-m VTK-m
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 193
    • Issues 193
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 37
    • Merge requests 37
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VTK
  • VTK-mVTK-m
  • Issues
  • #609
Closed
Open
Created Mar 01, 2021 by Ben Boeckel@ben.boeckelOwner

Find dependencies in VTKmConfig.cmake

VTK-m currently tries to create its own imported targets for external packages. This does not work in VTK because VTK intends to test things in different directories than is available when being built. This means that the locations found at build time are not useful at find_package() for install time and cannot be exported as LOCATION settings on the IMPORTED targets like vtkm::tbb. Instead, VTK-m should provide INTERFACE targets which chain to IMPORTED targets found at find_package(VTKm) time. VTK-m can ship its Find modules as needed.

Cc: @robertmaynard @kmorel

Assignee
Assign to
Time tracking