I’ll explain myself. I’m doing a small project using a few dependencies, so I have to add them when I call gcc. Everything else is really easy. I just have c files and header files. I find it really cumbersome to have to tell make what headers go with what c files when they have the same name. I don’t see why we don’t have a build system where you simply have to give a project folder with the name of source file with the main() function, give the name of the output executable, the external dependecies to be called with gcc, and that’s it. Everything else can be automatically detected and linked apropriately, even with multiple folders inside the project folder. Does something like that exist that’s simple to use, or is this doable in make?
But we do. Check out CMake.
https://cmake.org/examples/
Originally CMake was a higher level abstraction over make, and generated makefiles based from the high-level project description. Nowadays it supports other build automation tools, such as Ninja, Visual Studio, Xcode, etc.
Ah cmake. Boring but definitely works reliably for C/C++
What do you mean by “boring” ?
It’s boring like a good tool should be: does what it says. No fuss. No cloud of hype.