[Cmake] What I don't understand about CMake

[William A. Hoffman]

I think that feature would be very hard to implement.  
There are IF statements in cmakelist files, so conversion
would have to convert the entire cmake language into 
configure.in and automake files.   Before I did that, I would
try and make a "C" only implementation of cmake, and make
it so you can include the source for cmake in a project.
Of course, if you wanted to implement such a beast and you got
it working...

Although at the end of the day it seems like a lot of work
so that UNIX folks do not have to install a package which is quite
easy to install.


-Bill

At 07:53 AM 11/14/2003, Stefano Barbato wrote:
>I think that CMake have different kind of user base based on OS type.
>
>When looking from Windows prospective CMake could be considered a developer 
>tool since Windows *users* are not used to and don't usually benefit (or 
>care) about building from source code. CMake handes compilation and packaging 
>of binary files on developers machine, and those binary files will be 
>distributed to end-users. If somebody wants to compile by himself then he 
>must install CMake.
>
>Looking from Unix side CMake must be an end-user tool since most of the time 
>users need to buid from source because Unix environments could be very 
>different one another. Binary distribution is often not feasible. So here 
>we're shifting our target user from the developer to the end-user.
>
>So here is the today-madness-question :) Wouldn't a CMake-to-autotools 
>convertion feature fix this gap by allowing developers to take advantage of 
>CMake power features and end-users to compile without downloadind and 
>installing anything more then the application they want to use?
>
>This probably will not help to spread cmake on all unix systems around but 
>will help spreading cmake on developers PCs.
>
>stefano