CheckInstall VS CMake

Checkinstall to create deb or rpm package out of source installs which you can easily remove with your package manager again. (But this only keeps track of the installed files, doesn't do any dependency tracking). Source: over 2 years ago

There is also checkinstall which you run instead of make install. It creates a (simple) RPM package for you. You can remove that package with your package manager later on for easy uninstallation. Source: almost 3 years ago

Checkinstall is a rather popular way of dealing with self compiled packages. Source: about 3 years ago

CMake stands for "Cross-platform Make" and is an open-source, platform-independent build system. It's designed to build, test, and package software projects written in C and C++, but it can also be used for other languages. Here's an overview of CMake and its features:. - Source: dev.to / 2 months ago

When doing research for this lab exercise I looked at both vcpkg and conan. Both are package managers that would automate the installation and configuration of my program with its dependencies. However, when it came to releasing and sharing my program my options were limited. For example, the central public registry for conan packages is conan-center, but these packages are curated and the process is very... - Source: dev.to / 5 months ago

Install the CMake program using your system package manager, e.g. Sudo apt-get install cmake. Source: 7 months ago

Oh I just assumed it was talking about the one from cmake.org since I was having trouble. I can now confirm that mingw-w64-cmake and the binary from cmake.org do operate in mostly identical ways. Source: about 1 year ago

Then looking at any one of the many examples provided on cmake.org, it's clearly a viable way to do set(CMAKE_*), (e.g., set(CMAKE_CXX_STANDARD 11) Set(CMAKE_CXX_STANDARD_REQUIRED True)). Of course, another way to set these variables is to use the -D flag as you suggested, but I was just wondering why you would prohibit using set(CMAKE_*). Source: about 1 year ago