8e2852d506
So we can report perf results using JSON and not parsing stdout. I reordered the way the arguments are parsed, so that options go at the end, and not at the middle, which is an awkward place to put them. Regular usage specifying [-I], bottleneck_value, infile and outfile shouldn't be affected. Bug: chromium:807737 Change-Id: Ida863846400326c33e443d723f384971b891b6e5 Reviewed-on: https://webrtc-review.googlesource.com/47161 Reviewed-by: Henrik Lundin <henrik.lundin@webrtc.org> Reviewed-by: Oleh Prypin <oprypin@webrtc.org> Commit-Queue: Edward Lemur <ehmaldonado@webrtc.org> Cr-Commit-Position: refs/heads/master@{#21873}
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