Triangles in action! CMake beginner

It says that the target audience is beginners to cmake, but I think it's a good lecture for those who have used languages that use a build system and are wondering, "What exactly is this when I'm told to do cmake?" The content itself is clean and I feel like it's trying to convey only the key points. My main language is Python, so I listened to it as a general lecture, but it was easy to understand because it started from the big picture. The examples are also in the order of problem situation assumption -> solution -> significant section specification, so it was easy to get a feel for it. The github link was broken, so I had a little trouble, but I'll leave the link so that others can do it right away. https://github.com/daemyung/practice-cmake And in the case of Windows, there is no example for specifying the build system in the middle, but I installed vs2022 and proceeded with cmake -G "Visual Studio 17 2022" It's listed by version in the cmake help, so I think you can do it by looking at that.

The editing is neat, and the teaching skills (pronunciation, speaking speed, examples, etc.) are also very good. The answers to questions are also very quick👍 I think I got started with CMake very efficiently!

It was hard to find CMake lectures, so I'm so happy to see them here! I'll study hard. ㅎㅎ

It was very helpful that you explained CMake from the basics.

I have definitely learned the basics of CMake. Thank you.

Among the numerous options that cmake provides, only the commands that are actually used frequently are covered. Because of this, the lecture length is short and only the core contents are included, so it was easy to take the class and it was good. I didn't know how to use a single cmake command using the cmake extension provided by vscode, but I definitely learned it this time.

I listened to the lecture very well. I wish there was a dynamic library section in the CMake practical section. Additional) Questions Changing static to shared in add_library is not the end. In the actual code, codes for dynamically loading libraries (dlopen, LoadLibrary, etc.) must be branched and added for each platform, and additional dependencies such as CMAKE_DL_LIBS and windows.h are also needed to use that function. I am curious about how to organize platform branching while dynamically loading Shared Libraries in the runtime in the modern CMake style. If platform branching is too trivial, I think we need at least a dlopen lecture on Shared Libraries based on Linux. It is not difficult to make it work, but it is difficult to make it well, so I am curious.

It helped me a lot in learning the basic concepts.