Hey, compiled and built for arm.
Then tried to reconfigure for aarch64, did 5-8 steps from readme. and end result is again build for arm (armeabi-v7a)...
What am I doing wrong?
Done on Ubuntu 18.04.2 LTS on a virtual box.
PS - had to install/update clang and downgrade java to ver 8 (due to packaged gradle version)
you have to clean the kodi build dir before you change the target, or it will use cached data
(2019-04-01, 20:24)wsnipex Wrote: [ -> ]you have to clean the kodi build dir before you change the target, or it will use cached data
thanks that worked!
btw, configured --disable-debug and everything in log was prepared for 'release' but when building kodi still got 'debug' name in file - is it just naming leftover?
(2019-04-02, 13:46)cartman.dos Wrote: [ -> ] (2019-04-01, 20:24)wsnipex Wrote: [ -> ]you have to clean the kodi build dir before you change the target, or it will use cached data
thanks that worked!
btw, configured --disable-debug and everything in log was prepared for 'release' but when building kodi still got 'debug' name in file - is it just naming leftover?
Hi, did you get any update on the apk file name having 'debug'?
(2019-05-02, 23:29)atrdurai Wrote: [ -> ] (2019-04-02, 13:46)cartman.dos Wrote: [ -> ] (2019-04-01, 20:24)wsnipex Wrote: [ -> ]you have to clean the kodi build dir before you change the target, or it will use cached data
thanks that worked!
btw, configured --disable-debug and everything in log was prepared for 'release' but when building kodi still got 'debug' name in file - is it just naming leftover?
Hi, did you get any update on the apk file name having 'debug'?
Nah, but pretty sure it's not a debug ver, it's recognized as 'dirty' (guessing due to self-signed) and it functions like any other, plus the log file is not in debug mode. But IDK how a 'debug' ver would behave otherwise... so if someone can confirm that...