

Just as a side note, both Allegro and MinGW have new versions, MinGW is on 4.9.0 while Allegro has its 5.1 out (with a new API). The only time I had gone there for help they were really helpful. Unfortunately Allegro is not an easy to build library, on the contrary, it takes a lot of time, needs some specific DirectX files and other libraries, a pain go to this link if you want to give this a try.ġ - Try adding the -fexceptions option to your compiler flags (right before `pkg-config -cflags -libs allegro-5.0 allegro_primitives-5.0` ), it's worth a try.Ģ - Go to the forums and ask if anyone has the binaries for 4.8.1. The second obvious answer is telling you to compile Allegro 5.0.10 on your own instead of getting the binaries.

The obvious answer I could give you would be to download the Allegro binaries for MinGW 4.8.1, but I checked and they don't exist (these are community maintained, can't really complain). When I wrote that short tutorial I was using MinGW 4.8.1 myself this shouldn't be the problem. There is a complete guide to the process here. The unstable (development) versions of Allegro do not come in a binary format, so you will have to build them yourself from source - you could also build the stable version from source as well so that it does match your MinGW version.īuilding from source is not particularly difficult, but can take a while as you will need to download the tools (cmake, git etc) if you don't already have them and you will first need to build the dependencies. If you do decide to install the older version of MinGW to match the binaries you have then yes, you will need to uninstall the version you have now. Should I try to find the matching older version of MinGW and download that instead (and would I need to uninstall the current one)? Or should I try one of the unstable builds of Allegro in the hopes that it might have caught up with the compiler version (though this cmake business always confuses me)? Dynamic linking will not help either, as the problem is that the binaries are for a different version of MinGW. There is no official binary for the latest version of MinGW. That page is outdated as it states the latest version of MinGW as 4.7.0.

If static linking doesn't work, try dynamic linking. I don't know but maybe you it works better if you follow the instructions on the official wiki.
