I hate CMake, it is way too complex, these guys re-invented the wheel with no decent reuse of any methodology / language that existed before. If we take SCons as another example, it took python and used it to do build... So if you are python developer most probably you know how to SCons. Also, look the huge backlog of bugs of CMake, it is amazing!
Common to both CMake and SCons is the ability to work with Microsoft toolchain to produce binaries. This is a great advantage over the autotools. However, these tools are inferior when it comes to autotools (provided you know what you are doing) in *NIX, embedded and cross compile. To build using CMake or SCCons you need these tools on *TARGET* machine, these tools has LONG LIST of dependencies. To build using autotools you need POSIX utils (sh, sed, ls, rm, ...) and POSIX make and that's it! I don't mind if for Windows CMake/SCons will be maintain in addition, keep autotools usage for windows cross compile and *NIX build using autotools. Alon. On Thu, Nov 24, 2011 at 11:25 AM, Adriaan de Jong <dej...@fox-it.com> wrote: > Just to put in my 2cents on the build options: there is a tool that supports > all of those environments (gmake, cygwin, mingw, nmake, visual studio, > eclipse, ....), and that's CMake. It's widely used, and has a pretty good > track record. It can also support automated test environments and packaging. > > It has one major disadvantage: the current build system would need to be > converted from an autoconf-based to a new CMake-based system, together with > all of the knowledge contained within it. Further, there is less knowledge of > CMake than autoconf within the OpenVPN community. > > Disclaimer: I'm not trying to start a holy war here, I know every system has > its own advantages and drawbacks. I just want to get the option on the table > :). I've had some positive experience with CMake, through PolarSSL and some > projects at work. I'll try to make it to the meeting this evening for the > discussion. > > Kind Regards, > > Adriaan > >> -----Original Message----- >> From: Samuli Seppänen [mailto:sam...@openvpn.net] >> Sent: donderdag 24 november 2011 9:48 >> To: openvpn-devel@lists.sourceforge.net >> Subject: [Openvpn-devel] Topics for today's meeting >> >> Hi, >> >> We're having an IRC meeting today, starting at 18:00 UTC on #openvpn- >> de...@irc.freenode.net. Current topic list is here: >> >> <https://community.openvpn.net/openvpn/wiki/Topics-2011-11-24> >> >> If you have any other things you'd like to bring up, respond to this >> mail, send me mail privately or add them to the list yourself. >> >> In case you can't attend the meeting, please feel free to make comments >> on the topics by responding to this email or to the summary email sent >> after the meeting. >> >> NOTE: It's required to use a registered Freenode IRC nickname to join >> #openvpn-devel - look here for details: >> >> <https://community.openvpn.net/openvpn/wiki/GettingHelp#DeveloperIRCcha >> nnel> >> >> -- >> Samuli Seppänen >> Community Manager >> OpenVPN Technologies, Inc >> >> irc freenode net: mattock >> >> ----------------------------------------------------------------------- >> ------- >> All the data continuously generated in your IT infrastructure contains >> a definitive record of customers, application performance, security >> threats, fraudulent activity, and more. Splunk takes this data and >> makes sense of it. IT sense. And common sense. >> http://p.sf.net/sfu/splunk-novd2d >> _______________________________________________ >> Openvpn-devel mailing list >> Openvpn-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/openvpn-devel > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > Openvpn-devel mailing list > Openvpn-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openvpn-devel >
