<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">2014-06-12 0:40 GMT+02:00 Michael McNamara <span dir="ltr"><<a href="mailto:mmcnamara@control4.com" target="_blank">mmcnamara@control4.com</a>></span>:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif"> <div>Hi Chuck,</div> <div><br> </div> <div>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. </div> <div><br> </div> <div>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.</div></div></blockquote><div><br> </div><div style>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 everything?</div> <div style>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 Android.mk list in Android.</div><div style><br></div><div style>Cheers,</div><div style> Andoni</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif"> <div><br> </div> <div>Cheers.</div> <div><br> </div> <span> <div style="font-family:Calibri;font-size:11pt;text-align:left;color:black;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADDING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:medium none;PADDING-TOP:3pt"> <span style="font-weight:bold">From: </span>Chuck Crisler <<a href="mailto:ccrisler@mutualink.net" target="_blank">ccrisler@mutualink.net</a>><br> <span style="font-weight:bold">Reply-To: </span>Discussion of the development of and with GStreamer <<a href="mailto:gstreamer-devel@lists.freedesktop.org" target="_blank">gstreamer-devel@lists.freedesktop.org</a>><br> <span style="font-weight:bold">Date: </span>Wednesday, June 11, 2014 at 1:43 PM<br> <span style="font-weight:bold">To: </span>Discussion of the development of and with GStreamer <<a href="mailto:gstreamer-devel@lists.freedesktop.org" target="_blank">gstreamer-devel@lists.freedesktop.org</a>><br> <span style="font-weight:bold">Subject: </span>Re: Pared down build via cerbero?<br> </div><div><div class="h5"> <div><br> </div> <div> <div> <div dir="ltr">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.<br> </div> <div class="gmail_extra"><br> <br> <div class="gmail_quote">On Wed, Jun 11, 2014 at 2:47 PM, Michael McNamara <span dir="ltr"> <<a href="mailto:mmcnamara@control4.com" target="_blank">mmcnamara@control4.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif"> <div>All,</div> <div><br> </div> <div>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?</div> <div><br> </div> <div>Cheers and thank you!</div> <div><br> </div> <div><br> </div> </div> <br> _______________________________________________<br> gstreamer-devel mailing list<br> <a href="mailto:gstreamer-devel@lists.freedesktop.org" target="_blank">gstreamer-devel@lists.freedesktop.org</a><br> <a href="http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel" target="_blank">http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a><br> <br> </blockquote> </div> <br> </div> </div> </div> </div></div></span> </div> <br>_______________________________________________<br> gstreamer-devel mailing list<br> <a href="mailto:gstreamer-devel@lists.freedesktop.org">gstreamer-devel@lists.freedesktop.org</a><br> <a href="http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel" target="_blank">http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a><br> <br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Andoni Morales Alastruey<br><br>LongoMatch:The Digital Coach<br><a href="http://www.longomatch.ylatuya.es">http://www.longomatch.ylatuya.es</a> </div></div>