This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC] Separate Cygwin/mingw and ANSI/Unicode parts in windows-nat.c
- From: Christopher Faylor <cgf-use-the-mailinglist-please at sourceware dot org>
- To: gdb-patches at sourceware dot org, Pierre Muller <pierre dot muller at ics-cnrs dot unistra dot fr>
- Date: Sat, 23 Apr 2011 12:37:01 -0400
- Subject: Re: [RFC] Separate Cygwin/mingw and ANSI/Unicode parts in windows-nat.c
- References: <006501cbf57e$f88c4da0$e9a4e8e0$@muller@ics-cnrs.unistra.fr> <000301cbfead$48fc1b30$daf45190$@muller@ics-cnrs.unistra.fr>
On Tue, Apr 19, 2011 at 06:17:31PM +0200, Pierre Muller wrote:
> As nobody reacted to my earlier email,
>I send here a first attempt to separate out
>what depends on the fact that we use ANSI or Wide functions
>in the Windows API calls from what is specific to Cygwin code.
>(No attempt to use UNICODE standard macros here).
>
> The present code can be compiled in 6 versions:
>cygwin (using wide Windows API by default)
>mingw32 (using ANSI Windows API functions)
>mingw64 (also using ANSI Windows API functions)
>but also
>mingw32 with wide Windows API functions (by adding -D__USEWIDE to CFLAGS)
>likewise for mingw64
>and finally also
>cygwin with ANSI windows functions (by adding -D__USEANSI to CFLAGS).
>
> As I stated earlier, I am mostly interested in the fact
>that mingw32 still supports ANSI versions to be able to still use it on
>old Windows 95 OS.
>
> The fact that all 6 versions compile allowed me to better separate
>out Cygwin specific code from what is related to the use of Wide strings.
>In particular, windows_create_inferior is simplified which
>is important for the yet to come GDB local environment variable changes
>support.
>
> Comments?
I've already said that I'd like to just standardize on wide character
versions of the windows functions. gdb barely works on Windows 9x. I
have no problems not-supporting pre-NT versions of Windows with newer
versions of gdb.
cgf