From mboxrd@z Thu Jan 1 00:00:00 1970 From: DJ Delorie To: gdb@sources.redhat.com Subject: Re: DOS/Windows-specific code: all the rest Date: Tue, 08 May 2001 09:45:00 -0000 Message-id: References: <20010503211502.21716.qmail@web6401.mail.yahoo.com> <3AF1DAA0.3060702@cygnus.com> <200105071609.TAA24129@is.elta.co.il> <200105081157.OAA06357@is.elta.co.il> X-SW-Source: 2001-05/msg00134.html Eli Zaretskii writes: > - What's the story with files 29k-share/udi/ ? udi2go32.c seems to > be DJGPP-specific, while udi2soc.c and udr.c are the other way > around: all their code is ifdef'ed away under DJGPP. I wrote those. UDI required a custom version of go32 that had the UDI interface libraries linked in, and a custom API between that go32 and the program. It was quite a hack. On unix systems, the UDI interface always sits on the other side of a socket, and it talks to the hardware (or simulator) on your behalf. UDI, btw, has a standard interface for all boards and simulators, so that one debugger binary works with every target. You can't just code something in gdb and be done with it, you *have* to talk to these UDI modules, which are provided by the vendor. So, there needs to be one interface for each class of host environment that UDI drivers exist for.