On 25/8/2014, 14:16, Aryeh Gregor wrote:
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?
It may be that you know the changes to the .h file will compile just fine, and you really just want to compile the specific .cpp files which you suspect will have compile errors. In that case ./mach build binaries will take a long time to get to the errors.
kats _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
