Right. But other than the transitioning reason, is there any benefit to using autoconf in conjunction with CMake, as opposed to using CMake alone? Also, would the general scenario be to use autoconf to pass settings to CMake, or the other way around?
-w On 1/28/07, Craig Ringer <[EMAIL PROTECTED]> wrote:
Wojciech Jarosz wrote: > I've been looking through other projects that use CMake in order to > learn more. I've seen that some (Chicken, Scribus, for example) seem > to have configure.in files in addition to CMakeList.txt files. I was > wondering why one would use both autoconf and CMake in the same > project? Because CMake is relatively new to common use, and most people using it are transitioning from autotools. That's certainly the case for Scribus, which IIRC is planning on dropping autotools before 1.4 . I won't be too surprised if many of those projects are at the same time widening their portability, given that's where CMake is a real win. -- Craig Ringer
_______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
