----- Original Message ----- > FWIW, I've often made changes like this when touching files like > nsCOMPtr.h or nsINode.h -- or switching nsresult from a typedef to an > enum class! -- and I find just doing ./mach build binaries works fine. > It reports errors randomly from all over the tree, but that works fine > for me. What's the advantage of doing it directory-by-directory?
I've had some cases where a file that is included everywhere will break in some particular file, but be fine in most places, so you end up rebuilding a bunch of stuff you know is going to work everytime you adjust it. I don't recall offhand why that was. Maybe a template that broke in certain instantiations? Andrew _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
