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

OsmAnd~: Prepare v2.0.0 gradle support

Browse source
This commit is contained in:
Boris Kraut 2015-04-26 14:21:45 +02:00
parent f3f47e2947
commit 8a3504e112
1 changed files with 6 additions and 4 deletions

10
metadata/net.osmand.plus.txt
View file

@ -139,15 +139,15 @@ Build:1.9.5,197
ndk=r10d ndk=r10d
#use v2.0.0 branch #use v2.0.0 branch
Build:2.0,200 Build:2.0.1,200
disable=builds and is usable disable=testing
commit=d2327391a0ba102a422e825b9a2fbfcae6b3c9b6 commit=44cfaa5db6d0c8ef9af0fa7eaa2ff8d8392f3d86
subdir=android/OsmAnd subdir=android/OsmAnd
submodules=yes submodules=yes
build=../../build build=../../build
gradle=fullLegacyFat
buildjni=no buildjni=no
ndk=r10d ndk=r10d
output=build/outputs/apk/OsmAnd-full-legacy-fat-release-unsigned.apk
Maintainer Notes: Maintainer Notes:
No UCMs apply because git never contains actual releases, only pre-releses. No UCMs apply because git never contains actual releases, only pre-releses.
@ -159,6 +159,8 @@ Upstream now uses gradle. We invoke gradle from within ../../build which might
break on the BS. We should try to use gradle=fullLegacyFat to build like `gradle break on the BS. We should try to use gradle=fullLegacyFat to build like `gradle
clean assembleFullLegacyFatRelease`. Versioname is off, e.g. "2.0.02.0" instead clean assembleFullLegacyFatRelease`. Versioname is off, e.g. "2.0.02.0" instead
of "2.0" -- it looks like our forcing is no longer necessary. of "2.0" -- it looks like our forcing is no longer necessary.
I don't know where the 2.0.1 is comming from..
. .
Auto Update Mode:None Auto Update Mode:None