Pared down build via cerbero?

Andoni Morales ylatuya at
Thu Jun 26 02:06:11 PDT 2014

2014-06-12 0:40 GMT+02:00 Michael McNamara <mmcnamara at>:

>  Hi Chuck,
>  Thanks for the reply.  I’ve successfully cut down the number of plugins
> in use inside our apps via #define statements in iOS and Android while
> maintaining the functionality that’s needed.  (I agree that it is tricky to
> get the right combination sometimes!)  Presumably those plugins that aren’t
> #defined aren’t making it into the final app binary.  The overall binary
> size in fact grows or shrinks based on those #defines,  so I feel pretty
> good about what’s going on there.
>  My question is more about keeping the unneeded plugins from ever being
> built via cerbero as they’re not needed — or if it’s even reasonably
> possible to do something along those lines.

You could change the configure options in the recipe to remove plugins you
don't want as well as removing them from the files listings and packages,
but the amount of work needed is much bigger than the results you can get.
With all that work you can reduce the build by maybe 10 minutes, from 2
hours to 1h50... but how many times do you really need to rebuild
I think you are already doing it the correct way, which is using only a
subset of all plugins via defines in iOS and the list in Android.


>  Cheers.
>   From: Chuck Crisler <ccrisler at>
> Reply-To: Discussion of the development of and with GStreamer <
> gstreamer-devel at>
> Date: Wednesday, June 11, 2014 at 1:43 PM
> To: Discussion of the development of and with GStreamer <
> gstreamer-devel at>
> Subject: Re: Pared down build via cerbero?
>   I don't know anything about using cerbero, but on linux you can remove
> features with configure. You just have to be careful that you don't remove
> something that you really do need. Sometimes it isn't immediately obvious.
> On Wed, Jun 11, 2014 at 2:47 PM, Michael McNamara <mmcnamara at>
> wrote:
>>  All,
>>  Here’s a build question…  If you know that you’re only in need of a
>> small subset of plugins, is there a relatively simple way to only include
>> those plugins that are needed in the build process?  What would the best
>> approach to take in such a scenario?  How fragile will things get if I
>> start removing libs from the get-plugins-good recipe for example?  Or is
>> that the wrong direction to head?
>>  Cheers and thank you!
>> _______________________________________________
>> gstreamer-devel mailing list
>> gstreamer-devel at
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at

Andoni Morales Alastruey

LongoMatch:The Digital Coach
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the gstreamer-devel mailing list