<div dir="auto">Shortly before a release there are several RC (release candidate) builds. That is the perfect time to perform this testing and identify and fix problems. </div> <div class="gmail_quote"><div dir="ltr">On Thu, Apr 12, 2018, 3:51 AM Sebastian Dröge <<a href="mailto:sebastian@centricular.com">sebastian@centricular.com</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, 2018-04-11 at 15:25 -0700, Mikel Pérez wrote: > I've been writing a music player (for replaygain, faster library > scanning than mediastore + caching external storage results, better > API overall than android's MediaPlayer, etc) for a while and tried to > update to 1.14.0, but I can't compile my app because of these > messages: > [...] That's this bug here: <a href="https://bugzilla.gnome.org/show_bug.cgi?id=794599" rel="noreferrer noreferrer" target="_blank">https://bugzilla.gnome.org/show_bug.cgi?id=794599</a> It also should affect iOS for the same reasons, and will be fixed with 1.14.1. > also, while I can compile with 1.12.4, I can't run the x86 version > due to text rellocations: > [...] This is probably <a href="https://bugzilla.gnome.org/show_bug.cgi?id=742633" rel="noreferrer noreferrer" target="_blank">https://bugzilla.gnome.org/show_bug.cgi?id=742633</a> and not fixed in 1.14 from what I can see. You need to disable the libav and x264 plugins as the code of the underlying libraries has text relocations. In general, please always report in Bugzilla if something does not work so that it can be fixed :) > so it seems this 1.14.0 release is borked for android, and the > previous one was borked for x86 android. is the project still being > maintained? I'd hate to see it go because I found the perfect lib for > my musicplayer It's still maintained and people are using it in production, but unfortunately not much testing from 3rd parties seems to happen in GIT master and also not with pre-releases, so such problems only show up after the releases then. So bugs that don't affect everybody might get unnoticed until someone actually tests the new release in their application that makes use of the affected features, and then reports them. The first one for example only happens if you use both the dtls plugin and souphttpsrc with TLS support, the second one only happens on x86 if using the x264 or libav plugin. -- Sebastian Dröge, Centricular Ltd · <a href="http://www.centricular.com" rel="noreferrer noreferrer" target="_blank">http://www.centricular.com</a>_______________________________________________ gstreamer-android mailing list <a href="mailto:gstreamer-android@lists.freedesktop.org" target="_blank" rel="noreferrer">gstreamer-android@lists.freedesktop.org</a> <a href="https://lists.freedesktop.org/mailman/listinfo/gstreamer-android" rel="noreferrer noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/gstreamer-android</a> </blockquote></div>