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 69
    • Issues 69
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 44
    • Merge Requests 44
  • 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
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Core Modules
  • dune-common
  • Issues
  • #210

Closed
Open
Created May 24, 2020 by Simon Praetorius@simon.praetoriusOwner

Move FindPackages for (Par)METIS, SuiteSparse and PTScotch to dune-istl

There are several FindPackages in dune-common that are not used anywhere and also the the dune-common code is not dependent on those packages. Those packages are

  • METIS
  • ParMETIS
  • SuiteSparse
  • PTScotch

METIS and ParMETIS are used in dune-istl and dune-grid, and SuiteSparse is used in dune-istl. Don't knwo where PTScotch is used.

Does it make sense to move the cmake files to the modules where they are actually used?

Edited May 24, 2020 by Simon Praetorius
Assignee
Assign to
New CMake Build-System
Milestone
New CMake Build-System
Assign milestone
Time tracking
None
Due date
None