My expectation would be that ProGuard would eliminate enough code to
fix this, but perhaps it’s not aggressively pruning library code.
I would like to know how much ProGuard strips out. Do we have that
somewhere? Does ProGuard make that easily available?
I haven't measured this, but I'd like to see it during the build. It
might be a little tricky because we run multiple iterations of PG, but
presumably this is solved. File it!
Nick
_______________________________________________
mobile-firefox-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/mobile-firefox-dev
