Hi,
Disabling the GStreamer debugging system can also help trim off a
decent amount from the packages.
Edward
On Wed, 2014-04-09 at 07:13 -0400, Patrick Doyle wrote:
> Thank you for the tips folks... please keep them coming. At the moment
> (for this pinhole sized project) I only need support for video. Is
> there any way to strip out all of the audio components from the
> gstreamer I generate? I tried adding --disable-vorbis to my recipe,
> only to find that config.status shows that both --disable-vorbis and
> --enable-vorbis options we set in ac_cs_config.
>
> In the mean time, I'm going to go build my own pipeline & link it
> statically as suggested by Sebastian.
>
> Thank you again.
>
> --wpd
>
>
> On Wed, Apr 9, 2014 at 4:53 AM, Burton, Ross <ross.burton@xxxxxxxxx> wrote:
> > On 9 April 2014 00:03, Patrick Doyle <wpdster@xxxxxxxxx> wrote:
> >> I have a ridiculously pinhole sized memory footprint into which I
> >> would like to squeeze a gstreamer based video pipeline. I am looking
> >> for tips on what I can do to minimize the footprint as much as
> >> possible for my Yocto based system.
> >
> > The GStreamer plugins and libraries are all packaged independently in
> > Yocto, so you can do some heavy size reduction by just installing the
> > packages you need, and double-checking that nothing unexpected gets
> > pulled in via dependencies.
> >
> > Ross
> _______________________________________________
> gstreamer-embedded mailing list
> gstreamer-embedded@xxxxxxxxxxxxxxxxxxxxx
> http://lists.freedesktop.org/mailman/listinfo/gstreamer-embedded
--
Edward Hervey <edward@xxxxxxxxxxxxx>
_______________________________________________
gstreamer-embedded mailing list
gstreamer-embedded@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/gstreamer-embedded
