Re: [Mingw-w64-public] Learning to use MinGW-w64

2013-12-05 Thread mity
I believe it is possible, but you have to explicitly tell it with the gcc option -municode. Martin > I am not sure what is the status now, but couple of years ago, GCC could > not compile programs with UNICODE version of WinMain. If it still > persist, you will need to declare the entry point as

Re: [Mingw-w64-public] Learning to use MinGW-w64

2013-12-05 Thread Ruben Van Boxem
2013/12/5 Pavel > I am not sure what is the status now, but couple of years ago, GCC could > not compile programs with UNICODE version of WinMain. If it still > persist, you will need to declare the entry point as > > int main(int argc, char **argv) > > You can get the UNICODE command line argume

Re: [Mingw-w64-public] Learning to use MinGW-w64

2013-12-05 Thread Pavel
I am not sure what is the status now, but couple of years ago, GCC could not compile programs with UNICODE version of WinMain. If it still persist, you will need to declare the entry point as int main(int argc, char **argv) You can get the UNICODE command line arguments later by calling GetComman

[Mingw-w64-public] Learning to use MinGW-w64

2013-12-05 Thread wynfield
>From: JonY >Date: Thu, 05 Dec 2013 17:23:48 +0800 >Subject: Re: [Mingw-w64-public] Using MinGW-w64 >On 12/5/2013 12:58, wynfield wrote: >> # I then tried to compile it, but it failed as soon below. >> >> $ /bin/i686-w64-mingw32-gcc.exe hello.c >>i686-w64-mingw32-gcc: error: spawn: