Closed
Bug 836570
Opened 11 years ago
Closed 11 years ago
Mark media/mtransport/build as FAIL_ON_WARNINGS on non-MSVC compilers
Categories
(Core :: WebRTC, defect)
Core
WebRTC
Tracking
()
RESOLVED
FIXED
mozilla21
People
(Reporter: dholbert, Assigned: dholbert)
References
Details
(Whiteboard: [WebRTC] [blocking-webrtc-] [qa-])
Attachments
(1 file)
755 bytes,
patch
|
jesup
:
review+
|
Details | Diff | Splinter Review |
W/ dependent bugs fixed, the source files built by media/mtransport/build/Makefile.in are warning-free[1]. Marking [1] (We've actually still got one MSVC warning that seems to be from a third-party header not properly checking whether a macro is defined. I filed bug 836500 on that one, and I'm excluding MSVC from this bug's FAIL_ON_WARNINGS annotation for now.)
Assignee | ||
Comment 1•11 years ago
|
||
Here's a green try run w/ this being tested on most of our platforms (I skipped a few, e.g. Linux32, to save on resources): https://tbpl.mozilla.org/?tree=Try&rev=1faeab6ced1d
Attachment #708386 -
Flags: review?(rjesup)
Assignee | ||
Comment 2•11 years ago
|
||
(The "#ifndef _MSC_VER" wrapper is the pattern we're using tree-wide for cases where we need to exempt MSVC from FAIL_ON_WARNINGS, per bug 824247 comment 7).
Updated•11 years ago
|
Whiteboard: [WebRTC] [blocking-webrtc-]
Updated•11 years ago
|
Attachment #708386 -
Flags: review?(rjesup) → review+
Assignee | ||
Comment 3•11 years ago
|
||
Green try run, w/ helper-bugs all fixed (all of which have already landed on inbound, except for bug 836196, which is awaiting review): https://tbpl.mozilla.org/?tree=Try&rev=ce8a81a060ec
Assignee | ||
Comment 4•11 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/e4088b236634
Flags: in-testsuite-
Comment 5•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/e4088b236634
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla21
Updated•11 years ago
|
Whiteboard: [WebRTC] [blocking-webrtc-] → [WebRTC] [blocking-webrtc-] [qa-]
You need to log in
before you can comment on or make changes to this bug.
Description
•