This lecture goes slightly in-depth in places. Don't worry! You won't have to do any of this manually! We will be using some build system like CMake or bazel for this. But to understand how those work it helps immensely to know what happens under the hood. 😜 Are you sold on this notion?
Yes absolutely!! I’ve never understood what Cmake is actually doing. I often get stuck during build errors. I would love to understand what actually goes on under the hood
I completely agree, thanks for the lecture! It would be very helpful imo if you could do an entire lecture dedicated to CMake and more in general on how to structure a project (probably there is no general way then some different examples of architectures would be required). Do you plan on doing something like that?
Yeah, I tried my best to be concise but still explain most of the stuff I wanted to explain. It's still not perfect, but I can always come back to it in the future and make it better 😉
@@CodeForYourself okay I'm too much of a beginner. I think I understand the tradeoffs of different types of libraries. Header only libs makes the devs life simple. But if you want to hide the implementation then they wont work.
@@ChimiChanga1337 yes, you are exactly right! Also, header only libraries, when we have many of them, make compilation waaay too slow. With compiler libraries we are able to often compile them once and link all over the place. Does this make sense?