From: Cosmin T. <co...@cs...> - 2014-01-18 18:08:42
|
On Fri, Jan 17, 2014 at 6:05 PM, John Bowler < joh...@gm...> wrote: > I would prefer just one build method for each IDE; I consider configure and cmake to be IDEs. This would mean eliminating scripts/makefile* wherever the corresponding system is supported by configure or cmake in 1.7 In my proposal, I removed the specific scripts that are handled by configure, and I kept the generic ones, as well as the ones outside of configure's applicability. Considering what constitutes an IDE, it's a matter of taste, I guess. configure and cmake certainly have their powers, but they make too many simple things complicated, at least for my taste. Their learning curves are way too steep, which is the opposite of what an IDE is supposed to help with. CMake covers more platforms and environments, but unlike configure, it is black-boxed, and even harder to figure out when I need to make a small change, or a small fix, or work around its plethora of implicit rules. My personal opinion, of course. > makefile.std is, however, useful because it helps on systems we don't know about. I agree with you on that, which is why I kept it. But it would be unfair to keep makefile.std and erase makefile.acorn or makefile.bc32, wouldn't it? See: https://bitbucket.org/ctruta/libpng-cos/commits/551b10c21c https://bitbucket.org/ctruta/libpng-cos/commits/5419f70bd9 Sincerely, Cosmin |