cURL / Mailing Lists / curl-library / Single Mail

curl-library

Re: Curl and CMake

From: Andy Cedilnik <andy.cedilnik_at_kitware.com>
Date: Wed, 13 Sep 2006 14:31:14 -0400

Hi Dan,

Well, I would take responsibility of maintaining CMake files, since I am
the one who needs them. By the way, libcurl is cmakified. We use it in
CMake for the last couple of years without any problems, so I would
argue that 75% or more of the work is already done.

Now, as far as the befit of adding CMake files, currently you have to
maintain lots of CMake files:

src/Makefile.am src/Makefile.b32 src/Makefile.in src/Makefile.inc
src/Makefile.m32 src/Makefile.netware src/Makefile.riscos
src/Makefile.vc6 src/Makefile.Watcom

And this is just in src. There is a similar list in libsrc and so on.

This can be replaced with a single (or if you want to keep m4 stuff,
two) set of files.

Ok, all I am really asking is if it would be possible to add CMake files
in the source tree, so that I can make sure they are in sync with the
sources.

Thank you.

       Andy

Dan Fandrich wrote:
> On Wed, Sep 13, 2006 at 11:31:30AM -0400, Andy Cedilnik wrote:
>
>> I can do most of this right now, but I would like to make my life easier
>> and try to get Curl developers to put the CMake lists file for building
>> Curl and libCurl into Curl source code. This way I can actually make
>> sure that the Curl is all the time compatible with CMake and I don't
>> have to do once a year merging of the latest Curl. In addition to
>> simplifying my life, it would perhaps make porting Curl to different
>> platforms easier and we could even setup a Dart testing dashboard for Curl.
>>
>
> The problem with this is that curl contains 5000 lines of m4 macros,
> Bourne shell code and automake templates that have been refined over the
> past 8 years to build on countless systems. It would take a tremendous
> effort to port that to CMake to start with, and unless curl switches to
> CMake as its configuration system, it would need to be kept up to date
> in parallel with autotools. That's lots of work for essentially almost no
> benefit to the curl project as it won't help curl work on any more systems
> than it does today.
>
>
>>>> Dan
>>>>

-- 
Andy Cedilnik
Kitware Inc.
Received on 2006-09-13