Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
D
dune-common
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 70
    • Issues 70
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 51
    • Merge Requests 51
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Core Modules
  • dune-common
  • Merge Requests
  • !888

Open
Opened Nov 04, 2020 by Simon Praetorius@simon.praetoriusOwner
  • Report abuse
Report abuse

WIP: cmake tests

  • Overview 2
  • Commits 3
  • Pipelines 1
  • Changes 9

Summary

Add facility to test cmake modules.

Details

We write a lot of find modules and add them to dune-common or any other dune module. Not always is the find modules used in the dune-module where it belongs to. Nevertheless, it would be good to test these modules also if not called in any CMakeLists file in the regular cmake. One way of doing this it to use a custom cmake test command that configures, builds and runs an independent cmake project containing the find module to test.

Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Reference: core/dune-common!888
Source branch: feature/cmake_tests