[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Sat, 12 May 2012 19:19:43 -0600, Trent Gamblin <trent@xxxxxxxxxx> wrote:
> On 2012-05-12, at 7:14 PM, Peter Wang wrote:
> > Hi,
> >
> > I got a bit further but still can't get the Android port to run on my
> > 2.2 device.
>
> It's certainly possible, I'm running it on 2.1.
Thanks, that's good to know.
> > Firstly, liballegro.so wouldn't load. It seems that libandroid.so was
> > introduced in 2.3 for NativeActivity (maybe amongst other things).
> > Do we really need to link with that library? It turns out we don't link
> > it if WANT_ANDROID_LEGACY is set, but I thought that meant Android 1.6 or
> > thereabouts, which is why I didn't think to set it.
>
> You want to set WANT_ANDROID_LEGACY. It's meaning is kind of fuzzy but
> you likely need to build for armv6. You still shouldn't set WANT_GLES2 off though.
>
> > Next, the user application liballegro-example.so won't load.
> > I guess it's unable to find or load liballegro-debug.so, etc. even
> > though they're in the /data/data/org.liballeg.app/lib directory as well.
> > Any ideas? dlerror is particularly useless.
>
> In the project directory you should put your allegro_*-debug.so's in
> jni/armeabi.
Yeah, I tried that as well (LEGACY, armv6, using strace on the process
as it loads in adb (ridiculous)). Still nothing.
Can you provide an apk for me to test?
Peter