coderefinery/cmake

CMake lesson material.

CMake lesson

• Credit and license

cmake's Issues

Replace the weather/fruit examples with more real life examples

"make test" not visible in parent scope

Testing CMake source code should rather be included via include().

Add WORKING_DIRECTORY to git hash example

Compare qmake and CMake and snakemake

Be clear on where to make the build directory

Some make the build directory under src. CMake then only sees the CMakeLists.txt under src and not the hierarchy of CMakeLists.txt

Simplify fizz-buzz example

We can simplify this even further to crystallize out the CMake aspects and to not waste any time on understanding what this code is about. I am working on this this week, just FYI @blindij

Include formative assessment questions at the end of each episode

refer to https://github.com/coderefinery/git-intro/issues/129 for details

Motivate better why CMake if already using Make.

E.g. check out https://prateekvjoshi.com/2014/02/01/cmake-vs-make/.

Change license from CC-BY-SA to CC-BY

Motivation (discussion on the Carpentries mailing list): https://carpentries.topicbox.com/groups/discuss/Td64229aeb252a027

In short, the motivation is to simplify reuse for those who wish to take parts of our lessons and remix them into material which is CC-BY.

At the team meeting 2019-08-12 we have decided to change the license to CC-BY provided that all contributors to this lesson material agree to this change.

This issue will track the progress of this change.

Consider extending to a 1-day workshop

Consider taking it out of the default workshop and turn it into a separate 1-day workshop which can be coupled with a 1-day workshop on mixed-language development.

Section about build directly structure

@blindij I am worried that this section might not be helpful for beginners. IMO one very rarely builds for several platforms at the same time (I have never done that) and this is something that novices should IMO not worry about. We want cross-platform but typically we build only for the platform where we are on. I would remove that section.

In 02-hello-world.md binary changes between "hello" and "hello.x"

@blindij I would stick with "hello.x" throughout to avoid confusion. It is currently not consistent.

Show how to define compiler flags per target or per file

Just a reminder for myself.

POST_BUILD example in 03-hello-world-cmake

@blindij I think I see why you want to show it but this might motivate people to do this in their projects. If one needs to change the build directory structure, then this is probably a better way: http://stackoverflow.com/a/6595001

Simplify find_packages example

Currently we have TBB and Armadillo but I am not sure too many participants can relate to these libraries. I am brainstorming about a simpler example where we possibly detect a package or library that we have created ourselves. I am brainstorming/working on this this week @blindij.

Consider showing some language constructs

They have disappeared to make room for find_package but it would be good to show them somewhere, integrated in an example, passively.

Compiler flags and find family

@blindij I suggest to keep compiler flags and find family in different sections so that both are easier to find. They are relatively unrelated. But of course both super useful. Also there seems to be a leftover 09-find-familiy. I agree that the find family should be mentioned before the break.