CMake

[OgreTransporter]

Wouldn't it be easier to switch the build system from ImageMagick to CMake? Then you only have to maintain the ImageMagick main repository and not VisualMagick as well.

[urban-warrior]

As an open-source project, any user can contribute the CMake build files to build ImageMagick. And one user has done that-- however, as is, it was far from robust. It's easy enough to naively get CMake to build the ImageMagick from source, its a much different situation to replace the plethora of features currently supported by the autoconf/automake build. To succeed, the CMake build must support all the delegate libraries, delegate programs, build options, updating the ImageMagick configuration files with the build information, targeting of different ABI versions, support TAP unit tests, support for building PerlMagick, support for building under {Linux, Mac OS X, Windows}, and support for different versions of ImageMagick: 6 & 7, and ensuring all of these requirements work robustly. What we've seen in the past, some users have offered CMake builds but fall short of a robust build configuration-- that is, it takes a week to create the initial CMake ImageMagick build. However, for a full production ready CMake build for ImageMagick, it will likely take 6 months. With that in mind, when can you deliver a robust CMake build for ImageMagick to replace the current autoconf/automake build?