If you are maintaining a C++ library, there is very little way to get around using CMake, as it's the de-facto standard (meta) build system for cross-platform development.
Writing good CMake build files for libraries makes all the differences, if a library integration goes smoothly or ends up being a huge hassle for the user of the library.
While integrating numerous (>100) open source libraries for inhouse usage, I have seen and learned alot about how (and how not) to write good CMake Code.
In this talk, we will touch upon some fundamental concepts, that result in clean CMake code, useful for any developer using CMake.