msys

I'd like to use AnsiColorLogger to get color ouput from Ant . I'm using Git Bash on Windows. I tried: $ ant -logger org.apache.tools.ant.listener.AnsiColorLogger but my output looks like: Buildfile: c:\foo\build.xml ←[2;36m [junit] Testsuite: org.foo.BarTest←[m ←[2;36m [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 0.188 sec←[m ←[2;36m [junit] ←[m ←[2;36m [junit] Testcase: testInherits took 0.175 sec←[m ←[2;36m [junit] FAILED←[m ←[2;36m [junit] subdir not child←[m ←[2;36m [junit] junit.framework.AssertionFailedError: subdir not child←[m ←[2;36m [junit] at org.foo.BarTest

I'm running windows XP. I have been following this tutorial and so downloading mingw-get-inst here . I've done this a couple times and the last time I checked boes to install EVERYTHING including, but not limited to, gcc, g++, MSYS and the MinGW Compiling Suite. I told it to make a program menu shortcut, too. I believe I have correctly added MinGW/bin to the Environment Settings' Path . So I have the shortcut to the MSYS shell now. It goes to C:\MinGW\msys\1.0\msys.bat, but the whole msys directory does not exist! There are tons of "packages" have been downloaded as far as I can tell ("mingw

I was just trying to build netcat in MSYS using MinGW and realized that MinGW never really ported all of the BSD socket stuff to Windows (eg sys/socket.h). I know you can use Windows Sockets in MinGW, but why did they never make a Windows port of the BSD sockets? I noticed quite a few programs using #ifdef's to workaround the issue. Is there a Windows port of the BSD sockets somewhere that can be used instead? Here are the errors when doing a make for netcat in MSYS: gcc -DLOCALEDIR=\"\/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -Wall -c `test -f 'core.c' || echo './'`core.c

I can't seem to get a handle on the difference between the two. It seems that one ( GNUWin32 ) is an layer on top of windows (like MSYS ) and the other (cygwin) is something else (?) What does that mean? When would I use one over the other? Are they both suited for the same thing? I want to use it mainly for git but want to keep my options open for learning and doing all thing *nixy. Is there another tool for this? Will msysgit be better suited for this? Are there any resources that go through the differences of all of these *nix platforms exhaustively? Michael Slade Cygwin is a library that

I'm using mingw with msys and mintty on windows. I have a problem that msys and mintty are somehow not flushing output until a command is finished. This means I can't really run any interactive programs. For example, if I have in C : printf("Test\n"); the output won't appear until the program has terminated. However, if I have: printf("Test\n"); fflush(stdout); then the output appears immediately. If I use msys without mintty or the windows console, then everything works normally. So my question, what's going on with msys and mintty? This can be an issue when msys uses the rxvt shell under a

I have an old library (in C++) that I'm only able to build on MinGW+MSYS32 on Windows. From that I can produce a .a static library file generated from GNU libtool. My primary development is done in Visual Studio 2008. If I try to take the MinGW produced library and link it in Visual Studio, it complains about missing externals. This is most likely due to the C++ symbol mangling that is done, and that it doesn't match whats in the .a file. Is there any know way to convert a static .a file to VC++ library format? If symbols are mangled differently, the compilers are using a different ABI and you

We have the git bare repository in unix that has files with same name that differs only in cases. Example: GRANT.sql grant.sql When we clone the bare repository from unix in to a windows box, git status detects the file as modified. The working tree is loaded only with grant.sql, but git status compares grant.sql and GRANT.sql and shows the file as modified in the working tree. I tried using the core.ignorecase false but the result is the same. Is there any way to fix this issue? Windows is case-insensitive (more precisely, case-preserving). There is simply no possible way for two files to