On Tuesday 19 November 2002 12:09 pm, Vincent Béron wrote:
> Greg Turner a écrit:
> > Actually, I have similar questions about the programs and dlls
> > trees of wine... for example, Alexandre has requested that I remove
> > #ifdef's from rpcss... but can I safely code against the assumption
> > th
On November 19, 2002 12:55 pm, Greg Turner wrote:
> The wine headers are very interesting to me right now. I guess we need
> to do something like
>
> #if (some hairy condition)
> typedef WCHAR wchar_t
> #endif
>
> in the appropriate place (I guess, stddef.h)?
Here's what I did:
Index: incl
On Tuesday 19 November 2002 09:58 am, Dimitrie O. Paun wrote:
> On November 19, 2002 10:57 am, Vincent Béron wrote:
> > Quickly checking in MS's headers (an old version), there's a lot of
> > typedef to define wchar_t.
>
> I figured that much. I was hoping for a patch... :)
The wine headers are ve
Greg Turner a écrit:
The wine headers are very interesting to me right now. I guess we need
to do something like
#if (some hairy condition)
typedef WCHAR wchar_t
#endif
in the appropriate place (I guess, stddef.h)?
Actually, in winnt.h (and wtypes.h, although it's #ifdef 0, and
msvcrt
On November 19, 2002 10:57 am, Vincent Béron wrote:
> Quickly checking in MS's headers (an old version), there's a lot of
> typedef to define wchar_t.
I figured that much. I was hoping for a patch... :)
--
Dimi.
On November 19, 2002 10:51 am, Martin Wilck wrote:
> Using this line and WCHAR instead of wchar_t, I'm fine. It prints "sizeof
> (WCHAR) = 2".
I know, but this is not good enough. I want to port some apps over
(eg putty) and that one uses wchar_t. Changing the source is not an
option IMO. In this
Dimitrie O. Paun a écrit:
On November 19, 2002 10:26 am, David Fraser wrote:
So the following C program compiles fine with the above command,
-fshort-wchar or not, and making stdio.h angle-bracketed will take away the
size_t warning:
What I'm waiting for is a solution that does not touch the
Am Die, 2002-11-19 um 15.59 schrieb Dimitrie O. Paun:
> Nevertheless, they solve only part of the problem:
>
> [dimi@dimi wine]$ gcc -fshort-wchar -I /home/dimi/dev/wine/wine.src/include/msvcrt
>-I /home/dimi/dev/wine/wine.src/include test.c
> test.c: In function `main':
> test.c:8: `wchar_t' un
On November 19, 2002 10:26 am, David Fraser wrote:
> So the following C program compiles fine with the above command,
> -fshort-wchar or not, and making stdio.h angle-bracketed will take away the
> size_t warning:
What I'm waiting for is a solution that does not touch the program
I've posted. My
Dimitrie O. Paun wrote:
On November 19, 2002 09:46 am, Dimitrie O. Paun wrote:
[dimi@dimi wine]$ gcc -nostdinc -fshort-wchar -I /home/dimi/dev/wine/wine.src/include/msvcrt -I /home/dimi/dev/wine/wine.src/include test.c
Hm, maybe we need the standard headers after all.
Even though this mi
On November 19, 2002 09:46 am, Dimitrie O. Paun wrote:
> [dimi@dimi wine]$ gcc -nostdinc -fshort-wchar -I
>/home/dimi/dev/wine/wine.src/include/msvcrt -I /home/dimi/dev/wine/wine.src/include
>test.c
Hm, maybe we need the standard headers after all.
Even though this might create confusion.
Neve
Hi guys,
Here's a small test program:
#include
#include
#include
#include
int main()
{
printf("sizeof(wchar_t)=%d\n", sizeof(wchar_t));
return 0;
}
And I want to compile this with our msvcrt headers.
Look what happens:
[dimi@dimi wine]$ gcc -nostdinc -fshort-wchar -I
/home/dimi
12 matches
Mail list logo
