On Fri, 23 Sep 2016, Brad House via c-ares wrote:

I'd like to re-open the discussion of the last patch I sent via this mailing list: "[PATCH] remove configure-time type size checks"

This fixes multi-arch building for iOS and MacOSX (without requiring separate builds and using lipo to join them), and has been tested across a large number of platforms.

Was that patch complete? I thought we still had some missing pieces. Please, bring it back up and let's make sure we iron out any left wrinkles. I'd like to see those configure-time checks removed as well.

If that patch is accepted, then I'd also like to re-proprose my CMake build system for c-ares as well. I do have some slight tweaks/fixes for some platforms (like iOS), as well as it being compatible with the aforementioned type size check patch.

I'm torn on cmake.

I personally feel completely lost with it and I experience that it takes me much more time and effort to get anything done with it than autotools. Of course this is mostly because I've written autoconf checks for almost 20 years. But I also feel that in general we find fewer people with cmake skills than autoconf skills so I've seen the cmake build lag in maintenance in other projects I spend time in. Does cmake support all those old legacy unixes to the same extent configure scripts do?

Then again, the c-ares configure script is fairly simple and is probably an ideal candidate for replacing with cmake.

I would like to propose that we start out with merging cmake build support in parallel to the existing build scripts so that we all can get a feel for both and help out making the cmake get up to par with the autoconf based one and then at some point in the future when we think they're roughly equal in what they support we can decide to drop the autoconf version.

I would also *love* to hear what others have to say about this!

--

 / daniel.haxx.se

Reply via email to