Move VideoFrame and related declarations to webrtc/api/video.

webrtc/sdk/objc/Framework/Classes/avfoundationvideocapturer.mm

Index: webrtc/sdk/objc/Framework/Classes/avfoundationvideocapturer.mm
diff --git a/webrtc/sdk/objc/Framework/Classes/avfoundationvideocapturer.mm b/webrtc/sdk/objc/Framework/Classes/avfoundationvideocapturer.mm
index 49b56817277fdc86a015fe8cc888220c4657c2c8..8169c673bb496bebeb149d201a51756c3bfd7746 100644
--- a/webrtc/sdk/objc/Framework/Classes/avfoundationvideocapturer.mm
+++ b/webrtc/sdk/objc/Framework/Classes/avfoundationvideocapturer.mm
@@ -24,12 +24,12 @@
 
 #include "libyuv/rotate.h"
 
+#include "webrtc/api/video/rotation.h"
 #include "webrtc/base/bind.h"
 #include "webrtc/base/checks.h"
 #include "webrtc/base/logging.h"
 #include "webrtc/base/thread.h"
 #include "webrtc/common_video/include/corevideo_frame_buffer.h"

[the sun, 2016/11/24 10:36:59]

Should corevideo_frame_buffer move here? The "sdk/"s should serve as tests for
the C++ API - that it provides the necessary "pins" on the chip - so no poking
around with internals should be required/allowed.

[nisse-webrtc, 2016/11/25 08:58:03]

I agree that makes some sense. But it's for someone more familiar with the objc
sdk to decide. (And doesn't have to be in this cl).

-#include "webrtc/common_video/rotation.h"
 
 // TODO(denicija): add support for higher frame rates.
 // See http://crbug/webrtc/6355 for more info.