I have used AutoTools for my or others' projects as well in the past, and find 
AutoTools quite stable, albeit sometimes cryptic to configure at times.

I've tried educating myself with CMake, but found only low-level documentation 
packaged with or available via CMake's website.  All CMake's other third party 
documentation costs, or are supposedly inadequate.  Unfortunately or 
fortunately, CMake is still unusable at my end of the user spectrum.  As to 
Python being popular due to multi-platform use (and slow when compared to 
C/C++/Bash Scripting); CMake is similar, providing cross-platform use.

CMake is basically a wrapper around Make, so I do not expect to see the same 
inadequacies I see with Python, except for maybe adhering to standards.  Python 
constantly has been known to break standards in the past.  I do not know what 
standards CMake follows, nor if they've broken any with version releases.

When I code, I tend to go with what tools others' are commonly using, which 
tends to be tools that are most stable and lowest consuming in resources.

If some source code breaks within AutoTools, I can fix it.  CMake, I just 
forget about it here. Meson, never heard of it either.

Ah, Meson Wikipedia; "Being written in Python Meson runs natively on Linux 
kernel-based operating systems, on macOS, on Microsoft Windows and on other 
operating systems."  Maybe they've finally found something Python is useful at? 
Or maybe now my builds here are just going to get extremely more slower than 
using AutoTools?  (eg. Slower meaning more CPU usage, and more waste of 


Geeqie-devel mailing list

Reply via email to