| commit | 7284e8a650dc33304c1548a5b5f4b56d32cc1d1c | [log] [tgz] |
|---|---|---|
| author | Mirko Bonadei <mbonadei@webrtc.org> | Thu Dec 14 15:05:18 2017 +0000 |
| committer | Commit Bot <commit-bot@chromium.org> | Thu Dec 14 16:00:43 2017 +0000 |
| tree | f3a0c7e1d7ab8b116364e10811a150c5a79edfb4 | |
| parent | 1610f94ee35f788de9317a7c434448930eb121ed [diff] |
Revert "Use std::fstream instead of rtc::File to write perf results + rename flag." This reverts commit f711428898cb2f03d4d09738ba751cf0d316c631. Reason for revert: Breaks downstream projects. Original change's description: > Use std::fstream instead of rtc::File to write perf results + rename flag. > > Use std::fstream instead of rtc::File to write perf results. > On Android, when I use rtc::File, the results are not written for some reason. > > Also rename the flag to '--chartjson_result_file'. > > Bug: webrtc:8566 > Change-Id: I32215e2233e18690c41050dfd35ac77e01d11f35 > Reviewed-on: https://webrtc-review.googlesource.com/32001 > Reviewed-by: Patrik Höglund <phoglund@webrtc.org> > Commit-Queue: Edward Lemur <ehmaldonado@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#21225} TBR=phoglund@webrtc.org,ehmaldonado@webrtc.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: webrtc:8566 Change-Id: I55611592c3171152cee97e64bff35a0d62cea510 Reviewed-on: https://webrtc-review.googlesource.com/33080 Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> Commit-Queue: Mirko Bonadei <mbonadei@webrtc.org> Cr-Commit-Position: refs/heads/master@{#21283}
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.
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.