[tracking] Stop doing wasteful stuff in a top-level `mach build`

NEW
Unassigned

Status

()

Core
Build Config
2 years ago
a year ago

People

(Reporter: ted, Unassigned)

Tracking

(Depends on: 4 bugs)

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
`mach build binaries` and `mach build faster` are great, but it'd be nice if `mach build` was fast enough that we didn't have to resort to hacks. It will probably take a fair bit of effort to make it as fast as either of those, because we'd have to stop doing recursive traversal, but we could at least get rid of the waste.

Here's what a no-op `mach build` looks like on my Linux machine with the patches from bug 1295937 applied:
https://gist.github.com/6e51e7b622273de16c1bcd36057a663b

We burn a few seconds re-compiling nsBrowserApp.cpp and re-linking firefox due to bug 1297373. We spend a *lot* of time processing jar manifests (bug 1297381). We spent a few seconds needlessly rebuilding XPI files (bug 1240676). bug 1295937 removes another offender, recursing through NSS' export tier.
Depends on: 1319348
You need to log in before you can comment on or make changes to this bug.