https://github.com/krux02/minimal_cmake_example

this tries to be a minimal cmake example, that covers sources resources dependencies and packaging.
https://github.com/krux02/minimal_cmake_example

Last synced: about 2 months ago
JSON representation

this tries to be a minimal cmake example, that covers sources resources dependencies and packaging.

• Host: GitHub
• URL: https://github.com/krux02/minimal_cmake_example
• Owner: krux02
• License: cc0-1.0
• Created: 2015-10-12T21:31:55.000Z (over 8 years ago)
• Default Branch: master
• Last Pushed: 2019-01-17T15:23:32.000Z (over 5 years ago)
• Last Synced: 2024-02-01T16:09:25.474Z (5 months ago)
• Language: CMake
• Size: 8.79 KB
• Stars: 178
• Watchers: 10
• Forks: 44
• Open Issues: 2
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Lists

• awesome-cmake - minimal_cmake_example - Minimal CMake example, that covers dependencies and packaging. [```[CC0-1.0]```][CC0-1.0] (Examples / Templates)

README

        
# 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.