* internationlization
@ 2000-08-11 21:44 reedkotler
0 siblings, 0 replies; 5+ messages in thread
From: reedkotler @ 2000-08-11 21:44 UTC (permalink / raw)
To: gcc
that worked.
i just added:
#define WCHAR_UNSIGNED 1
#define WCHAR_TYPE_SIZE 16
#define WCHAR_TYPE "short unsigned int"
#define MAX_WCHAR_TYPE_SIZE WCHAR_TYPE_SIZE
to mips.h
and of course you have to use little endian.
> ----- Original Message -----
> From: "Mike Stump" <mrs@windriver.com>
> To: <reedkotler@hotmail.com>
> Sent: Friday, August 11, 2000 3:58 PM
> Subject: Re: internationlization
>
>
> > > From: reedkotler@hotmail.com
> > > To: "Mike Stump" <mrs@windriver.com>
> > > Date: Fri, 11 Aug 2000 15:34:51 -0700
> >
> > > yes, but what "config" or "compiler time" parameter is it?
> >
> > As documented in the manual... I'll quote from it:
> >
> > @findex WCHAR_TYPE_SIZE
> > @item WCHAR_TYPE_SIZE
> > A C expression for the size in bits of the data type for wide
> > characters. This is used in @code{cpp}, which cannot make use of
> > @code{WCHAR_TYPE}.
> >
> > @findex WCHAR_TYPE
> > @item WCHAR_TYPE
> > A C expression for a string describing the name of the data type to use
> > for wide characters. The typedef name @code{wchar_t} is defined using
> > the contents of the string. See @code{SIZE_TYPE} above for more
> > information.
> >
> > If you don't define this macro, the default is @code{"int"}.
> >
> >
> > A port is free to use a wide range of compile time switches, if it
> > wants, to set the value of this. See ports that do -mint64 types of
> > things.
> >
> > > i know that cygnus is building wince applications so someone has a
> > > gcc that processes wide character strings properly for wince.
> >
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: internationlization
2000-08-11 13:50 ` internationlization Reed Kotler
@ 2000-08-12 12:29 ` Alexandre Oliva
0 siblings, 0 replies; 5+ messages in thread
From: Alexandre Oliva @ 2000-08-12 12:29 UTC (permalink / raw)
To: Reed Kotler; +Cc: gcc
On Aug 11, 2000, "Reed Kotler" <reedkotler@hotmail.com> wrote:
> there must be some way to "config" it properly or to
> set the proper manner at compile time.
> this would be needed for all the wince targets so somewhere
> people must have already solved this.
I think the `pe' string is present in all WinCE triplets. Is that
your case?
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: internationlization
2000-08-10 22:01 ` internationlization Alexandre Oliva
@ 2000-08-11 13:50 ` Reed Kotler
2000-08-12 12:29 ` internationlization Alexandre Oliva
0 siblings, 1 reply; 5+ messages in thread
From: Reed Kotler @ 2000-08-11 13:50 UTC (permalink / raw)
To: Alexandre Oliva; +Cc: gcc
there must be some way to "config" it properly or to
set the proper manner at compile time.
this would be needed for all the wince targets so somewhere
people must have already solved this.
----- Original Message -----
From: "Alexandre Oliva" <aoliva@redhat.com>
To: <reedkotler@hotmail.com>
Cc: <gcc@gcc.gnu.org>
Sent: Thursday, August 10, 2000 10:01 PM
Subject: Re: internationlization
> On Aug 11, 2000, <reedkotler@hotmail.com> wrote:
>
> > when i compiler L"hello" with the gcc for NT it produces the same as
> > the microsoft cl compiler.
>
> The size of a wide character varies from platform to platform. GCC
> follows pre-existing compilers of each platform, when they exist.
>
> --
> Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
> Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
> CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
> Free Software Evangelist *Please* write to mailing lists, not to me
>
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: internationlization
2000-08-10 21:52 internationlization reedkotler
@ 2000-08-10 22:01 ` Alexandre Oliva
2000-08-11 13:50 ` internationlization Reed Kotler
0 siblings, 1 reply; 5+ messages in thread
From: Alexandre Oliva @ 2000-08-10 22:01 UTC (permalink / raw)
To: reedkotler; +Cc: gcc
On Aug 11, 2000, <reedkotler@hotmail.com> wrote:
> when i compiler L"hello" with the gcc for NT it produces the same as
> the microsoft cl compiler.
The size of a wide character varies from platform to platform. GCC
follows pre-existing compilers of each platform, when they exist.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
^ permalink raw reply [flat|nested] 5+ messages in thread
* internationlization
@ 2000-08-10 21:52 reedkotler
2000-08-10 22:01 ` internationlization Alexandre Oliva
0 siblings, 1 reply; 5+ messages in thread
From: reedkotler @ 2000-08-10 21:52 UTC (permalink / raw)
To: gcc
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 370 bytes --]
when i compiler L"hello" with the gcc
for NT it produces the same as the microsoft
cl
compiler.
Â
.ascii "h\0e\0l\0l\0o\0\12\0\0\0"
Â
however, when i compiler using the
mips
compiler, it is much different.
Â
.asciiÂ
"\000\000\000h\000\000\000e\000\000\000l\000\000\000l\000" .asciiÂ
"\000\000o\000\000\000\n\000\000\000\000"
Â
any ideas?
Â
Â
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2000-08-12 12:29 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-08-11 21:44 internationlization reedkotler
-- strict thread matches above, loose matches on Subject: below --
2000-08-10 21:52 internationlization reedkotler
2000-08-10 22:01 ` internationlization Alexandre Oliva
2000-08-11 13:50 ` internationlization Reed Kotler
2000-08-12 12:29 ` internationlization Alexandre Oliva
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).