Compile guide using Osmand-manifest is IMHO unnecessarily too complicated. You can make it manually and it just works. My compile guide: mkdir ~/osmand cd ~/osmand git clone https://github.com/osmandapp/OsmAnd-core -b legacy_core core-legacy git clone https://github.com/osmandapp/Osmand Osmand git clone https://github.com/osmandapp/OsmAnd-resources resources # help module is optional git clone https://github.com/osmandapp/osmandapp.github.io help
export ANDROID_SDK=/opt/android-sdk-update-manager export ANDROID_NDK=/opt/android-ndk/ cd Osmand ./gradlew --refresh-dependencies assembleFullLegacyFatDebug assembleFull means you build Full version instead of Free version, Legacy means you build with legacy core (instead of Qtcore), Fat means you build for every architecture (instead of e.g. armv7). You can get possible combinations from ~/osmand/Osmand/OsmAnd/build.gradle W dniu piątek, 23 września 2016 03:43:20 UTC+2 użytkownik [email protected] napisał: > > > The current status of my build attempt, following the instructions at > https://github.com/osmandapp/OsmAnd-core are as follows: > > > - I'm building armeabi-android-gcc.sh instead of amd64-linux-gcc.sh. > > > - I had to correct build/target/android-gcc.cmake to set > system_lib_dirs to include > > ${toolchain_root}/lib/gcc/${toolchain_prefix}/${toolchain_version}.x/${toolchain_lib_subpath}. > > That is, i had to add ".x" after ${toolchain_version}. > - Compilation currently fails with "cannot find -lgnustl_shared. This > is frustrating since gnustl_shared is found using find_library(), which > returns the full path. At some point, CMake is throwing away the full > path > and then complaining that the library cannot be found... > > -- You received this message because you are subscribed to the Google Groups "Osmand" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
