Become CPS compatible
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 507
- Forks
- 87
- Avg merge
- 15h 27m
- Merged PRs (30d)
- 2
Description
The Common Package Specification enforces the package name to match the namespace of the targets, see https://www.kitware.com/common-package-specification-is-out-the-gate
CPS addresses this by enforcing qualified target names, where the root “namespace” of the target is exactly the name of the package which provides that target. (This is also why existing CMake projects are strongly encouraged to use their package name as their CMake namespace when generating CMake-script exports, as this will reduce porting friction when transitioning to CPS.)
Do you mind if we change the name of the CMake project from "MDSpan" to "mdspan" ?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name a file, so start by locating the CMake project declaration and references to the current “MDSpan” name. Read the linked CPS guidance, then update the project/package naming consistently; done when the project uses “mdspan” and satisfies the stated namespace requirement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 70/100