cf85e24661
This test was added in https://webrtc-codereview.appspot.com/15789004/, which looks like it was early on in adding support for capture and encode with native textures on Android. Since then, the VideoFrame/VideoFrameBuffer interfaces have emerged and texture support has changed a lot (now using VideoFrameBuffer with type kNative). The test only exercises the parts of the video pipeline before VideoStreamEncoder::pre_encode_callback_, which doesn't care at all about the type of the corresponding VideoFrameBuffer. That's not so useful, and since it blocks removal of pre_encode_callback, let's delete this old test. Bug: webrtc:9864, chromium:362437 Change-Id: I2eb6c4c48557883309fd6431bc25528441c83078 Reviewed-on: https://webrtc-review.googlesource.com/c/115411 Reviewed-by: Erik Språng <sprang@webrtc.org> Commit-Queue: Niels Moller <nisse@webrtc.org> Cr-Commit-Position: refs/heads/master@{#26086}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
Development
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://webrtc.googlesource.com/src
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: http://build.chromium.org/p/client.webrtc
- Coding style guide
- Code of conduct