From: Danny Smith <danny_r_smith_2001@yahoo.co.nz>
To: gdb@sources.redhat.com
Subject: Re: [Mingw-users] Re: _WIN32?
Date: Sat, 05 May 2001 15:57:00 -0000 [thread overview]
Message-ID: <20010505225648.23019.qmail@web6404.mail.yahoo.com> (raw)
>>
>> 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
Please be patient. I have very little experience with multiplatform
configurations, none with autoconfigury I am one of these folk:
>>(don't worry we're working on it and
>> will have something in the next <<undeterminied>> timeframe, really
>> we will) Windows.
and I am getting a bit confused by some of this discussion, and what I should
do. For me examples teach.
Here is an example of what I would like to add:
In event-loop.c, a clock is needed. Posix uses gettimeofday. Here is how I
would provide that clock for w32:
/* winbase.h definitions */
typedef struct _FILETIME {
unsigned long dwLowDateTime;
unsigned long dwHighDateTime;
} FILETIME;
void __stdcall GetSystemTimeAsFileTime(FILETIME*);
/*time from 1 Jan 1601 to 1 Jan 1970 in 100ns units */
#define _W32_FT_OFFSET (116444736000000000LL)
typedef union {
long long ns100; /*time since 1 Jan 1601 in 100ns units */
FILETIME ft;
} w32_ftv;
void nt_gettimeofday(struct timeval* p, struct timezone* tz /* IGNORED */){
w32_ftv _now;
GetSystemTimeAsFileTime( &(_now.ft) );
p->tv_usec=(long)((_now.ns100 / 10LL) % 1000000LL );
p->tv_sec= (long)((_now.ns100-_W32_FT_OFFSET)/10000000LL);
return;
Now, how would you like me to put this into event-loop.c.
An example please, either on this list or privately
_____________________________________________________________________________
http://store.yahoo.com.au - Yahoo! Store
- It's time you had your business online!
next reply other threads:[~2001-05-05 15:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-05 15:57 Danny Smith [this message]
2001-05-05 18:54 ` Christopher Faylor
2001-05-05 23:03 ` Eli Zaretskii
2001-05-05 23:02 ` Eli Zaretskii
2001-05-06 1:52 ` Danny Smith
[not found] <200105010009.RAA12115@tully.CS.Berkeley.EDU>
2001-05-03 1:24 ` Paul Hilfinger
2001-05-03 13:41 ` Andrew Cagney
2001-05-03 14:15 ` Danny Smith
2001-05-03 15:24 ` Andrew Cagney
2001-05-03 15:54 ` Christopher Faylor
2001-05-03 16:11 ` Andrew Cagney
2001-05-04 2:17 ` Eli Zaretskii
2001-05-04 2:19 ` Eli Zaretskii
2001-05-04 8:45 ` Christopher Faylor
2001-05-04 10:18 ` Eli Zaretskii
2001-05-04 12:04 ` Christopher Faylor
2001-05-07 9:08 ` Eli Zaretskii
2001-05-03 23:58 ` Paul Hilfinger
2001-05-04 9:04 ` Andrew Cagney
2001-05-04 0:20 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2001-04-30 10:15 _WIN32? Christopher Faylor
2001-04-30 16:19 ` [Mingw-users] _WIN32? Danny Smith
2001-04-30 17:03 ` Christopher Faylor
2001-04-30 17:29 ` Danny Smith
2001-05-01 7:03 ` Kai Ruottu
2001-05-01 7:44 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010505225648.23019.qmail@web6404.mail.yahoo.com \
--to=danny_r_smith_2001@yahoo.co.nz \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox