> No, I don't need tchar.h in 'unixcalls.c'. I only needed it
> for 'winefile.c'. The problem is, if I add 'include/msvcrt'
> to the include path, it is added to both files at the same time.
I see. What about adding a separate rule to Makefile.in just for
unixcalls.c and omit that file from C_SR
Hi Martin,
> currently it's impossible to compile winefile in UNICODE mode
> with Wine without some extra rule for unixcalls.c in the
> Makefile. I tried it even without using any TCHAR functions
> or types, but inserting include/msvcrt in the include path
> conflicts with inclusion of the hea
> > So I really think Wine has to support the TCHAR type and all
> > associated functions/macros to stay as close to the Windows
> > API as possible.
>
> Wine obviously supports TCHAR, that doesn't mean you want to
> use it in new code. We have 16-bit support too but nobody
> advocates writing
Hi,
> The pure existence of in the Wine code base
> shows me, Wine is aimed to support TCHARs. So why don't you
> want to properly activate its functionality and take Winefile
> as an example how to use it?
> ...
> I know, I won't be able to convince you. Any one out there to
> support my poin
