8434aeb3a7
This code is much more sophisticated in that it doesn't rely on argv[0], but rather asks the OS where our executable is. We can then simply go two steps up since we count on running in out/Whatever relative to the src dir. This is how Chromium does it. The aim here is to get rid of SetExecutablePath, which will be the next CL. Bug: webrtc:9792 Change-Id: I7da027b7391e759b1f612de12f27a244fe884c09 Reviewed-on: https://webrtc-review.googlesource.com/c/103121 Reviewed-by: Artem Titov <titovartem@webrtc.org> Commit-Queue: Patrik Höglund <phoglund@webrtc.org> Cr-Commit-Position: refs/heads/master@{#25017}
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