[FFmpeg-devel] [PATCH] Obey configure updates for OGG, Matroska, and MOV parsers.

[Dale Curtis]

Chrome as a whole has a bunch of infrastructure for monitoring binary size:

http://build.chromium.org/f/chromium/perf/dashboard/sizes.html
http://build.chromium.org/f/chromium/perf/linux-release/sizes/report.html?history=150&rev=-1

http://build.chromium.org/f/chromium/perf/mac-release/sizes/report.html?history=150&rev=-1
http://build.chromium.org/f/chromium/perf/xp-release/sizes/report.html?history=150&rev=-1

In this case though, I just built the binaries on a couple platforms and
checked the shared library / DLL size w/ and w/o the flags.

Thanks for the script!

- dale

On Tue, Apr 10, 2012 at 1:43 PM, Reimar Döffinger
<Reimar.Doeffinger at gmx.de>wrote:

> On Tue, Apr 10, 2012 at 01:25:24PM -0700, Dale Curtis wrote:
> > On Tue, Apr 10, 2012 at 11:46 AM, Reimar Döffinger <
> Reimar.Doeffinger at gmx.de
> > > wrote:
> > After digging through the history on this patch, it looks like this patch
> > was added to reduces the size of the ffmpeg library used by Chrome.
> > Retesting this assumption with the current code base and our configure
> > options shows an ~4kb uncompressed improvement with these patches and
> ~0kb
> > compressed improvement. Which is not worth the trouble.
>
> Do you have some tools to help getting the size down?
> I've so far been using this command (as a script) which sorts symbols by
> size:
> objdump -t "$1" | grep "$2" | awk '{ print $5"   "$6 }' | grep '^0' | sort
> | less
>
>
> I mostly used it to search for large tables that are in .data even
> though the should be const (and thus in .rodata) by calling it like this:
> sortsym.sh ffmpeg_g '\.data'
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>