cmake-init-executable
cmake-init
Our great sponsors
cmake-init-executable | cmake-init | |
---|---|---|
7 | 1 | |
18 | 904 | |
- | 1.8% | |
6.1 | 0.0 | |
14 days ago | 6 months ago | |
CMake | CMake | |
- | MIT License |
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-executable
-
Learning CMake on Windows with ArmCC
Then you can pass this to the configure command using the --toolchain flag. If you keep the embedded specific details far far far away from your CMakeLists files, then you get an otherwise completely normal CMake project that supports building for the host platform as well. This comes with the benefit that you can write the business logic in a separate object library target, which tests can consume and run on the host. You can see that in action here: https://github.com/friendlyanon/cmake-init-executable
-
What exactly does CMake output?
You can take a look at an example workflow with CMake using presets here.
-
a bootloader as both executable and library
This example is similar to what you need in structure sans the executable at the top level.
-
Using Xmake for C/C++ Program Development in VSCode
Besides, a CMake project that focuses only on building something doesn't need more than a CML file. If you compare the baseline with a fully populated cmake folder (https://github.com/friendlyanon/cmake-init-executable) and this one https://github.com/friendlyanon/generate-opaque-structs then you can see that you don't need anything from the baseline, but it's all very useful stuff that everyone should use.
-
how to ignore main() when testing functions from main.c?
You make the entrypoint as minimal as possible and develop the actual application logic basically as a library. This example - while being C++ - shows you how to do that. You can generate the exact same project with the tool linked in the README with the --c switch for a C project.
-
Thoughts on build systems?
Ah, you mean flashing as in download. You can create a custom target for that, like in this example. Do note that the example allows complete customizability of the commands, because the developer environment isn't necessarily identical for everyone.
-
how to pack each subfolder separately with cpack?
You create separate install components for them and then you can control how those components are packed using CPACK_INSTALL_CMAKE_PROJECTS.
cmake-init
-
Using Xmake for C/C++ Program Development in VSCode
It's easier to list what is not wrong about CMake. The only positive thing about CMake is that it works once you spend days or weeks ripping your hair out trying to configure it. cmake-init is a perfect example of what is wrong with it. Over 400 commits, lots of files to properly start a project. No other language does that, because it is unspeakably bad.
What are some alternatives?
CIDLib - The CIDLib general purpose C++ development environment
utility-boilerplate-qt - 🚀Boilerplate for C++ utility application based on Qt5
new_cmd - A batch file to help scaffold a simple build system for C++, C or Python.
cmake-sfml-project - Repository template for SFML projects using CMake
Kowloon-Simulator-2020
generate-opaque-structs - Example to show how to generate opaque structs with proper size and alignment
cmake-init-clang-on-windows - Using LLVM Clang on Windows with CMake
ModernCppStarter - 🚀 Kick-start your C++! A template for modern C++ projects using CMake, CI, code coverage, clang-format, reproducible dependency management and much more.
xrepo-cmake - CMake wrapper for Xrepo C and C++ package manager
CPM.cmake - 📦 CMake's missing package manager. A small CMake script for setup-free, cross-platform, reproducible dependency management.
cmake-init - The missing CMake project initializer