4 ms·
> navigating the maze that is picking a C runtime, a libc implementation, a compiler or potentially compiler frontend and backend, a linker, a build tool, a dep
by lelanthran 2y ago
> navigating the maze that is picking a C runtime, a libc implementation, a compiler or potentially compiler frontend and backend, a linker, a build tool, a dependency manager, and then figuring out the linking, figuring out the dependency management, figuring out the building process,
You're misrepresenting this somewhat: all but two of those items listed need you to only "pick" a compiler and (as parent said) use Make.
The dependency manager is a problem yes, but lets not misrepresent everything.
- perching_aix 2y agoIt comes up more when you try stuff multiplatform. Another thing I didn't touch on is the massive compatibility tables for language features one needs to look out for, in case they plan to make their code work on multiple mainstream compilers, which is arguably the prudent thing to do. I really don't think that considering the C/C++ build story as complex and frustrating would be misrepresentative.
- lelanthran 2y ago> I really don't think that considering the C/C++ build story as complex and frustrating would be misrepresentative. Who was talking about C++? This thread was about C, right? (It's possible that I didn't read very closely upthread, but I'm almost certain that we were all talking about C). I actually agree that C++ can be a pain in the rear, especially for multiplatform, and you have to pick all your options, etc. But C? Not so much. Even on multi-platform. As GP (or GGP, or GGGP, I forget how far upthread it is) said, with C all you need is a compiler, an editor and Make. That's pretty much still true, even if you're using third party libraries.