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 5.2.4.1 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 :

i686-8.1.0-release-posix-dwarf-rt_v6-rev0.7z

Here are the binaries for Allegro 5.2.4 :

Allegro524_mingw-w64-gcc81_posix_dwarf.7z

And here are the binaries for Allegro 4.4.3 :

Allegro443_mingw-w64-i686-gcc81_posix_dwarf.7z

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 :

Allegro443.chm

Allegro524.chm.

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 :

http://members.allegro.cc/EdgarReynaldo/BuildA5.html

Thank you Neil, .

What did you think of the compile guide?

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.

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.

x86_64 indicates 64 bit binaries

The exception handling is different too.

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 :
{"name":"611485","src":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/2\/7\/27b87424a2315d6e25157dcba1b2a609.png","w":691,"h":439,"tn":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/2\/7\/27b87424a2315d6e25157dcba1b2a609"}

EDIT
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.

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!!!