commit | 6714bf9f18f2514919f7b0cdc305107076cdc65b | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@webrtc.org> | Wed Oct 17 14:23:31 2018 -0500 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Oct 18 14:41:12 2018 +0000 |
tree | 092130ab30deafdd546e15bc85fc63212008d970 | |
parent | 50b1e6b760b267b646ee7a15db20671d82e0d9a9 [diff] |
Fix up OpenSSL/BoringSSL forward declarations. There is no need to redefine SSL_CTX. base.h/ossl_typ.h defines it already. Additionally, switch the base.h includes to the OpenSSL-compatible ossl_typ.h spelling. That just got landed in https://webrtc-review.googlesource.com/c/104120, so I'm guessing OpenSSL consumers just didn't notice yet. While getting the current BoringSSL name mangling scheme working with WebRTC is a ways off, one of the requirements will almost certainly be that WebRTC never forward-declare any BoringSSL types itself, instead leaving it to openssl/base.h (or openssl/ossl_typ.h, the OpenSSL-compatible alias). This is because we'd need to rename the struct names themselves where they participate in C++ name mangling. E.g. std::pair<RSA*, int> would mangle as rsa_st. Bug: webrtc:5664 Change-Id: Ib9695d4ae4bc07d2bc54c9fdfb8600f44b5ec7bb Reviewed-on: https://webrtc-review.googlesource.com/c/106675 Commit-Queue: David Benjamin <davidben@webrtc.org> Reviewed-by: Karl Wiberg <kwiberg@webrtc.org> Reviewed-by: Per Kjellander <perkj@webrtc.org> Cr-Commit-Position: refs/heads/master@{#25257}
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.