missytake/fdroiddata
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

MuPDF: Enable 1.5 builds

Browse source
This commit is contained in:
Boris Kraut 2014-08-09 23:58:10 +02:00
parent e9f0641aa8
commit 48c3ea110c
1 changed files with 36 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

49
metadata/com.artifex.mupdfdemo.txt
View file

@ -61,8 +61,7 @@ Build:1.2-MIPS,52
make generate make generate
buildjni=yes buildjni=yes
Build:1.5-ARM,53 Build:1.5,53
disable=wip
commit=1.5-ios-appstore commit=1.5-ios-appstore
forcevercode=yes forcevercode=yes
subdir=platform/android subdir=platform/android
@ -74,29 +73,53 @@ Build:1.5-ARM,53
buildjni=yes buildjni=yes
scandelete=build/debug/ scandelete=build/debug/
Maintainer Notes: Build:1.5,54
Source code is not up to date as far as android versioning goes. Our version commit=1.5-ios-appstore
codes probably differ from the official ones. forcevercode=yes
subdir=platform/android
submodules=yes
forceversion=yes
prebuild=sed -i -e 's/armeabi-v7a/x86/g' -e 's/android-8/android-9/g' jni/Application.mk && \
cd ../.. && \
make generate
buildjni=yes
scandelete=build/debug/
Looking at http://mupdf.com/downloads/ and platform/android/jni/Application.mk Build:1.5,55
the version scheme is like: commit=1.5-ios-appstore
forcevercode=yes
subdir=platform/android
submodules=yes
forceversion=yes
prebuild=sed -i -e 's/armeabi-v7a/mips/g' -e 's/android-8/android-9/g' jni/Application.mk && \
cd ../.. && \
make generate
buildjni=yes
scandelete=build/debug/
Maintainer Notes:
Our version codes differs until 1.5. With 1.6 we try to sync up with
upstream releases. They will try to tag android releases and update
their versionCode in the Manifest, too.
armeabi = baseversion + 0, e.g. mupdf-1.5-android-50-armeabi.apk armeabi = baseversion + 0, e.g. mupdf-1.5-android-50-armeabi.apk
armv7 = baseversion + 1, e.g. mupdf-1.5-android-51-armv7a.apk armv7 = baseversion + 1, e.g. mupdf-1.5-android-51-armv7a.apk
x86 = baseversion + 2, e.g. mupdf-1.5-android-52-x86.apk x86 = baseversion + 2, e.g. mupdf-1.5-android-52-x86.apk
mips= baseversion + 3, e.g. mupdf-1.5-android-53-mips.apk mips= baseversion + 3, e.g. mupdf-1.5-android-53-mips.apk
I'd assume baseversion corresponds to the versionName, e.g. 1.5 = 50. This The basename "bears no resemblance to the app version", however 1.4
would make 1.6 starting with verCode 60 up to 63 for the mips release. However, used 40 and 1.5 used 50. This would make 1.6 start with 60 -- or
the verCode has been 50 for ages (~2013!) and the devs in #ghostscript said: even a 16xx scheme.
"The android apk version numbers bear no resemblance to the app version."
Documents: Documents:
http://www.mupdf.com/docs/how-to-build-mupdf-for-android http://www.mupdf.com/docs/how-to-build-mupdf-for-android
http://mupdf.com/downloads/
http://twiki.ghostscript.com/do/view/MuPDF/AndroidReleases
http://git.ghostscript.com/?p=mupdf.git;a=blob;f=platform/android/jni/Application.mk;h=60909b6e9989b79231a6f3a7a04f371039185dbf;hb=HEAD
. .
Auto Update Mode:None Auto Update Mode:None
Update Check Mode:None Update Check Mode:None
Current Version:1.4 Current Version:1.5
Current Version Code:53 Current Version Code:55