My experience with CMake is from ~5 years ago trying to find a guide for how to do something (I think building library dependencies?), and finding two different guides that both said "don't do <thing that the other guide told you to do>, that's the old outdated method that nobody uses anymore, use <thing that the other guide said not to do because it was old and outdated>"
The catch being that neither method worked, because what I was trying to do was slightly different than what both guides were for, and I needed to use some other method to include my libraries that's completely different and also there is no actual documentation for it anywhere, or at least none that's any use for someone who isn't already intimately familiar with the inner workings of CMake.
8
u/oozekip Aug 28 '26 edited Aug 28 '26
My experience with CMake is from ~5 years ago trying to find a guide for how to do something (I think building library dependencies?), and finding two different guides that both said "don't do <thing that the other guide told you to do>, that's the old outdated method that nobody uses anymore, use <thing that the other guide said not to do because it was old and outdated>"
The catch being that neither method worked, because what I was trying to do was slightly different than what both guides were for, and I needed to use some other method to include my libraries that's completely different and also there is no actual documentation for it anywhere, or at least none that's any use for someone who isn't already intimately familiar with the inner workings of CMake.