From: Harald O. <har...@el...> - 2012-12-07 09:38:19
|
Am 07.12.2012 10:24, schrieb Trevor Davel (Twylite): > Hi, > > On 2012/12/07 11:07 AM, Harald Oehlmann wrote: >> I personally whant to help to get tcl8.6.0 released. >> >> Thats why I work on the test in the build environment. >> The IMHO function for the build people is, that a "make test" on tcl >> just runs all tests of all bundled packages. >> >> I will not try CMake, as it will not bring us further to the aim. > I agree with that approach, which is why I contributed the attempt at a > makefile.vc for tdbcodbc. I would like to see a move to CMake in the > longer term, but it won't help towards an 8.6.0 release. > >> There should be a general decision like: >> 1) we use CMAKE and MSVC++ 6,7,8,9,10 (any set of them) > Yes. In fact the CMake team made specific changes to support the path > quoting needed for pkgConfig defines passed in from the build file, > which require some really weird quoting in MSVC 6 and 8 project files. > >> 2) we use NMAKE and MSVC++ 6,7,8,9,10 (any set of them) > What we have now. Painful to maintain, and doesn't allow Windows users > to work in the MSVC IDE, use interactive debugging, use third-party > memory checking tools, etc. > >> 3) we use cygwin/msys make and MSVC++ 6,7,8,9,10 (any set of them) > Over the past couple of years the msys installer has been broken on and > off for months. It is not acceptable to rely on a technology that is > not itself reliable. Using msys also means requiring Windows developers > to learn how to use a *nix shell prompt, maintain builds using autoconf > (which is itself a black art), and not use the MSVC IDE and its > facilities (as mentioned above). In short it's just keeps Windows as a > second-class environment for Tcl development. Thank you for the valueable summary. I agree and have put it on http://wiki.tcl.tk/20966 Harald |