Modern CMake for C++: Effortlessly build cutting-edge C++ code and deliver high-quality solutions

Clear, Comprehensive, Modern, Helpful.Most pleasant surprise: the book covers how to integrate CMake with all the popular tools.A few little typos here and there (eg. page 293).An excellent resource for crafting a mature, reliable CI/CD pipeline for C++ code

Who knew a book about CMake would be 500 pages!? Yes, it is a sign of a mature tool with a broad user base.Frankly despite these years I program less in C++, keeping my projects in an organized way and coherent manner was always, and must be every developers` paramount.In my opinion Modern CMake for C++ will make this happen.As complex as CMake can seem when you approach it, this book manages to digest in so in a piecemeal approach it will settle in very nicely.I struggled in the past with CMake and honestly tried to avoid it. The most difficult part was the language to the point I doubted its usefulness in respect to how much time I spent configuring CMake scripts, but I am not intimidated nor I am doubtful anymore.A general thought, books on tools are as powerful as the tools themselves they teach.Please make an effort and find the time to learn about CMake.

I've been working with some projects that use CMake and I'm not able to understand how I can modify it. This book helped me to understand enough about CMake so I can use it and make the modifications I needed.

This book is an excellent reference and guide to CMake with clear and thorough presentation. A great feature of it is noting on which version each feature was introduced so you decide if you need to update the minimum version in legacy projects. Highly recommended as CMake documentation is thorough but not very easy to digest.

Great Cmake reference. It got me out a mess with one of my applications.

I recently read Modern CMake for C++, Second Edition and was thoroughly impressed. Despite considering myself highly technical and knowledgeable in CMake, I still learned a plethora of new information. The book covers a wide range of topics, from debugging a CMake project, understanding the grammar, targets, and package management like FetchContent, to using CMake in advanced IDEs.One of the standout aspects of this book is its guidance on properly setting up a project. It emphasizes good practices, what to focus on when building a project, the hierarchy, and various gotchas to avoid. The book even delves into the linking models of C and C++ and how to handle them correctly in CMake.This book is a must-read for every developer using CMake. By following the rules and best practices outlined, it will make your project healthier. Regardless of your experience level, you are bound to pick up new skills. The format and organization of this book are simply fabulous, making it highly recommended.

Disclosure: I was provided an early review copy at no expense but these opinions are my own.I've used CMake for several years and know enough to generally make it do what I need it to do. That being said, there's always more to learn. This book is a fantastic resource for a number of reasons.1. It starts from an introductory level with very few assumptions of your current knowledge.2. There are a number of side-notes and tips for best practices that can help provide context for deeper understanding.3. It goes beyond introductory tutorials and explains deeper concepts before ending with a solid summary chapter project.By building on a foundation of basics piece by piece all the way to more complicated topics -- with chapters explaining concepts that I didn't know even after using CMake for years -- I anticipate that this book would be a solid roadmap for beginners to learn how to start effectively using CMake in their projects and for the proficient to at least learn something new.

I have heard through 149 pages of the book, but while it has covered details of the cmake language, propagates properties, and other esoteric topics, it has not covered in detail the compilation process which are upcoming in chapters 7 and 8. I would restructure the material so that common tasks, i.e. creating a project using cmake, setting compilation and linking flags, and linking with libraries whose source codes are not available, are covered early on.I would also pay more attention to security issues. For example, on page 143, the author advises regenerating the automatically generated code files versus checking them in. For security reasons, it may be best to work with one version of code generators (especially the ones you download off the internet such as protoc), visually inspect the generated output, and then check them in.