Re: [AD] Old problems that still persist on Allegro 4.2 beta 3

[Elias Pschernig <elias@xxxxxxxxxx>]

On Thu, 2005-05-26 at 15:47 +0200, Elias Pschernig wrote:
> > Um, well, just the source code changed. And not a lot, just had to start
> > hacking around a bit to un-tangle some of the worst spaghetti code in
> > it. And I found a off-by-one bug when I restructured the dirty
> > rectangles code, can't remember details though.
> > 
> > Must now think about the best way to include it into the make process..
> > 
> 
> Patch attached. It got big, simply because it has every line of demo.c
> twice :P And I had to discover that the build system didn't support
> multi-sourcefile executables (except makedoc, which doesn't link Allegro
> though), so some changes where necessary (but the same changes are
> needed for any new demo as well - so adding that should now be easy).
> 
> The makefile.osx, makefile.vc, makefile.mgw, makefile.be, makefile.qnx,
> makefile.dj are all untested, but should work in theory. They use a
> target "*/%" which I seem to have forgotten about, so not sure if it now
> chooses the * target only if there's no other (as I assumed for the
> patch), or always (in which case, it won't work).
> 
> It works fine here with makefile.in in linux. I think that's all the
> platforms we support.. (BeOS and QNX probably are broken anyway..).
> 

Ok, committed it. There's no problem if the 4.2.0 distribution will have
a new demo, it's good in any case to think about how to include a
multi-file program in the build process. If my hacked in makefile rules
cause problems on some platforms in RC1, then we can try it with a
completely separate makefile. It's good to test this before the new demo
goes in in any case.

-- 
Elias Pschernig <elias@xxxxxxxxxx>