Build fails with Allegro 5.2.x about microwindows

[ghaerr]

I will have to look into this. The Allegro driver library v5.1.13 will not build on my OS X system, so I am using v5.2.4. The Microwindows scr_allegro5.c was updated by me for speed but uses no new Allegro API calls, just rearrangement for a single update operation per select() cycle, so you should be fine with using v5.1.13 for Android. Can you verify that v5.1.13 still compiles and works for you?

[nwrkbiz]

Jep v5.1.13 works perfectly fine, but switching to v5.2.4 would make sense, because they have fixed some stuff that made allegro crashing on android. (changing screen orientation, put app to background etc., ...)

What allegro header files are you using, the ones from the v5.2.4 source tarball?

[ghaerr]

Yes, I’m using the headers from the 5.2.4 source .zip file. Is is possible they renamed that MOUSE_EMULATION mode that your app build fails on, except that it compiles on OS X.

…

On Feb 4, 2019, at 9:51 AM, Daniel G. ***@***.***> wrote: Jep v5.1.13 works perfectly fine, but switching to v5.2.4 would make sense, because they have fixed some stuff that made allegro crashing on android. (changing screen orientation, put app to background etc., ...) What allegro header files are you using, the ones from the v5.2.4 source tarball? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#17 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALbi5QPi_qRCS9V7JfuKss7leB5IJX7Bks5vKGUmgaJpZM4ahWEA>.

[nwrkbiz]

#define ALLEGRO_UNSTABLE is missing before the allegro.h include, seems like this mouse emulation stuff is considered as unstable by allegro :) I created a pull request.