Re: [Mingw-users] Re: _WIN32?

Christopher Faylor
2001-05-04T12:04:00Z

On Fri, May 04, 2001 at 08:19:10PM +0300, Eli Zaretskii wrote:
>> Date: Fri, 4 May 2001 11:44:17 -0400
>> From: Christopher Faylor <cgf@redhat.com>
>> >
>> >> Yes, for the most part I would like to strongly encouraging people doing
>> >> WIN32, GO32 and CYGWIN ports to look back over all those #ifdef's and
>> >> see if they are better served by an autoconf feature test.
>> >
>> >Based on my experience, quite a few of them won't be served better by
>> >an Autoconf test, because it isn't quite clear what to test. One
>> >notable example is the terminal initialization in
>> >utils.c:init_page_info--how do you test for something whose effect is
>> >on the screen?
>>
>> You don't necessarily have to test for anything. We could just add
>> a TERMINAL_DOES_BLAH conditional which was set only when gdb was being
>> run under cygwin, or djgpp, or (don't worry we're working on it and
>> will have something in the next <<undeterminied>> timeframe, really
>> we will) Windows. You don't actually have to write an autoconf test
>> for this.
>
>I agree with that approach, but Andrew was talking about Autoconf.

So was I. You could still do this in configure.in. The alternatives are
having something like:

#if defined (__CYGWIN__) || defined (__DJGPP__)
# define FILENAME_CASE_INSENSITIVE
#endif

of something like (in configure.host):

case "$host_cpu" in

i[3456]86-*-cygwin*)
gdb_host=cygwin
FILENAME_CASE_INSENSITIVE=1
;;

i[3456]86-*-msdosdjgpp*)
gdb_host=go32
FILENAME_CASE_INSENSITIVE=1
;;
esac

AC_SUBST(FILENAME_CASE_INSENSITIVE)

cgf