cmake-init-multi-target VS xmake

But also a lot of problems come from people not understanding that regardless of CMake and C++, how shared and static libraries work and why they work the way they work. For example, if your CMake project has multiple targets, one being the main export and another being just a "utilities" target of sorts, then you must do some extra work to make the main export target be installed properly when it is built as a static library. This has nothing to do with CMake or C++, but that fact that static libraries are "just" archives of object files that the linker will later roll into a "real" binary (shared library or executable). When you are creating a project you must account for propagating the "utility" target as well, because otherwise the consuming project will not get the code for the "utility" target that was linked to your main export PRIVATEly. I created an example repository on how to deal with this, because a Conan package maintainer was curious about why CMake was inserting $ genex into the installed export set.

In recent times I prefer Xmake[0] to CMake.

[0] https://xmake.io