Le Thu, 26 Mar 2009 12:14:06 +0100, Pierre Joye <[email protected]> a écrit:
> hi, > > I would go with CMake and autoconf. Both cover all possible platforms. > > Cheers, > > On Thu, Mar 26, 2009 at 12:03 PM, Daniel Stenberg <[email protected]> wrote: >> On Wed, 25 Mar 2009, Piotr Dobrogost wrote: >> >>> Having this CMake build scripts doesn't prevent having the hand written >>> nmake makefiles as well. This would allow to build curl without using CMake >>> for those who doesn't want to use it. In the future we could add boost.build >>> scripts so that people used to this build system could build this way. >> >> I think we shouldn't have to add support for every imaginable build system >> just because they exist. They all require maintenance (and we already have >> problem to maintain the non-configure builds) and we risk "drowning" in >> options. >> >> Or would boost.build add anything in particular that cmake won't? (I've not >> used either one.) >> >> -- >> >> / daniel.haxx.se >> Hi all, 1. Agreed for autoconf + CMake (not more because of maintenance). As a side note: No matter which build system we support until the build is easy on all platforms. 2. Agreed to merge the current CMake scripts and do the CVS stuff. I did not have the time to merge yet (I'm ill...), but I'll do it ASAP. See you! -- Sukender PVLE - Lightweight cross-platform game engine - http://pvle.sourceforge.net/
