| |||||||||||||
Why the KDE project switched to CMake -- and how (continued)Why the KDE project switched to CMake -- and how (continued)Posted Jun 23, 2006 3:54 UTC (Fri) by jamesh (guest, #1159)In reply to: Why the KDE project switched to CMake -- and how (continued) by aleXXX Parent article: Why the KDE project switched to CMake -- and how (continued)
Some prominent ones that come to mind are Mozilla and Python. There are others, but autoconf is definitely used in more projects than automake (which is no surprise since automake requires autoconf but not vice versa).
(Log in to post comments)
Why the KDE project switched to CMake -- and how (continued) Posted Jun 23, 2006 20:13 UTC (Fri) by nix (subscriber, #2304) [Link] Mozilla, Python, GCC, Emacs, XEmacs... the list is long.
A brief scan of the packages I have unpacked here reveals 1319 using Autoconf, of which 835 use Automake.
|
|||||||||||||