https://github.com/cmakepp/cmaize

Simplifies writing CMake-based build systems.

https://github.com/cmakepp/cmaize

Science Score: 39.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
    Found .zenodo.json file
  • DOI references
    Found 1 DOI reference(s) in README
  • Academic publication links
  • Academic email domains
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (14.7%) to scientific vocabulary

Keywords

cmake cmake-best-practices
Last synced: 5 months ago · JSON representation

Repository

Simplifies writing CMake-based build systems.

Basic Info
Statistics
  • Stars: 12
  • Watchers: 3
  • Forks: 12
  • Open Issues: 28
  • Releases: 0
Topics
cmake cmake-best-practices
Created over 7 years ago · Last pushed 7 months ago
Metadata Files
Readme License

README.md

alt text

Documentation link

We believe that the development of build systems should follow the same software engineering best practices as traditional source code. One such best practice is the DRY ("Don't Repeat Yourself") principle. Most build systems written in CMake are extremely verbose and boilerplate heavy. CMaize was developed to facilitate writing CMake build systems which adhere to the DRY principle.

Features

  • Minimize boilerplate. CMake is verbose, CMaize isn't.
  • Pure CMake. CMaize is written using the CMake programming language which means you have access to every feature CMake provides in addition to those provided by CMaize itself.
  • Automatically keep up with CMake's ever changing best practices. CMaize provides a stable API and maintains the mapping from that API to CMake's current best practices.
  • Seamlessly integrate targets that rely on languages not supported by CMake. Currently limited to Python, but can be extended.

Install

If you are using CMaize as part of your project's build system it is recommended that you set up your build system to automatically fetch CMaize. See here for more details.

Contributing

Acknowledgments

This research was supported by the Exascale Computing Project (17-SC-20-SC), a collaborative effort of the U.S. Department of Energy Office of Science and the National Nuclear Security Administration.

Additional funding has come for Iowa State University through the College of Liberal Arts & Sciences Dean’s Professor Chair.

Owner

  • Name: CMakePP
  • Login: CMakePP
  • Kind: organization

Dedicated to making packaging projects with CMake eaiser

GitHub Events

Total
  • Issues event: 4
  • Watch event: 3
  • Delete event: 3
  • Issue comment event: 5
  • Push event: 18
  • Pull request review event: 4
  • Pull request event: 6
  • Fork event: 1
  • Create event: 5
Last Year
  • Issues event: 4
  • Watch event: 3
  • Delete event: 3
  • Issue comment event: 5
  • Push event: 18
  • Pull request review event: 4
  • Pull request event: 6
  • Fork event: 1
  • Create event: 5

Issues and Pull Requests

Last synced: 6 months ago

All Time
  • Total issues: 2
  • Total pull requests: 3
  • Average time to close issues: about 2 hours
  • Average time to close pull requests: about 4 hours
  • Total issue authors: 1
  • Total pull request authors: 2
  • Average comments per issue: 0.0
  • Average comments per pull request: 1.33
  • Merged pull requests: 3
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 2
  • Pull requests: 3
  • Average time to close issues: about 2 hours
  • Average time to close pull requests: about 4 hours
  • Issue authors: 1
  • Pull request authors: 2
  • Average comments per issue: 0.0
  • Average comments per pull request: 1.33
  • Merged pull requests: 3
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
  • ryanmrichard (4)
  • zachcran (3)
Pull Request Authors
  • ryanmrichard (7)
  • zachcran (2)
  • jwaldrop107 (2)
Top Labels
Issue Labels
bug (4) enhancement (2)
Pull Request Labels
bump:minor (1)