[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: Coordination of admins/developers of the game programming library Allegro <alleg-developers@xxxxxxxxxx>
- Subject: Re: [AD] 4.3.10+ branch
- From: Elias Pschernig <elias@xxxxxxxxxx>
- Date: Wed, 23 Jul 2008 22:24:56 +0200
On Wed, 2008-07-23 at 18:56 +1000, Peter Wang wrote:
> On 2008-07-23, Thomas Fjellstrom <tfjellstrom@xxxxxxxxxx> wrote:
> > On July 23, 2008, Milan Mimica wrote:
> > > Peter Wang wrote:
> > > > On 2008-07-22, Milan Mimica <milan.mimica@xxxxxxxxxx> wrote:
> > > >> Peter Wang wrote:
> > > >>> There's also the no-asm issue on djgpp.
> > > >>
> > > >> What's that?
> > > >
> > > > http://www.allegro.cc/forums/thread/596566
> > >
> > > Since when we care about people trying to run DJGPP executables on WinXP?
> >
> > I'm not 100% certain but I think it effects pure DOS exes as well. Its as if
> > noone ever tested the C only mode with DOS (and I mean pure C, with all of
> > the asm disabled including various drivers that depend on it, and all of the
> > fancy allegro calling conventions..)
>
> Exactly. I might try it in qemu later.
>
I can confirm that most examples crash in qemu (the only two who open a
graphics mode and work here are exfont and extimer I think).. but I have
no idea how to debug it. If I run gdb, it stays in fullscreen and all I
can do is close the qemu window :/
Also, with my qemu setup, compilation took almost an hour.. much longer
than it took in real DOS back then - so that's no good for doing much
testing either.
Does someone remember what exactly the problem is? Why would the C-only
version need non-C calling convention for anything?
--
Elias Pschernig <elias@xxxxxxxxxx>