安卓mupdf的MIPS和x86架构 [英] android mupdf for MIPS and x86 arch
问题描述
即时通讯目前使用 MuPDF
在我的Android应用程序,当我建造它从源代码(基于的ReadMe.txt)它只生成。所以
文件 armeabi
和 armeabi-V7A
而不是 86
和 MIPS
,当我的胳膊拱设备上运行应用程序(三星Galaxy Tab 7),它看起来很不错。但不是在 MIPS
拱。我的问题是我怎么能生成 86
和 MIPS
共享对象文件?如果没有其他解决办法,我将AP preciate吧...
im currently using MuPDF
in my android application, when i built it from source (based on ReadMe.txt) it's only generate .so
file for armeabi
and armeabi-v7a
but not x86
and MIPS
, when i run the app on arm arch devices (Samsung Galaxy Tab 7), it looks good. But not in mips
arch. my question is how i can generate x86
and MIPS
shared object file? if any other solution, i will appreciate it...
PS:我使用的Android NDK r8d
,我试着用来改变的Android NDK-R6B
但我得到了同样的问题。
PS: i'm using android ndk r8d
, i tried to change with android-ndk-r6b
but i got same problem.
推荐答案
如果你在安卓/ JNI / Application.mk的mupdf源中,您将看到一行:
If you look in android/jni/Application.mk within the mupdf source you will see a line:
APP_ABI = armeabi armeabi-v7a
您可以做这样的:
APP_ABI = armeabi armeabi-v7a x86 mips
甚至是:
APP_ABI = all
启用其他架构。
to enable the other architectures.
这将导致问题目前成为Android / JNI / Core.mk和Android / JNI / Core2.mk文件定义-DARCH_ARM和-DARCH_THUMB(因为当时他们写的,机器人只支持ARM处理器)。这需要一点魔术的preprocessor:
This will cause problems currently as android/jni/Core.mk and android/jni/Core2.mk files define -DARCH_ARM and -DARCH_THUMB (as at the time they were written, Android only supported ARM processors). This needs a bit of magic with the preprocessor:
ifeq ($(TARGET_ARCH),arm)
LOCAL_CFLAGS += -DARCH_ARM -DARCH_THUMB -DARCH_ARM_CAN_LOAD_UNALIGNED
ifdef NDK_PROFILER
LOCAL_CFLAGS += -pg -DNDK_PROFILER -O2
endif
endif
LOCAL_CFLAGS += -DAA_BITS=8
我会放在这些修复 - 看我们的混帐回购协议,在未来几天。 编辑:修复目前正致力于
I will get fixes put in for these - watch our git repo over the next couple of days. Fix is now committed.
这篇关于安卓mupdf的MIPS和x86架构的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!