https://sourceforge.net/projects/alleg/files/allegro/5.0.10/

MD5SUMS
89110c288c4a1c1eb7e18951bca0f817  allegro-5.0.10.7z
bf51a90e158ff8b1cec0514ef70195cf  allegro-5.0.10.tar.gz
4a061a98d1a702f8b903f422c3804141  allegro-5.0.10.zip

A lot of work in this one!

My favorite:

Are most people installing both the stable (5.0) and unstable (5.1) branches? I'm running unstable only and don't want to miss out on anything.

I am running unstable only here. Development happens on the 5.1 branch and relevant changes are brought back into the 5.0 branch. You won't miss anything if you stick with 5.1.

I just grab whatever Michał builds

I prefer the unstable, because it's the bleeding-edge of features.

... So all the updates here have already been included in the latest unstable release (5.1.8). That makes sense.

Thank you!

Can we get a Windows Binary made? The bug with al_set_mouse_xy in windowed mode in 5.0.9 is preventing me from further development on my game. :/

There you go. Windows build is ready.

allegro-5.0.10-mingw-4.5.0.7z
allegro-5.0.10-mingw-4.5.2.7z
allegro-5.0.10-mingw-4.6.1-tdm.7z
allegro-5.0.10-mingw-4.6.2.7z
allegro-5.0.10-mingw-4.7.0.7z
allegro-5.0.10-msvc-11.0.7z
allegro-5.0.10-msvc-9.0.7z

Please let me know in case of problems related to builds.

Thanks Michał!

Ah! Thanks so much, Michal!

Whenever I see one of these threads and no Michal post, I wonder to myself "What the fuck am I going to do now?"

Thanks from me too!

Sorry to be so clueless but I'm wondering since I'm not a windows user. Is it really that hard to build allegro yourself on windows? On Linux, building is rather easy.

The base Allegro is easy to build, but all of the dependencies with an easy-to-distribute monolithic version? No.

Windows support feels like an afterthought in most of A5 dependencies. I made a guide to install A5 and the dependencies from source with MinGW, but that only worked predictably after I patched the dependency sources myself: it was a pain to figure out. The main offender is autotools, which leads me to predict that compiling everything with MSVC might be easier.

I don't use the builds myself, I'm just thanking Michal for putting in the time to help people that need them.

OK, I see. It's the dependencies that cause some problems. Could anything be done about that? If some libraries have non-restrictive licenses that are compatible with Allegro's it might be possible to vendor them...

Of course, I also think Michał is doing a great job in providing the windows builds.

Hi. I hope I'm not asking too much but could I ask you to compile a version for MSVC2010? It seems to be the one missing here this time, and I would need that exact version.

Thanks!

I wonder about missing 2k10 version too. I hope I just forgot to put it on ftp. I will check that on Friday.

Edit:

There it is. Fixed build for Windows. Sorry for troubles.

allegro-5.0.10-mingw-4.5.0.7z
allegro-5.0.10-mingw-4.5.2.7z
allegro-5.0.10-mingw-4.6.1-tdm.7z
allegro-5.0.10-mingw-4.6.2.7z
allegro-5.0.10-mingw-4.7.0.7z
allegro-5.0.10-msvc-10.0.7z
allegro-5.0.10-msvc-11.0.7z
allegro-5.0.10-msvc-9.0.7z

Will you be adding a compiled version for 4.7.1-tdm in the near future?

Whats wrong with using the one for 4.7.0?

That's another thing I've been wondering about as of lately: who do so many people still use allegro 4.x? What is allegro 5 missing that makes 4 more attractive?

Existing code?

But those two are talking about mingw/gcc 4.7.1 there's no such thing as allegro 4.7

I thought adding the -tdm would give it away that I was talking about MinGW 4.7.1-tdm.

I don't understand why people use the "tdm" version of MinGW in the first place...

Backward compatibility.

There you go:
allegro-5.0.10-mingw-4.7.1-tdm.7z

In my case, it defaults to link static run-time and produce executables without unwanted MinGW DLL. For games this is a good thing, I think.

`-static-libgcc -static-libstdc++` is all you need with regular MinGW.

Note: I don't even build my libraries with those switches, just the game.

That's true. I cannot recall more arguments. I just know people are using it.

Thanks Michal. I tested it and it works great. Just had to link openal and libwinmm.a which seemed to be unnecessary in 5.0.6, but everything is working nicely again.

At one point (I'm not sure if it's still the case), they were releasing newer versions of GCC before the MinGW team were.

Thanks Michal for MSVC2010 version!

Here's a contribution from me.

Allegro 5.0.10 - Compiled CHM API reference
https://www.dropbox.com/s/8oazl79tyfoad6n/allegro-5.0.10-doc.7z

Enjoy!

@ArekXV
Hey, nice contribution with the CHM docs!

It would be awesome if allegro's build system was capable of producing a CHM manual as well. How much work would that be? Are there any good guides for writing hhc / hhp files? I forget what all is involved in making chm docs.

If someone is looking for GCC for windows there is one up to date version prepared by Stephan T. Lavavej there. It is up to date in order to test newest C++ features.

Interesting. The guy works for Microsoft and maintains a version of GCC. .

Well you have HTML Help Workshop which is free, it's not that difficult to understand. You have a HHP file which is a project file, HHC is a content file and there is also an index file which is not required, but helpful.

Here's what I've done.

1. Download the whole API reference from allegro site using wget - you can get it for windows here - http://downloads.sourceforge.net/gnuwin32/wget-1.11.4-1-setup.exe
I've used this commad:
wget.exe --recursive --no-clobber --page-requisites --html-extension --convert-links --restrict-file-names=windows --domains alleg.sourceforge.net --no-parent alleg.sourceforge.net/a5docs/5.0.10

After it's finished it will create folder structure:
alleg.sourceforge.net/a5docs/5.0.10

You can stop here if you don't need the CHM version. HTML files work okay.

Then I've made a simple ruby script for making HHP, HHC and index files so that I don't have to add all of those content file index and stuff by myself, you can get it here:
https://www.dropbox.com/s/2tn6j5pv8unz6n5/generateHHP.7z

You put it inside:
alleg.sourceforge.net/a5docs/

And run it, enter folder name, which in this case is 5.0.10 and it will generate HHP, HHC and index files in it. It will also remove searchbox from all html files because javascript doesn't work very well in CHM.

After that you just run the chmproject.hhp file and compile the file which should be saved inside:
alleg.sourceforge.net/a5docs/

And that's it.

Also here's 5.1.8 - Compiled CHM api:
https://www.dropbox.com/s/3lka1o1xzwr0cxg/allegro-5.1.8-doc.7z

Allegro sources come with pregenerated documentation so there is no need top scrape the web site.

Haven't really looked at it. I see it now.

You can skip the download step and put the contents of generateHHP.7z into docs/html of allegro source.

Run generateHHP.bat and enter refman as folder name.

Rest is the same.

HTML Help Workshop is available here - http://go.microsoft.com/fwlink/?LinkId=14188

EDIT:

I've made a batch script which automatically generates necessary files and compiles CHM file.

All you need to do is to put the contents into docs/html of allegro source run generateCHM.bat and press Enter to begin.

Get it here:
https://www.dropbox.com/s/93queu1a4nvv4wc/generateCHM.7z

Please note that HTML Help Workshop needs to be installed for this to work. This script will look for it in Program Files directory.

Are there any chance to have allegro build for Visual Studio 2012 with Windows XP (v110_xp) toolset?

You can use standard MSVC2012 version for that, it's the same - http://targonski.nazwa.pl/thedmd/allegro/5.0.10/allegro-5.0.10-msvc-11.0.7z

ArekXV thanks for reply.

With this build there is one small problem, it is not targeting Windows XP operating system.
According to this post http://blogs.msdn.com/b/vcblog/archive/2012/10/08/10357555.aspx
To target Windows XP application and its dependencies must be built with v110_xp platform toolset selected.

Please reply if I'm missing something.

I will look at XP compatible build on Friday or Saturday.

Thanks.

Hmm you might be missing something here. I've tried compiling my project in MSVC2012 with Visual Studio 2012 - Windows XP (v110_xp) toolset and it compiled without any problems.

Again, I used this version - http://targonski.nazwa.pl/thedmd/allegro/5.0.10/allegro-5.0.10-msvc-11.0.7z

Can you write what kind of errors are you getting exactly?

This is not a compilation or linking issue, application just not running on Windows XP system, it is not compatible with it.

Did you try to run your application on Windows XP? Is it working?

Probably you'll get some error that I had:

---------------------------
Main.exe - Entry Point Not Found
---------------------------
The procedure entry point K32GetModuleFileNameExA could not be located in the dynamic link library KERNEL32.dll.
---------------------------
OK
---------------------------

That's not Allegro's issue (probably), you're probably using something which uses Process Status API, i.e. psapi.lib. I had a similar problem, you need to define a preprocessor directive:

Also you can try this:

Now I'm not 100% sure but I don't think that Allegro uses Process Status API.

Main cause for this error is because versions of Windows after Windows XP have moved functions (like those named upwards) from Process Status API (psapi.lib) to main kernel32.lib to gain more speed.

If Allegro uses psapi.lib then that's other story, and then it needs to be recompiled with MSVC2012 - Windows XP toolchain WITH preprocessor directive PSAPI_VERSION=1

Check your other libraries you are or might be using as well, if any of them are using psapi.lib then they should need to be recompiled too.

I managed to experiment with XP mode but weekend passed before I put a build together on that. There is a chance I will be near my dev PC tomorrow so I give it a try.

Yes you right.

But if allegro don't use PSAPI explicitly, it may use it implicitly via winmm or shell32 etc. libraries it linked with.

I think that even just small example allegro app won't run on xp with current build.