Allegro.cc - Online Community

Allegro.cc Forums » Allegro Development » Allegro 5.2.1.1 released!

This thread is locked; no one can reply to it. rss feed Print
Allegro 5.2.1.1 released!
SiegeLord
Member #7,827
October 2006
avatar

Allegro development continues at a frenzied pace, adding 2x more features, fixing 3x more bugs and introducing 4x more new bugs than before!

Not really... there were some serious issues with the 5.2.1(.0) release, so this patch release fixes those.

Check out the source archives here.

MSYS2 binaries are available here with the dependency packages available here.

You can grab the MSVC Nuget package here.

Ubuntu and homebrew will be updated in the coming days.

Changes from 5.2.1 to 5.2.1.1 (August 2016)

The main developers this time were: Trent Gamblin, SiegeLord.

Core

  • Enforce backwards compatibility in the version check, rather than erroneously allowing forwards compatibility.


  • Temporarily remove new extensions in ALLEGRO_OGL_EXT_LIST as that broke ABI compatibility.

OSX port

  • Temporarily revert changes in joystick detection, as it did not interact well with some joysticks.

Windows port

  • Fix the clear display to black right away to avoid an ugly white flash change.

SHA256SUMS

3fab4b595c83d9d9f5976b16063e9176372b81ecedeaf8e9cc981c3439e1b0c2  allegro-5.2.1.1.7z
973d77a99b6b7653dc2b200d280815cd589981a5df4896782ef4f3fce0a288ab  Allegro.5.2.1.1.nupkg
b5d9df303bc6d72d54260c24505889acd995049b75463b46344e797a58a44a71  allegro-5.2.1.1.tar.gz
9e7a18e4d91c16a5cbfb3ebd04300432b4ab17b51b803abd134373ab8efc2f95  allegro-5.2.1.1.zip
7841e14283189058ec7f8746dd79b2cb0463fc21c6199694fae4d6e57b6bff3f  allegro-mingw-gcc5.3.0-x64-dynamic-5.2.1.1.zip
174b6df88cfe11560a9d3b885257dd58bd8bd2f9fb101868ab312843911e4851  allegro-mingw-gcc5.3.0-x64-static-5.2.1.1.zip
a78f2b12313d924a4ce04679ece90f9fad0af127fdd41326895cf90dd37297a1  allegro-mingw-gcc5.3.0-x86-dynamic-5.2.1.1.zip
687f4ac79dced15d5f2e1d8111dd78e4e9452ac4c76caea62aa77861aeeae2e9  allegro-mingw-gcc5.3.0-x86-static-5.2.1.1.zip

"For in much wisdom is much grief: and he that increases knowledge increases sorrow."-Ecclesiastes 1:18
[SiegeLord's Abode][Codes]:[DAllegro5]:[RustAllegro]

Edgar Reynaldo
Member #8,592
May 2007
avatar

Just a note - the library fails to build if you use a recent version of freetype and you have compiled freetype with libpng support because it doesn't link to libpng and zlib.

Binaries for MinGW 4.8.1 and 5.3.0 are on the way. ;)

SiegeLord
Member #7,827
October 2006
avatar

Oh yeah, that's right. I'll make an issue about it on github an get it fixed for the next release. I should work on adding more and updating the existing dependencies to these binaries... in particular, I'm missing OPUS, as it's a bit of a pain to compile just like vorbis was.

"For in much wisdom is much grief: and he that increases knowledge increases sorrow."-Ecclesiastes 1:18
[SiegeLord's Abode][Codes]:[DAllegro5]:[RustAllegro]

Edgar Reynaldo
Member #8,592
May 2007
avatar

I'm assuming you mean the OPUS codec for audio, correct? When was that added? What I'd really like to see added is support for saving in .ogg format. I have yet to find a decent audio editor that I really like that isn't bloated with adware.

SiegeLord
Member #7,827
October 2006
avatar

OPUS support was added in 5.2.1.

"For in much wisdom is much grief: and he that increases knowledge increases sorrow."-Ecclesiastes 1:18
[SiegeLord's Abode][Codes]:[DAllegro5]:[RustAllegro]

Mark Oates
Member #1,146
March 2001
avatar

Was the ugly-white-flash-fix removed? :-[

Or just fixed? :D

SiegeLord
Member #7,827
October 2006
avatar

It was fixed.

"For in much wisdom is much grief: and he that increases knowledge increases sorrow."-Ecclesiastes 1:18
[SiegeLord's Abode][Codes]:[DAllegro5]:[RustAllegro]

Orochii Zouveleki
Member #11,166
July 2009
avatar

And here I was, finally building Allegro 5.2.1 about 2 days ago hahaha! I'm very tempted to make the change, but I'm satisfied with the previous version right now. How bad are those things fixed in this new version? Like, the white clear and all that. Right now I would update mostly to help with testing.

Nevertheless congrats for the new release and thanks for all the hard work!

SiegeLord
Member #7,827
October 2006
avatar

The joystick thing is probably the most likely issue you'll hit, but it's only on OSX.

"For in much wisdom is much grief: and he that increases knowledge increases sorrow."-Ecclesiastes 1:18
[SiegeLord's Abode][Codes]:[DAllegro5]:[RustAllegro]

Niunio
Member #1,975
March 2002
avatar

I was in stand by for a lot of time so my thread was closed. Anyway, it's a related theme so...

SiegeLord said:

I don't exactly know what is involved in this system none though, so somebody else needs to implement it. In particular, Allegro uses TLS pretty heavily inside pretty much everywhere, and that pthread crash might be TLS related. It might end up being a lot of work.

Sad to know about this. Unfortunately I have almost no experience with pthread and no-one with TLS (not sure what's TLS anyway, I didn't a lot C/C++ programming in the last decade), so I can't help. Anyway I can provide a minimal program that reproduces the error so you may trace it if you think it's worth of.

-----------------
Current projects: Allegro.pas | MinGRo

Edgar Reynaldo
Member #8,592
May 2007
avatar

Hi everybody.

I've put together some unofficial distributions of MinGW 4.8.1 and MinGW 5.3.0, as well as binaries of Allegro 4.4.3 from GIT as of 8/12/2016 and Allegro 5.2.1.1 for each version of MinGW. Each includes all the example and test programs as well as the addons and dependencies. Only monolith versions of Allegro 5 are provided.

See the associated thread for downloads and info :

https://www.allegro.cc/forums/thread/616446

Hope this helps get more people developing with Allegro!!! Happy coding! ;)

EDIT
Neil Roy downloaded my distro for MinGW 5.3.0 and Allegro 5.2.1.1. He had some issues with the timer behavior in his program. See the associated bug reports below :
https://www.allegro.cc/forums/thread/616446/1024510#target
https://www.allegro.cc/forums/thread/616446/1024512#target

ex_timer_pause when run from the command line does nothing and returns immediately. When run from gdb it pauses normally. printf output does not work with either case. It simply does not appear.

In the changelog for 5.2.0 some timer behavior was changed. Perhaps that is the cause of these strange effects.

Gideon Weems
Member #3,925
October 2003

Whoo hoo! I git pulled the upgrade without even noticing... That's what I get for not frequenting the forums enough.

Thank you.

Edgar Reynaldo
Member #8,592
May 2007
avatar

Mark Oates
Member #1,146
March 2001
avatar

It's too bad I'm on mac now. But when I'm on PC I'll be sure to use them. :)

Neil Roy
Member #2,229
April 2002
avatar

Sorry, haven't been programming a lot lately. I can't test out DLLs, I statically link. I should probably use DLLs perhaps, but when I went to use them, I got errors and my enthusiasm is already fairly low so... ;)

Edgar Reynaldo
Member #8,592
May 2007
avatar

DLLs should technically be easier to use, as you only need to link to the allegro monolith and then include the dlls with your exe.

If you're getting errors, you should post them. Maybe I can help. And maybe they're my fault for building it wrong somehow. If you don't post, I don't know.

EDIT
I uploaded a static debug lib for you to try :
https://www.allegro.cc/forums/thread/616446/1024739#target

EDIT2
Neil reports the issue is fixed now. I've uploaded new binaries with the patch applied. As well, they now include the static version of libFLAC, which was missing from the first versions.

Get them here :

Allegro5211_MinGW4814_Rel2.tar.7z

Allegro5211_MinGW5302_Rel2.tar.7z

Gideon Weems
Member #3,925
October 2003

Neil Roy said:

I can't test out DLLs, I statically link. I should probably use DLLs perhaps, but when I went to use them, I got errors and my enthusiasm is already fairly low so... ;)

Weird. I'm used to this being the other way around.

Neil Roy
Member #2,229
April 2002
avatar

Weird. I'm used to this being the other way around.

I never had a problem statically linking and I hate having to remember which DLLs to include etc. I find this way just easier. When it's compiled, everything that is needed is in the executable. No fuss, no muss. ;)

Edgar Reynaldo
Member #8,592
May 2007
avatar

Neil Roy downloaded my distro for MinGW 5.3.0 and Allegro 5.2.1.1. He had some issues with the timer behavior in his program. See the associated bug reports below :
https://www.allegro.cc/forums/thread/616446/1024510#target
https://www.allegro.cc/forums/thread/616446/1024512#target

ex_timer_pause when run from the command line does nothing and returns immediately. When run from gdb it pauses normally. printf output does not work with either case. It simply does not appear.

In the changelog for 5.2.0 some timer behavior was changed. Perhaps that is the cause of these strange effects.

...

Neil reports the issue is fixed now.

For reference, and for anyone else who may be experiencing an issue with the timers in Allegro 5.2.1.1 with their applications, the fix is to add a line in timernu.c. Insert this line after line 106 of allegro/src/timernu.c and recompile allegro to fix this issue :

allegro/src/timernu.c#SelectExpand
104 al_lock_mutex(timers_mutex); 105 while (_al_vector_size(&active_timers) == 0 && !destroy_thread) { 106 al_wait_cond(timer_cond, timers_mutex);
107+ old_time = al_get_time() - interval;
108 } 109 al_unlock_mutex(timers_mutex);

Also, Trent told me the reason ex_timer_pause returns immediately from the command line is because it is compiled as a graphic application instead of a console program. This change in the way the examples are compiled was introduced recently. I don't know if it affects any of the other example programs.

Go to: