New targets call:rtp_interfaces, call:rtp_receiver, call:rtp_sender.

webrtc/call/rtp_demuxer.h

Index: webrtc/call/rtp_demuxer.h
diff --git a/webrtc/call/rtp_demuxer.h b/webrtc/call/rtp_demuxer.h
index e1a81603dd21c085f483d016252fe852d431d21e..26dc1ee69f26c695d0c2fe2eb97d143774f031a4 100644
--- a/webrtc/call/rtp_demuxer.h
+++ b/webrtc/call/rtp_demuxer.h
@@ -12,16 +12,9 @@
 
 #include <map>
 
-namespace webrtc {
-
-class RtpPacketReceived;
+#include "webrtc/call/rtp_packet_sink_interface.h"

[the sun, 2017/06/01 07:28:21]

forward decl would suffice

[nisse-webrtc, 2017/06/01 07:48:05]

True. Not entirely clear if it makes sense to use the demuxer without the real
definition. But it seems Call doesn't need it.

So I'm changing to a forward declaration.

 
-// This class represents a receiver of an already parsed RTP packets.
-class RtpPacketSinkInterface {
- public:
-  virtual ~RtpPacketSinkInterface() {}
-  virtual void OnRtpPacket(const RtpPacketReceived& packet) = 0;
-};
+namespace webrtc {
 
 // This class represents the RTP demuxing, for a single RTP session (i.e., one
 // ssrc space, see RFC 7656). It isn't thread aware, leaving responsibility of