A5, MinGW-W64, GCC8.1, binaries, and compile guide
Edgar Reynaldo

Update 06/14/2018 - I also made a binary package for Allegro 4.4.3. Get them below. ;)

Hello again fellow allegator(ette)s!

I've put together a new binary release of Allegro using the new GCC 8.1 provided by MinGW-W64.

VVV Get them hot off the press here!!!111 VVV

First you need the compiler they were built with, which you can find here :


Here are the binaries for Allegro 5.2.4 :


And here are the binaries for Allegro 4.4.3 :


The binaries include dynamic and debug static and shared monolithic versions of allegro 5, along with all the dependencies.

It includes all the example, test, and demo programs built in dynamic debugging mode.

It includes html and CHM docs. Get the CHM by itself here :



Respectively, there are .bat files named RunA524Examples.bat and RunA443Examples.bat depending on the version you downloaded. If you run it, it will add the bin/dlls folder to the path and put you in the examples directory so you can easily run any example at will. It also sets up several environment variables named A5INCDIR, A5LNKDIR, and A5STATICLIBS for Allegro 5 and A4INCDIR, A4LNKDIR, and A4STATICLIBS for Allegro 4. Using them on the command line makes compiling much easier.

Don't forget to add mingw/bin to your path and then you can use the env vars in the following manner :

g++ -Wall -g -o test.exe -DALLEGRO_STATICLINK -I %A5INCDIR% test.cpp -L %A5LNKDIR% -lallegro_monolith-debug-static %A5STATICLIBS%

During my latest build of allegro, I documented the process, so it will be easier for anyone else who wants to build allegro on windows using mingw.

I put the guide up on my member website. You can find it here :



Nicely done Edgar! Thanks.

Edgar Reynaldo

Thank you Neil, ;).

What did you think of the compile guide?

Frank Drebin

Thanks Edgar!

I wanted to try Allegro 5 anyway so I'll give it a try within the next days... Will these files be added to the official resource page?

For me it is not clear if there is a 64-bit version of allegro 5 on allegro.cc or on liballeg.org available yet. When I saw these 4 precompiled binary files
I was wonderwing why all of them contain 'mingw32' in their name. This looks like all of them are using the 32-bit version of MinGW and thus will produce 32-bit binaries as well. Or what is the difference between these 4 files?


I was wonderwing why all of them contain 'mingw32' in their name

Because they were compiled for the MingW32 compiler as stated in the first post. It's typical to name library files based on what architecture/compiler they are compiled for.


What did you think of the compile guide

I honestly didn't look at it until now, but looks impressive! This is the sort of thing that is needed to help people.

Edgar Reynaldo

In the compile guide I mentioned it was 32 bit, but I didn't mention that above.

Building a 64 bit version should be just as simple if you replace the 32 bit compiler with a 64 bit one.

Frank Drebin

If the 'mingw32' in their names indicates that these 4 packages are built for the 32-bit version of mingw (2x dynamic and 2x static versions) what's the difference between 'allegro-i686-w64-mingw32-gcc-7.2.0-posix-dwarf-dynamic-' and 'allegro-x86_64-w64-mingw32-gcc-7.2.0-posix-seh-dynamic-' ?

Edgar Reynaldo

x86_64 indicates 64 bit binaries

The exception handling is different too.


If the 'mingw32' in their names indicates that these 4 packages are built for the 32-bit version of mingw

No, that's not why. x86_64-w64-mingw32 is a target triple, consisting of 3 parts:

  1. Architecture - x86_64 or i686, for 64 and 32 bits

  2. Vendor - w64, because the official binaries use mingw-w64 for compilation.

  3. System - Mingw32, 32 means nothing.

Edgar Reynaldo

SiegeLord and I use different processes to build our binaries. SL, did you convert all the dep libs to CMakeLists.txt format?

As I mentioned in the compile guide, I had to use MSYS 1.0.11 to build ogg, vorbis, theora, and flac, which all compile flawlessly minus a bug in one of the theora examples.

Everything else provides a CMakeLists.txt build script for CMake. That's all I use. It's super simple once you get the hang of it, and cmake-gui makes configuring everything super simple, while still allowing you to make alterations on the command line if necessary. ENet has no install target, and they only build static libs, so I hacked their CMakeLists.txt to build dynamic libs too. All that is provided in my source pack.

Here are the versions used :

Can anyone give me some tips on a better layout for the compile guide? It's just a super simple html hack I put together. I didn't put it on the wiki b/c the wiki hates me. Thinks I'm a spammer, probably because of the page I put up to mirror Gideon Weems hall of shame, which was full of borked hyperlinks.

Frank Drebin

Thanks for the explanation SiegeLord! It was the 'mingw32' that confused me but as you mentioned the 32 means nothing and 'mingw-w64' is used for compilation actually. Now it all makes sense to me ;D

Edgar Reynaldo

Forgot to say, DUMB is in there too. Got it built from GIT finally. I suppose I should put the version I used in the source pack I provided....

EDIT 06/10/2018
I'll be posting a new binary distro of Allegro 4.4.3 here in the next few days. Bump for lock free sailing!

EDIT 06/14/2018
Look at the OP for the new Allegro 4.4.3 binaries!!!

Thread #617424. Printed from Allegro.cc