cmake-init-use-pkg-config
Using a dependency that does not support clients using CMake (by friendlyanon)
cmake_format
Source code formatter for cmake listfiles. (by cheshirekow)
Our great sponsors
cmake-init-use-pkg-config | cmake_format | |
---|---|---|
2 | 2 | |
4 | 925 | |
- | - | |
2.6 | 0.0 | |
over 2 years ago | 2 months ago | |
CMake | Python | |
- | GNU General Public License v3.0 only |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cmake-init-use-pkg-config
Posts with mentions or reviews of cmake-init-use-pkg-config.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-11-14.
-
Good reasons to NOT use CMake
You have to realize that the point of using CMake is not entirely about your project, but about downstream users who wish to use CMake as well. If you do not support clients using CMake (i.e. install a CMake package) you are forcing every downstream user to figure your requirements out by themselves, which even for a project with no dependencies is non-trivial: https://github.com/friendlyanon/cmake-init-use-pkg-config
-
cmake-init - The missing CMake project initializer, now with Conan and vcpkg templates!
See this example from the wiki. This one tries to use unofficial vcpkg package nd targets, then falls back to pkg config, then falls back to find_* commands. This is probably more than what you are asking, but you can put anything in the find module, even code that vendors projects, although I highly recommend against any form of vendoring (manual, git, FetchContent, etc). Vendoring only causes problems for packagers.
cmake_format
Posts with mentions or reviews of cmake_format.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-07-12.
-
What about a CMake transpiler?
There's a cmake-format project with some linting features, but it's hard to add the checks to clean up the biggest CMake antipatterns because relevant solutions tend to be more opinionated in one direction or another.
-
cmake-init - The missing CMake project initializer, now with Conan and vcpkg templates!
Have you considered integrating cmake-format? It requires an extra dependency of course, but you can make it optional.
What are some alternatives?
When comparing cmake-init-use-pkg-config and cmake_format you can also consider the following projects:
cmake-init - The missing CMake project initializer
cmake-init-fetchcontent - Example for optionally vendoring using FetchContent
Python Packages Project Generator - 🚀 Your next Python package needs a bleeding-edge project structure.
meson-brainfuck - A proof that Meson is actually Turing-Complete
ProxImaL - A domain-specific language for image optimization.
premake-cmake - cmake output for premake5
cppfront - CMake wrapper around the cppfront repository
cmakepp - An Enhancement Suite for the CMake Build System
honcho - Honcho: a python clone of Foreman. For managing Procfile-based applications.
cmake-init-use-pkg-config vs cmake-init
cmake_format vs cmake-init-fetchcontent
cmake-init-use-pkg-config vs cmake-init-fetchcontent
cmake_format vs Python Packages Project Generator
cmake-init-use-pkg-config vs meson-brainfuck
cmake_format vs cmake-init
cmake-init-use-pkg-config vs ProxImaL
cmake_format vs premake-cmake
cmake-init-use-pkg-config vs cppfront
cmake_format vs cmakepp
cmake_format vs honcho