Quote:
Took a really quick look, and it seems to at least support shaders. If it does, it's quite likely that they're also required. If this is the case, we can forget it for now.

Keep in mind that neither Allegro nor SDL are game engines. They are libraries which are meant to make writing engines easier by having a couple of ready-made solutions for common tasks, and providing a uniform API across different platforms.

This is great news! My idea to make a shared library version of Allegro was to make a utility based on a C parser that would extract the macros that generate the DLL export function on Windows and generate an FD file or some such.

Quote:

It seems that Allegro is exporting number of globals which makes shared library quite complicated. It would have to be implemented as dual shared/link library but due to relatively low numbers of software options and EOL development it doesnt make sense.

Thanks for the tip. AROS 68k is already slated to use such a dual-library setup since it is AROS ABI v1. I was planning on writing an AROS version before I would've gotten around to setting up another MorphOS box (Mine died).

As for EOL, my interest is not so generally about Allegro games, but rather is about getting AllegroGL to work on AGA which is also EOL.

I understand that :) I was thinking hard about shared library but could not find enough motivation. Writing function description (#?.fd) files is the most boring part.

Quote:

Oh well, never mind then. Maybe the AROS guys will port it to their OS at some point.