I mean, all cmake does is run some commands for you. You not understanding cmake errors (mostly) means you don’t understand the errors given to you by the C/C++ compiler.
CMake can also emit its own errors during the configure step though, particularly if you have complicated build logic and/or lots of external packages.
I mean, all cmake does is run some commands for you. You not understanding cmake errors (mostly) means you don’t understand the errors given to you by the C/C++ compiler.
Partly, yes. But I also think their documentation is a bit hard do read. Maybe this will get better with time.
I use rust btw.
I use distcc, and do not have to take vacation for my programs to finish compiling.
If it means my code won’t panic out of nowhere and cause a disaster for me, I am willing to “take a vacation” for my program to finish compiling.
Yes, just give it a few more decades.
CMake can also emit its own errors during the configure step though, particularly if you have complicated build logic and/or lots of external packages.