From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Faylor To: gdb@sources.redhat.com Subject: Re: [Mingw-users] Re: _WIN32? Date: Fri, 04 May 2001 12:04:00 -0000 Message-id: <20010504150314.A18777@redhat.com> References: <20010503211502.21716.qmail@web6401.mail.yahoo.com> <3AF1DAA0.3060702@cygnus.com> <200105040919.FAA27879@delorie.com> <20010504114417.D17458@redhat.com> <8582-Fri04May2001201909+0300-eliz@is.elta.co.il> X-SW-Source: 2001-05/msg00072.html 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 >> > >> >> 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 <> 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