4 ms·
Use a 3rd party tool to generate... autotools "scripts", that's the best compromise IMHO... build tools are not a solved problem yet, you'd think it would be pr
by throw_m239339 6y ago
Use a 3rd party tool to generate... autotools "scripts", that's the best compromise IMHO... build tools are not a solved problem yet, you'd think it would be priority #1 for the dev world but no...
Ultimately, devs shouldn't have to suffer to build C or C++ programs like that. Why is building executables so hard like even today? Developers need to solve that problem once and for all. Containers aren't the solution.
- justinclift 6y ago> Use a 3rd party tool to generate... Isn't that a case of "now you have two problems"? :)
- hulitu 6y ago> > Use a 3rd party tool to generate... > Isn't that a case of "now you have two problems"? :) No. Now you have 3 problems: the 3rd party and the tool.
- josefx 6y agoMore than that, after all we already generate make files. So it is 3rd party -> auto tools -> Makefile. Every step in this chain probably adds another layer of obfuscation to any build error you encounter.
- baby 6y agoI think most of the engineering has moved towards things like Cargo for Rust or Go for Golang.