On Fri, Nov 30, 2012 at 7:09 AM, Jan Nijtmans <[email protected]>wrote:
> 2012/11/30 Gilles <[email protected]>: > > 1. BTW, if the MinGW version offers better support for shell use, why > > is the Windows binary compiled with MSVC? > The Windows binary is compiled with MinGW, only the commandline > parser is replaced, That replacement command-line parser is not used on MinGW. Notice the "!defined(__MINGW__)" on this line: http://www.fossil-scm.org/fossil/artifact/a6c2200ac42a?ln=493 You can use the "fossil test-echo" command to check to test the command-line parser, to see what it does for your particular build. There is also a --hex option to "fossil test-echo" (in very recent versions) that shows you hexadecimal, to make sure it is handling UTF8 correctly. > in order to fix bugs like [13b7388964], [490b6c2edd] > [cadc9aa78f], [d22946aa0c], all related to not using utf-8 on > Windows. This parser doesn't do command-line expansion, just > like MSVC and mingw-w64. Command-line expansion is an > unique feature of MinGW, it is useful when using the Windows > command line prompt, but is not expected in other situations. > > See also ticket [8ca2aae391], which contains Richard's remark > how to finally fix that. > > > 2. Also, the Fossil wiki says: "Note that Fossil requires the "zlib" > > compression library. This library is available by default on most unix > > systems, but it will typically have to be installed separately on > > windows systems. > > That's fixed now, the wiki can be adapted: You don't need to > install zlib any more on Windows in order to build fossil. > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
