World: r3wp

you'll probably have to use a different gcc (i686-pc-mingw32-gcc 
or something) or pass -mno-cygwin to the default gcc

btw, you don't need msys to compile the host kit. mingw alone is 
sufficient

I was going to try using the i686 build (on this machine) of MinGW-64 
in Cygwin as my only Windows x86 compiler. Then I'd only need to 
add the Android ARM and x86 cross compilers to cover what I currently 
need to compile, and be able to make 64bit apps when I get my Win7 
machine rebuilt.

without a 64-bit r3lib, you won't get 64bit builds of r3 any time 
soon :)

Best to be prepared :)

but usually, the x86-64 gcc's happily emit x86-32 just by passing 
-m32

Yup, MinGW-64 has good support for generating 32bit code; I was researching 
the issues involved all of yesterday.

Fixed the warning: deprecated conversion from string constant to 
'wchar_t*'

https://github.com/Oldes/R3A110/commit/aebc8b8334f1396862b7249d2ab993d83c1c11f8

should be probably improved to set different name for non Windows 
builds.

And here is merge with Andreas' changes:

https://github.com/Oldes/R3A110/commit/ed261d8a39b973de6635b9833c32ceffe0780cba

Tested only on Windows.

What is strange is, that exes built using make-gcc/3.1/makefile are 
detected by Norton Sonar as suspicious :-/  not the one built with 
Codeblocks

http://www.symantec.com/connect/forums/sonar-detects-our-protected-application-high-security-risk

this one:

http://securityresponse.symantec.com/security_response/writeup.jsp?docid=2010-090200-2232-99
I will submit it to Norton as false positive.

Using the Cygwin compilers turned out to be unnecessary, so I can 
get away with just the Cygwin base install plus make for the NDK, 
TDD-GCC for the host kit, and Git for Windows for the Git support. 
Only one set of compilers per target platform, but 3 mostly duplicated 
sets of general command line tools.