GStreamer registry cache

[Sebastian Dröge]

On Mi, 2015-03-25 at 11:43 +0100, Arnaud Vrac wrote:
> On Tue, Mar 24, 2015 at 1:33 PM, Nicolas Dufresne <
> nicolas.dufresne at collabora.com> wrote:
> 
> > Le mardi 24 mars 2015 à 09:47 +0100, Víctor M. Jáquez L. a écrit :
> > > I guess that simply running a gst-inspect-1.0 "at factory" and always
> > > setting
> > > the GST_REGISTRY_UPDATE system-wide, would be the answer.
> >
> > Not fully sufficient, but close. A "no patch solution" is to indeed
> > generate a cache file in post install scripts. Any application that
> > calls gst_init() will do, gst-inspect-1.0 is a way of course. So
> > something like:
> >
> > # Global env
> > GST_REGISTRY=/usr/share/gstreamer-1.0/registry.$(uname -m).bin
> > GST_REGISTRY_UPDATE=no
> >
> > # In post install scripts (env must be set)
> > gst_inspect-1.0 > /dev/null
> 
> 
> Is it possible to do this when cross-compiling ? If I build the same
> package for the host and target, can I run host gst-inspect-1.0 on the
> target plugins, and will the registry file be compatible ?

No, the registry format is platform dependent. And also contains
absolute paths to plugins, in case they differ between host and target
for you.

-- 
Sebastian Dröge, Centricular Ltd · http://www.centricular.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: This is a digitally signed message part
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20150325/e995f798/attachment.sig>