We track total binary size here: http://build.chromium.org/buildbot/perf/dashboard/sizes.html
I don't know of any place we track per-module sizes. On Fri, Nov 13, 2009 at 2:33 PM, Eric Seidel <esei...@chromium.org> wrote: > Do we have any hard data about where our binary size goes? It seems > such data would be very useful. > > On Fri, Nov 13, 2009 at 2:14 PM, Evan Martin <e...@chromium.org> wrote: >> I measured that SVG is nearly a sixth of the binary size of a Chrome >> debug build. That's not only more compile time, it's also more link >> time for each incremental link and more time for the debugger to grind >> it when starting gdb. For my day-to-day debugging I would like to >> build without SVG (and many other bits, but let's start with SVG). >> >> I put on one obvious patch and one patch I'm not sure about at >> https://bugs.webkit.org/show_bug.cgi?id=31490 >> >> Does anyone have thoughts about the right way to disable SVG in the GYP >> files? >> Here's the hacky second patch mentioned above: >> https://bug-31490-attachments.webkit.org/attachment.cgi?id=43196 >> In particular, I'm not sure of the right way to conditionally build >> the SVGNames bits. >> >> I've seen in some cases files are completely wrapped with "#if >> ENABLE(FOO)"; do you know when that is appropriate? >> >> -- >> Chromium Developers mailing list: chromium-dev@googlegroups.com >> View archives, change email options, or unsubscribe: >> http://groups.google.com/group/chromium-dev >> > -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
