OpenAssetIO / OpenAssetIO/OpenAssetIO
Consistent CMake coding standards across projects
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 348
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
Ensure CMake style is consistent across projects. Note that linting is handled in a separate issue: #1132
This may involve building out a common set of CMake utilities.
But more likely just means that similar CMake tasks are accomplished in a similar way across projects, so that it's easier to grok one project given familiarity with another, and easier to copy-paste and customise snippets from one project to another.
Contributor guide
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
No files, tests, or entry points are named. Start by comparing the CMake setup across the repository's projects and review issue #1132 to keep linting out of scope; agree on the common standards and utilities before defining completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100