OsmAnd~: Prepare v2.0.0 gradle support
This commit is contained in:
parent
f3f47e2947
commit
8a3504e112
|
@ -139,15 +139,15 @@ Build:1.9.5,197
|
|||
ndk=r10d
|
||||
|
||||
#use v2.0.0 branch
|
||||
Build:2.0,200
|
||||
disable=builds and is usable
|
||||
commit=d2327391a0ba102a422e825b9a2fbfcae6b3c9b6
|
||||
Build:2.0.1,200
|
||||
disable=testing
|
||||
commit=44cfaa5db6d0c8ef9af0fa7eaa2ff8d8392f3d86
|
||||
subdir=android/OsmAnd
|
||||
submodules=yes
|
||||
build=../../build
|
||||
gradle=fullLegacyFat
|
||||
buildjni=no
|
||||
ndk=r10d
|
||||
output=build/outputs/apk/OsmAnd-full-legacy-fat-release-unsigned.apk
|
||||
|
||||
Maintainer Notes:
|
||||
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
|
||||
clean assembleFullLegacyFatRelease`. Versioname is off, e.g. "2.0.02.0" instead
|
||||
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
|
||||
|
|
Loading…
Reference in a new issue