wouldn't it be nice to have winemaker-generated sources automatically
add -fshort-wchar to the C compiler options?
To make this robust, one could write a configure test for it.
Martin
--
Martin WilckPhone: +49 5251 8 15113
Fujitsu Siemens Computers Fax: +49 5251 8 20409
On December 11, 2002 08:13 am, Martin Wilck wrote:
wouldn't it be nice to have winemaker-generated sources automatically
add -fshort-wchar to the C compiler options?
I personally don't understand why we even bother with other options.
The -fshort-wchar is the only correct fix to the problem,
Am Mit, 2002-12-11 um 16.17 schrieb Dimitrie O. Paun:
The -fshort-wchar is the only correct fix to the problem, and just
by enumerating the other hacks we just confuse the issue.
Agreed - at least I see no need for automating them.
Who is crazy enough to use the other hacks where there is
On December 11, 2002 10:52 am, Martin Wilck wrote:
well the configure script should probably check if -fshort-wchar is
supported, add the option to CFLAGS if yes, and issue a warning if no.
But the problem is that winemaker will run on different systems that
configure runs on... It will get it
Am Mit, 2002-12-11 um 16.49 schrieb Dimitrie O. Paun:
On December 11, 2002 10:52 am, Martin Wilck wrote:
well the configure script should probably check if -fshort-wchar is
supported, add the option to CFLAGS if yes, and issue a warning if no.
But the problem is that winemaker will run on
On December 11, 2002 12:05 pm, Martin Wilck wrote:
I can't follow you. Winemaker generates a configure.ac file. You need to
run autoconf and configure anyway to build your code.
We just need to make sure that Winemaker puts a test for -fshort-wchar
into configure.ac.
What am I missing?
On Jan 17, 2001, Jon Griffiths [EMAIL PROTECTED] wrote:
Thanks for the feedback though. If I get time I might scribble up some docs
on using unicode. Its taking a little getting used to, so it might be useful
for others working with Winelib in the future...
If you do get some docs
If you do get some docs written, by all means submit it to one of the
Wine guides (the Winelib User Guide?). If you don't feel like writing
it in DocBook, you can just send me the plain ASCII text, and I'd be
happy to convert it and find a good place for it.
big grin
I was hoping someone
Hi,
Use gcc 2.97 with -fshort-wchar.
Well, this was for VWCL, and I wanted to make the price of entry as low as
possible for the existing win programmers, so I've gone for another solution;
since its a C++ framework its sufficient to use
#define VTEXTW(str) wine_unicode_text(L##str)
and
Jon Griffiths wrote:
Hi,
Use gcc 2.97 with -fshort-wchar.
Well, this was for VWCL, and I wanted to make the price of entry as low as
possible for the existing win programmers, so I've gone for another solution;
since its a C++ framework its sufficient to use
#define VTEXTW(str)
Hi,
Of course the name is a bit long (and it's WINE specific) so you
could do:
#define VTEXTW(x) WINE_UNICODE_TEXT(x)
In this case the macro is only used in c++, so I used what WINE_UNICODE_TEXT
expands to in this context; this works for single chars and strings. I think
to be
Jon Griffiths wrote:
Hi,
Of course the name is a bit long (and it's WINE specific) so you
could do:
#define VTEXTW(x) WINE_UNICODE_TEXT(x)
[...]
Actually, having said that, have you tested -fshort-wchar? does it require
libc to be rebuilt? or just to build with a different
Actually it helps a little in that you can use the standard C library
headers (e.g. to get wcslen) and then link with crtdll or msvcrt.
This is what I was wondering; given that they expect wchar_t* and Winelib
uses WCHAR* I assumed the headers would be useless.
But the libc C still
On Thu, 18 Jan 2001, Jon Griffiths wrote:
Actually it helps a little in that you can use the standard C library
headers (e.g. to get wcslen) and then link with crtdll or msvcrt.
This is what I was wondering; given that they expect wchar_t* and Winelib
uses WCHAR* I assumed the headers
On Tue, 16 Jan 2001, Jon Griffiths wrote:
[...]
Under windows, __TEXT gives you a string in ascii or u/c depending on whether
UNICODE is defined. But you can still always get a u/c string by using
L"foo". With winelib this gives you a glibc u/c string :-(
Use gcc 2.97 with
15 matches
Mail list logo
