From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Eli Zaretskii" To: ac131313@cygnus.com Cc: hilfingr@gnat.com, cgf@redhat.com, danny_r_smith_2001@yahoo.co.nz, gdb@sources.redhat.com, mingw-users@lists.sourceforge, dewar@gnat.com Subject: Re: [Mingw-users] Re: _WIN32? Date: Fri, 04 May 2001 00:20:00 -0000 Message-id: <2950-Fri04May2001102024+0300-eliz@is.elta.co.il> References: <200105010009.RAA12115@tully.CS.Berkeley.EDU> <20010503082444.40BDEF28A1@nile.gnat.com> <3AF1C25B.5040304@cygnus.com> X-SW-Source: 2001-05/msg00063.html > Date: Thu, 03 May 2001 16:40:59 -0400 > From: Andrew Cagney > > #if defined(_WIN32) || defined(__MSDOS__) || defined(__CYGWIN__): > > Remember, GDB is moving away from OS specific tests and towards > autoconf/feature based tests. Things like this should be replaced by > something like WITH_REALLY_TRICKY_FILESYSTEM_SUPPORT test (and > eventually changed to a runtime switch?). What do you envision the runtime switch will test? These conditionals define behavior that depends on the system where the GDB executable runs. Since any given GDB binary is by definition produced for only one type of platform, all the features of that platform are known at compile time, and there's no need to test anything at run time. In other words, gdb.exe compiled on Windows will only run on Windows, so we can know in advance all the features which will or will not work when it runs. And similarly for gdb produced for running on GNU/Linux.