GNOME Bugzilla – Bug 796402
Linking error for android release 1.14.1 for all archs.
Last modified: 2018-11-03 16:13:22 UTC
Created attachment 372406 [details] Build Error Log file Hi, I am facing 'undefined reference' and 'incompatible target' linking error on android platform for all arch's in release 1.14.1. Build environment details are below. Host OS: Windows 7 Editor: Android Stuio 3.0.1 NDK version: r16 error logs and android.mk files are attached.
Created attachment 372407 [details] Android.mk file
It seems like it is always using the first architecture in Application.mk, so in your case x86. This did not seem to happen with a gradle based build that I tried some days ago. Can you provide a whole project for reproducing?
Ok. I will share a new app within few days. By the time, I observed continuous memory increase while using H/W decoders in this release. While using libav codecs, no memory increase observed. I used android studio profiler tool.
Created attachment 372446 [details] Android studio project file
This project is not yet complete but solving our purpose to reproduce build issue. I will make it a Test player for future issue. Note: you may get below warning/error message while opening the solution in Android Stuio. Just ignore that and try to build. Error:Execution failed for task ':app:preDebugAndroidTestBuild'. > Conflict with dependency 'com.android.support:support-annotations' in project ':app'. Resolved versions for app (26.1.0) and test app (27.1.1) differ. See https://d.android.com/r/tools/test-apk-dependency-conflicts.html for details.
I can't reproduce this when using a gradle build that uses an externalNativeBuild block instead of an explicit call to ndk-build. I tested with https://github.com/sdroege/gst-launch-remote. As noted above, the problem seems to be related to having multiple architectures in the APP_ABI line in Application.mk https://groups.google.com/forum/#!topic/android-ndk/Y1ozOWg1Cyw seems related, although claims to be an old bug that was fixed many years ago. In any case, I don't think this is a regression in the GStreamer binaries - it's something broken in ndk-build itself.
It would be worth trying e.g. with https://cgit.freedesktop.org/gstreamer/gst-docs/tree/examples/tutorials/android-tutorial-5 This probably does not happen with gradle but only with plain ndk-build.
(In reply to Sebastian Dröge (slomo) from comment #7) > It would be worth trying e.g. with > https://cgit.freedesktop.org/gstreamer/gst-docs/tree/examples/tutorials/ > android-tutorial-5 > > This probably does not happen with gradle but only with plain ndk-build. I will try this project in my environment and let you know. By the time, are we going to dig out what failing in case of plain ndk-build ?
Kim: any updates? Jan: did you make any more progress on this?
Tim: Build was successful after using externalNativeBuild for all arch's in Application.mk file. I am attaching modified gradle build file.
Created attachment 372627 [details] Modified gradle build file
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gstreamer-project/issues/14.