[Bug 756082] qmlglsink: add a QML extension plugin

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=756082

--- Comment #6 from Holger Kaelberer <hk at getslash.de> ---
> This probably isn't going to work very well on android and iOS which require
> static plugins.  I'm not sure what the process is there for extension
> plugins.

Do gstreamer builds for android require that?

For a 'normal' Qt application targeting Android platform and using 3rd party
qml plugins imho the process is

1) Build the plugin with the Qt build-tools for the android_armv7 platform.
2) Package the plugin as ANDROID_EXTRA_PLUGIN (qmake wording)
3) Buildit

Looking at how we package e.g. the qml-box2d plugin in GCompris-qt for android
(https://quickgit.kde.org/?p=gcompris.git&a=blob&h=731d968737e7f7ba15cf988be1b29caf46dd01c8&hb=826d26b0c89070a47065790b887de4c44b9cbd03&f=CMakeLists.txt#l321)
I find linker flags like the following generated for building this 3rd party
module:

LFLAGS        = --sysroot=/opt/android-ndk//platforms/android-9/arch-arm/
-Wl,-rpath=/mnt/ltmp/Qt5.5.1-android/5.5/android_armv7/lib -Wl,--no-undefined
-Wl,-z,noexecstack -shared

Therefore from a Qt PoV I don't think it's necessary to link the *qml* plugin
statically on Android. And the gstreamer-part only needs to cope with the *gst*
plugin, no?

I have no idea of iOS, though.

If we'd really to link the plugin statically, afaik the registering of the qml
type probably needs to be done manually on app-layer (that's what I see other
plugins doing then).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.