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

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

On 6/21/2009 07:34, Thomas Steinbach wrote:
> Hello Jon,
>
>>>> [...]
>>> 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?
>
>> Both mingw.org and mingw-w64 support the _t* names, take a look at
>> "tchar.h" header.
>
> But this doesn't make any sense. In noc case.
> Why are these header implemented, if I CAN'T compile and link
> a windows GUI application as a unicode application???
>
> Can you or anybody explain me that crazy and mad thing?
>
>> 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.
>
> These _t* funcitons doesn't make any sense, if mingw gcc, can't compile
> and link to get a full unicode progamm ???
>

I meant to say that using _tmain or _tWinMain won't work, but _tprintf 
would work as expected. You cannot use wWinMain() or wmain() as the 
entry point for your programs because of the missing startup code.

> I don't understand that. Please tell me why?
> That is really mad and I'm verryt disappointed about that :-(
>
> So it looks like I should recommend every new user to use
> Visual C or any other compiler which is abel to compile
> unicode programs...
>

I have told you already that the Unicode startups are missing in the 
mingw.org crt and suggested you used the mingw-w64 toolchain as a 
replacement.