I have been writing code for 35 years. I got my first job writing C++ 30 years ago. Please feel free to open an issue and ask questions.
When studied line drawing errors in C++ over 30 years ago, I didn't know why the author of the book would not have noticed the error. The author of Game Programming in C++ (a massive book nearly 1,000 pages), kindly offered for people to write him about any mistakes in the book. I just didn't have any explanation as to why the line was drawn not staright in appearance at the end of it in the classic game programming book. I know that games then evolved into using sprite graphics to ensure quality image. We saw the strange not straight lines again with 3D graphics in early 3D games.
I know that game programming is different than other programming. When we are learning how to develop in new areas than we have before, we like to see the correct answer before we can relax into a new sense of accomplishment in new confidence. Developing code is not like playing video games, and I think this is part of the reason why the better games are capable of drawing some graphics without complete accuracy in their implementation, while having the effect of enhancing player experience. This is really where the art of writing C++ code can be for some. If the code here, or explanations are not accurate, please let me know.
I like using cmake. I have first increased the cmake versioning before stepping up the C++ versioning for a build philosophy that will be more reliable.
innacuracies may exist. please open an issue.