All Projects → krux02 → Minimal_cmake_example

krux02 / Minimal_cmake_example

Licence: cc0-1.0
this tries to be a minimal cmake example, that covers sources resources dependencies and packaging.

Labels

Projects that are alternatives of or similar to Minimal cmake example

Cmake
A set of cmake modules to assist in building code
Stars: ✭ 127 (-10.56%)
Mutual labels:  cmake
Hlslib
A collection of extensions for Vivado HLS and Intel FPGA OpenCL to improve developer quality of life.
Stars: ✭ 131 (-7.75%)
Mutual labels:  cmake
Cmake
Common CMake modules
Stars: ✭ 137 (-3.52%)
Mutual labels:  cmake
Warzone2100
Command the forces of The Project in a battle to rebuild the world after mankind has been nearly destroyed by nuclear missiles. A 100% free and open source real-time strategy game for Windows, macOS, Linux, BSD+
Stars: ✭ 2,094 (+1374.65%)
Mutual labels:  cmake
Racecar gazebo
A gazebo-based simulator of the MIT Racecar.
Stars: ✭ 130 (-8.45%)
Mutual labels:  cmake
Notepanda
📃 A simple cross-platform notepad. Based on Qt and C++.
Stars: ✭ 134 (-5.63%)
Mutual labels:  cmake
Openage
Free (as in freedom) open source clone of the Age of Empires II engine 🚀
Stars: ✭ 10,712 (+7443.66%)
Mutual labels:  cmake
Reggae
Build system in D, Python, Ruby, Javascript or Lua
Stars: ✭ 141 (-0.7%)
Mutual labels:  cmake
Cmake Example
Example project which demonstrates various CMake features.
Stars: ✭ 131 (-7.75%)
Mutual labels:  cmake
Cmakeprotosgrpc
gRPC + protobuf using CMake example
Stars: ✭ 137 (-3.52%)
Mutual labels:  cmake
F4mp
Stars: ✭ 130 (-8.45%)
Mutual labels:  cmake
Limited Systems
Limited Systems
Stars: ✭ 132 (-7.04%)
Mutual labels:  cmake
Blt
A streamlined CMake build system foundation for developing HPC software
Stars: ✭ 135 (-4.93%)
Mutual labels:  cmake
Ffmpeg Development Kit
Stars: ✭ 127 (-10.56%)
Mutual labels:  cmake
Cmake Avr
cmake toolchain for AVR
Stars: ✭ 137 (-3.52%)
Mutual labels:  cmake
Opencv4androidwithcmake
Use Android Studio 3.0 (>=2.2) and Cmake Toolchain to make your Android device fly with Opencv (OpenCV 3.40)
Stars: ✭ 126 (-11.27%)
Mutual labels:  cmake
Gemm hls
Scalable systolic array-based matrix-matrix multiplication implemented in Vivado HLS for Xilinx FPGAs.
Stars: ✭ 134 (-5.63%)
Mutual labels:  cmake
Multi Rtl
Multi-channel receiver with use of RTL-SDR dongles
Stars: ✭ 142 (+0%)
Mutual labels:  cmake
Rttr
C++ Reflection Library
Stars: ✭ 2,031 (+1330.28%)
Mutual labels:  cmake
Sdl2 Examples
Examples for getting started with SDL2, for over 12 different programming languages
Stars: ✭ 136 (-4.23%)
Mutual labels:  cmake

Minimal CMake Example

This project tries to be a minimal cmake example. It covers sources, resources, dependencies and packaging.

I created this project, because I think the official documentation of CMake is not the best. It avoidids talking about the actually important parts to setup a new project, but instead explains and focuses on unnecessary fuss like how to write configuration headers.

I think that a configuariton headers are something you shouldn't do at all. In my opinion the project should just compile the source without any magic happening. Generating configuration headers just makes the build unnecessarily complicated, and tools that work on the source code get a harder job. I also disagree that every source folder should have it's own CMake file. I think when there is no really good reason do do it otherwise, one CMake file should be enough for the entire project. In one file you should be able to see everything that is important to build all parts of the project. This information should not be scattered around in different source folders within the project.

build can fail because of boost

The build of this project might fail, when CMake does not find boost. This does not mean that there is an error in the CMakeLists.txt file, it just means, that CMake could not find boost in your system. You can simply remove the boost dependency, if you don't want or need it. Or you could tell CMake where to find boost with ccmake or cmake-gui. It's just there to serve as an example, how you could declare dependencies that you do not distribute with your project.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].