utest.h
cmake-init
Our great sponsors
| utest.h | cmake-init | |
|---|---|---|
| 3 | 164 | |
| 1 | 1,827 | |
| - | - | |
| 0.0 | 8.1 | |
| over 2 years ago | 9 days ago | |
| C | CMake | |
| The Unlicense | GNU General Public License v3.0 only |
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.
utest.h
-
what's the hate for CMake all about? Is CMake really that bad?
I would say simple things are simple. CMake does use RPATH on RPATH compatible platforms, there is no need to copy DLLs. In fact, if the DLL depends on assets relative ot its location now you are just digging a deep hole for yourself for no good reason. On platforms where RPATH is not supported (Windows), you should make DLLs available via PATH, which Just Works tm. This is a shortcoming of Windows. You are free to forward your complaints to Microsoft. Regardless, here's some help with the PATH thing.
-
GitHub - Snaipe/Criterion: A cross-platform C and C++ unit testing framework for the 21st century
This fork of it has proper CMake integration and provides a module for automatic test discovery with the unique ability to handle DLL finding for you on Windows, which is documented here.
cmake-init
-
CMake install schema for single- and multi-config generators
https://github.com/friendlyanon/cmake-init This is how you do CMake properly. If you deviate from its install rules you are highly likely to do something wrong.
-
cgen: another declarative CMake configuration generator
CMake itself is as declarative as a build systems need to be. For anything nontrivial, these "declarative" solutions all fall apart. Just use https://github.com/friendlyanon/cmake-init, learn CMake and you won't have any issues.
-
How does one actually build a C++ project
If you want something with a (mostly) Just Works experience then just use https://github.com/friendlyanon/cmake-init
- CMakeList.txt, add_executable vs. add_library vs. target_link_libraries vs. target_link_directories
- Check out my tasks.json for C++ of VScode
- Clang++ Halp
-
Putting libraries in program folder
For CMake basics check out the official "Getting started" tutorial: https://cmake.org/cmake/help/latest/guide/tutorial/index.html, as well as Introduction to Modern CMake. You can also get inspired by the CMake project generator cmake-init
- Recourses to help understand libraries/projects and setting them up?
-
How to Create a Modern C Project with CMake and Conan
You can just use https://github.com/friendlyanon/cmake-init to get a CMake + Conan C project ready to go with a short little command: cmake-init --c -e -p conan coolio
- CMake template
What are some alternatives?
utest.h - 🧪 single header unit testing framework for C and C++
meson - The Meson Build System
Vcpkg - C++ Library Manager for Windows, Linux, and MacOS
w64devkit - Portable C and C++ Development Kit for x64 (and x86) Windows
xmake - 🔥 A cross-platform build utility based on Lua
fastbuild - High performance build system for Windows, OSX and Linux. Supporting caching, network distribution and more.
ModernCppStarter - 🚀 Kick-start your C++! A template for modern C++ projects using CMake, CI, code coverage, clang-format, reproducible dependency management and much more.
llvm-mingw - An LLVM/Clang/LLD based mingw-w64 toolchain
dockcross - Cross compiling toolchains in Docker images
conan - Conan - The open-source C and C++ package manager
CMake-VSCode-Tutorial - Template and short tutorial on how to setup an integrated environment for VS Code and CMake (Doxygen and ClangFormat ready)
pitchfork - Pitchfork is a Set of C++ Project Conventions