I just committed the android port to Allegro 5's subversion repo. What is done, works fine. What isn't done, doesn't work at all.

Basically a single display at a time, with touch and key events, is all that is done right now. That leaves file system access, apk package access, sound, accelerometer (some of the code for this is already done), camera access, some cleanup, and a bunch of tweaks to polish it up.

Those wanting to try out the new port, fetch and build Allegro 5.1 from subversion and let me know how it goes I expect problems, so don't hesitate to tell me about them.

I'm too busy with Santahack right now to try it, but this is awesome news.

{"name":"605236","src":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/0\/6\/06f324ef73229b8d03e1e3694998ab28.png","w":256,"h":256,"tn":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/0\/6\/06f324ef73229b8d03e1e3694998ab28"}

I might try this later today if I ever wake up.

Compilation fails when it gets to the opengl stuff

/opt/android/arm-linux-androideabi-4.4.3/bin/arm-linux-androideabi-gcc  -Dallegro_EXPORTS -fPIC -DANDROID -mthumb -Wno-psabi -march=armv7-a -mfloat-abi=softfp -W -Wall  -O2 -g -fPIC -I/opt/android/arm-linux-androideabi-4.4.3/arm-linux-androideabi/include/c++/4.4.3/arm-linux-androideabi -I/home/jon/svn/allegro/5.1/include -I/home/jon/svn/allegro/5.1/b/include    -DALLEGRO_SRC  -DALLEGRO_LIB_BUILD -o CMakeFiles/allegro.dir/src/opengl/extensions.c.o   -c /home/jon/svn/allegro/5.1/src/opengl/extensions.c
In file included from /home/jon/svn/allegro/5.1/src/opengl/extensions.c:22:
/home/jon/svn/allegro/5.1/include/allegro5/allegro_opengl.h:70:21: error: GLES/gl.h: No such file or directory

On my system I installed the standalone toolchain to /opt/android/arm-linux-android-eabi-4.4.3. The ndk is extracted to /opt/android. As far as I can tell GLES/gl.h only lives in /opt/android/platforms/android-4/arch-arm/usr/include/GLES/gl.h so -I/opt/android/platforms/android-4/arch-arm/usr/include would have to be added to the compilation line.

Does Cmake expect opengl stuff to be in the standalone toolchain?

<edit>
I got it all to work. I had created the standalone system using --package-dir instead of --install-dir. This is an important distinction. Also the directions currently say to use --platform=4 but GLES2 and EGL only exist in higher versions (at least in ndk6) so I used --platform=9.

I ran the test application from android-project on my galaxy pad. I had to hack the makefiles and stuff to not use liballegro-debug.so but rather just liballegro.so. The test application shows a white box that you can touch and move around red boxes. I was able to press all 10 of my fingers and have 10 boxes show up!

It shouldn't take too much work. The Toolchain-android.cmake file just needs a couple more variables. Also it is not a standard CMAKE_TOOLCHAIN_FILE file. I tried to make it one of those, but the code that was needed does some stuff that doesn't work in a CMAKE_TOOLCHAIN_FILE file. Apparently toolchain files are included more than once in a run, and at least one of the times, its given an EMPTY environment, but its never the first pass. So its completely borked as a CMAKE_TOOLCHAIN_FILE file. Could probably just get rid of that file and stick it all in the main cmake file.

Very possible. I just went as far as getting graphics up, and the flicker doesn't happen on the nexus s, so I didn't know it happened at all, otherwise I'd have fixed it :-x

I'm not sure the emulator supports all the stuff we're using.

I don't really care if it works in the emulator, I care if it works on actual devices, so that's what (I) we test with. You're welcome to try it if you like, but I have my doubts as to its usefulness.

You need to remove the options that aren't supported by your OS. You'll need to find the docs on that, I found them with a google search. They'll mention "available on OS version XX" or something like that if they're additions. Then edit the java file and comment out the lines pertaining to those elements you removed from the configChanges option. It should give you errors with line numbers, but the lines will begin with lines similar to the ones you remove "..SCREEN_SIZE" etc.

Did you copy the allegro libraries into the jni dir? And since you didn't use the debug version, you need to edit AllegroActivity.java to load the regular lib rather than debug.

As for the configChanges option, I "Fixed" that by targeting Android 4.0, it runs fine on 2.3.4, I just don't get those events that came with 4.0.

Is it crashing, or not compiling? Crashing leads me to believe its actually compiling. Sadly without the debug version of allegro, we can't see any decent logs from 'adb logcat'.

If/when you build a debug version of allegro, and the app (ant debug), please run 'adb logcat' before launching the app, and let it continue to run till after the crash. then post the log here

But that stackoverflow solution is basically what I did. Changed the target to the 4.0 sdk, and things just work, even on 2.3.4.

no no... What Thomas wanted to say was: "then post the log here "

Try running with logcat. In one terminal run 'adb logcat', what for it to spew out its messages, then in another terminal use the adb -d shell command from the readme to run the app manually. The logcat window will print a ton of debug info. In my case it narrowed the problem down.

It strips off the lib part.

But that is the error all right, it can't find the allegro library. You absolutely sure you've coppied the liballegro-debug.so library into the jni/armeabi-v7a dir, and that you've fully uninstalled, rebuilt, and installed your app?

Ok, that should work. I've had similar issues in the past, where it just wouldn't recognize a change for some reason. Try 'ant clean', and 'ant debug' again. then see if it won't install and run.

Oh hey, also make sure you've changed the Java_ function names in the android_system.c and android_display.c files to match your new package name. I forgot to put that in the README. It shouldn't cause this error, rather it'd cause a different unsatisfied link error mentioning symbols couldn't be found.