3 ms·
> run "make" for many C projects. This generally fails miserably, in my experience. It's normally a dance of error: libfoo missing, followed by install (which
by disgruntledphd2 1y ago
> run "make" for many C projects.
This generally fails miserably, in my experience. It's normally a dance of error: libfoo missing, followed by install (which is generally only straightforward on linux), followed by libbar is missing etc.
Don't get me wrong, I have built lots of non-trivial C projects, but it's not straighforward at all (maybe if you always work in C it's easier).
- johnisgood 1y agoI don't like autotools, but I suppose that would be a good fit here, and perhaps proper pre-build instructions (e.g. "pacman -S libfoo").
- disgruntledphd2 1y agoTotally, autotools helps. However, it's generally dependency issues that cause the problems, you're missing some header files etc. Finding out about these at configure time is better, but there's still a bunch of toil in identifying and getting those dependencies.