meson-brainfuck
A proof that Meson is actually Turing-Complete (by xorvoid)
cmake-init-use-pkg-config
Using a dependency that does not support clients using CMake (by friendlyanon)
Our great sponsors
| meson-brainfuck | cmake-init-use-pkg-config | |
|---|---|---|
| 4 | 2 | |
| 10 | 4 | |
| - | - | |
| 0.0 | 2.6 | |
| over 4 years ago | over 2 years ago | |
| Meson | CMake | |
| - | - |
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.
meson-brainfuck
Posts with mentions or reviews of meson-brainfuck.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-04-17.
-
A proof that Meson is Turing-Complete
As other top-level comment indicates, this is debatable: https://github.com/xorvoid/meson-brainfuck/issues/1
-
Good reasons to NOT use CMake
Meson is not capable enough. It lacks ways to create abstractions. It also advertises itself as not being turing complete, which is not only unimportant, but also false.
-
Registries: Bring your own libraries to vcpkg
What about: https://github.com/xorvoid/meson-brainfuck :P
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.
What are some alternatives?
When comparing meson-brainfuck and cmake-init-use-pkg-config you can also consider the following projects:
cppfront - CMake wrapper around the cppfront repository
cmake-init - The missing CMake project initializer
ProxImaL - A domain-specific language for image optimization.
cmake-init-fetchcontent - Example for optionally vendoring using FetchContent
meson - The Meson Build System
cmake_format - Source code formatter for cmake listfiles.
nsbuild
meson-brainfuck vs cppfront
cmake-init-use-pkg-config vs cmake-init
meson-brainfuck vs ProxImaL
cmake-init-use-pkg-config vs cmake-init-fetchcontent
meson-brainfuck vs meson
cmake-init-use-pkg-config vs cmake_format
meson-brainfuck vs nsbuild
cmake-init-use-pkg-config vs ProxImaL
cmake-init-use-pkg-config vs cppfront