Frozen Bubble NDK build process


#1

Hi, I write software for the Frozen Bubble game app, and saw that the APK released by F-Droid supports all processors, as Frozen Bubble requires the NDK to build the module player source.

I would like to know how you are accomplishing this in your make process so I can do the same, as the version on Google play is only for armeabi.


#2

Hi,

I would like to know how you are accomplishing this in your make process so
I can do the same, as the version on Google play is only for armeabi.

you can view our build metadata at


, but it doesnt show anything strange. Maybe you need to look up what buildjni
actually does on the buildserver.


#3

Maybe you need to look up what buildjni
actually does on the buildserver.

I would do this where?


#4

I figured it out, stackoverflow to the rescue.

I added APP_ABI := all to jni\Application.mk (previously only had jni\Android.mk) and now it builds for all targets.


#5

Hi,

glad you figured it out, however, we don’t modify anything from
upstream.

I figured it out, stackoverflow to the rescue.

I added APP_ABI := all to jni\Application.mk (previously only had jni\Android.mk) and now it builds for all targets.

We just have the Android.mk from upstream, more precisesly
https://github.com/videogameboy76/frozenbubbleandroid/blob/master/jni/Android.mk.

For building we just run ndk-build, as specified in:


#6

While I have your attention, I removed the advertisement completely some time back, so you no longer have to edit the code to set adsOn to default to false - the variable no longer exists.


#7