This is the mail archive of the
mailing list for the Java project.
Re: [PATCH] [MinGW] for Review: Add UNICODE support to MinGW libgcj (UPDATED)
- From: Bryce McKinlay <bryce at mckinlay dot net dot nz>
- To: gnustuff at thisiscool dot com
- Cc: tromey at redhat dot com,luciano at virgilio dot it,Ranjit Mathew <rmathew at hotmail dot com>,GCJ Patches <java-patches at gcc dot gnu dot org>,java at gcc dot gnu dot org,MinGW Developer <mingw-dvlpr at lists dot sourceforge dot net>,João Garcia <jgarcia at uk2 dot net>
- Date: Fri, 5 Dec 2003 11:38:07 +1300
- Subject: Re: [PATCH] [MinGW] for Review: Add UNICODE support to MinGW libgcj (UPDATED)
- References: <73XTRKH3A9QPC9XW5Z86A796TYTMI.3fc0df72@p733>
On Nov 24, 2003, at 5:25 AM, Mohan Embar wrote:
This patch supersedes this:
...and attempts to address the outcry from those who didn't
want the UNICOWS licensing restrictions on Win9X. It adds
a configure switch for the compiler called --enable-libgcj-mingw-osapi
which can take one of three values:
ansi: Use the char and the Win32 A functions natively, translating
to and from UNICODE when using these functions.
unicows: Use the WCHAR and Win32 W functions natively. Adds -lunicows
to libgcj.spec to link with libunicows. unicows.dll needs to be
deployed on Win9X machines running built executables.
unicode: Use the WCHAR and Win32 W functions natively. Does not add
-lunicows to libgcj.spec. The built executables will only run
on WinNT and above.
Which is the default? Am I right in assuming that this gives the choice
ansi: libgcj that works everywhere, but is somewhat inefficient because
it converts all strings twice
unicows: libgcj that works everywhere but requires third party
libunicows to be available, and unicows.dll at runtime on win9x
unicode: fast libgcj that needs no extra library but only runs on >=
I'm presuming its just not really possible to just determine at runtime
which (ansi or unicode) should be used, right?
Please be sure to document this in gcj.texi.