Re: Landing c-c-breaking changes that remove c-c-only code from m-c

2014-04-24 Thread Henri Sivonen
On Thu, Apr 17, 2014 at 10:09 AM, Henri Sivonen hsivo...@hsivonen.fi wrote: I am not done preparing the removal patches yet, but with my current patch queue I can already get 149 KB off of Android ARMv7 optimized apk size and 138 KB off of Android ARMv7 optimized libxul size. And the numbers

Re: Landing c-c-breaking changes that remove c-c-only code from m-c

2014-04-24 Thread Nicholas Nethercote
On Thu, Apr 24, 2014 at 9:38 PM, Henri Sivonen hsivo...@hsivonen.fi wrote: And the numbers are in with the complete set of removals: apk size reduction: 193 KB libxul size reduction: 181 KB This is good stuff! Thanks. Nick ___ dev-platform mailing

Re: Landing c-c-breaking changes that remove c-c-only code from m-c

2014-04-22 Thread ISHIKAWA,chiaki
(2014/04/22 2:09), Joshua Cranmer  wrote: On 4/21/2014 11:50 AM, Ehsan Akhgari wrote: You can check CONFIG['MOZ_BUILD_APP'] against what you pass to --enable-application in mozconfig files. So that would be 'mailnews' (or 'mail'?) and 'suite' for Thunderbird and Seamonkey respectively.

Re: Landing c-c-breaking changes that remove c-c-only code from m-c

2014-04-22 Thread Joshua Cranmer 
On 4/22/2014 2:12 AM, Henri Sivonen wrote: There is no strong need for the m-c removals to be tied to the ESR schedule. However, I think it would be preferable to make the changes before the ESR deadline so that future c-c patches backport easily to the ESR (if there are security holes in the

Re: Landing c-c-breaking changes that remove c-c-only code from m-c

2014-04-21 Thread Joshua Cranmer 
On 4/21/2014 11:50 AM, Ehsan Akhgari wrote: You can check CONFIG['MOZ_BUILD_APP'] against what you pass to --enable-application in mozconfig files. So that would be 'mailnews' (or 'mail'?) and 'suite' for Thunderbird and Seamonkey respectively. Actually, CONFIG['MOZ_THUNDERBIRD'] and