Hello all: At the risk of sparking controversy, I think TigerVNC should use SCons as its only build system. Here's why:
1. SCons can use native tools on both Unix and Windows. No Unix emulation layer is required on Windows. The more I develop under Windows, the more I understand how different the two systems are, and the more I want to avoid trying to emulate Unix on Windows. 2. SCons uses a single, powerful programming language (Python) for its project files, rather than shell+make+m4+Perl as in autotools, or inflexible XML project files as in Visual Studio. Version number as SPOT? Sure. Auto-generation of license file with CRLF? Easy! Yes, Peter, I've been reading your SVN commit messages. 3. I think many developers have grown tired of autotools. Major projects still use it because it's considered some kind of standard; perhaps they think users will be severely disoriented or something like that if they have to do something other than "./configure && make". But end-users don't build software from source, and the people who actually do -- developers -- are smart enough to deal with a different build system if it's better. I would be surprised if anyone still likes autotools. That said, I'm not proficientin SCons yet, but I want to learn it. Any thoughts? Matt ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
