Re: [Mingw-users] unicode and WinMain compiling error

[JonY <10...@gm...>]

On 6/20/2009 10:54, Thomas Steinbach wrote:
> Hello Jon,
>
>>>>> [...]
>>>>> Does anybody knows this problem or does anybody have a hint and tips
>>>>> how
>>>>> to solve that?
>>>
>>>> Hi,
>>>> iirc, mingw.org provided gcc doesn't support wide startup.
>
> yes, you're right, forget that. But I already have the _tWinMain function,
> which
> schould also compile to a unicode version if defined, shouldn't it?
>
>>>> [...]
>> I forgot to mention it works on win32 too. They really have to come up
>> with a better name.
>
> Ah. Ok, I see. Will try that if I have more time
>
> Anyway. Is ther really _NO_ way to compile sourcecode, which is coded
> with the _t* functions and the _T('') macro, etc.? I can't believe that.
> I'm wondering if mingw can't compile such code...
> Why? And why there are such implementations of the _t* functions in mingw?
> It should compile as unicode if defined, shouldn't it?
>
>
> Thomas
>
>

Hi,

Both mingw.org and mingw-w64 support the _t* names, take a look at 
"tchar.h" header.

Now that you mention it, in mingw.org tchar.h, they have:

#if 0  /* no  wide startup module */
#define _tmain      wmain
#define _tWinMain   wWinMain
#define _tenviron   _wenviron
#define __targv     __wargv
#endif

Even if you did change it to wWinMain, the code still can't properly 
link due to the missing startup code in the mingw.org crt. The other _t* 
functions like _tprintf should work as expected.

mingw-w64 on the other hand already includes the Unicode startup codes, 
but the toolchain is a bit harder to set up, compared to the easy point 
and click mingw.org installer.