Bug 1073003, which enables warnings-as-errors on B2G,
landed today.
What this gives us:
- In B2G-only code, the compiler now enforces that we
keep the code warning-free. This is useful because
warnings can often point out legitimate problems in
the code.
- In cross-platform code, this was already enforced,
but if you worked with a B2G local build, you wouldn't
catch the warnings until you pushed to TBPL. Now,
the warnings will be caught in your local build.
What to do if a change you're trying to make introduces
a warning being treated as an error, and you're not sure
how to fix it:
- Look at the compiler documentation for the warning.
GCC warnings are documented here [1]. This is often
enough to figure out how to fix the warning.
- Look at how I've fixed warnings in bug 1073081 and
bug 1073003. I've fixed over 15 types of warnings
in those bugs; it's likely that one of the
techniques I used to fix them applies to your
situation.
- Feel free to ping me on IRC and ask!
Cheers,
Botond
[1] https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html
_______________________________________________
dev-platform mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-platform
