> Any idea what that compile time might look like for each of the M4 configurations?
Unfortunately not, but I'd hope to see a reduction to under 10 minutes with the M4 Pro at the very least.
> Also, how often do you have to compile a codebase of that size from scratch and why?
Very often; since Waterfox's changes are always rebased on top of Firefox, every time we pull from upstream, the build system will do a from scratch compile.
A full release build takes about 1 hr (due to monolithic LTO and PGO, which requires 2 builds and about 15 minutes of app runtime to profile).
Unfortunately not, but I'd hope to see a reduction to under 10 minutes with the M4 Pro at the very least.
> Also, how often do you have to compile a codebase of that size from scratch and why?
Very often; since Waterfox's changes are always rebased on top of Firefox, every time we pull from upstream, the build system will do a from scratch compile.
A full release build takes about 1 hr (due to monolithic LTO and PGO, which requires 2 builds and about 15 minutes of app runtime to profile).