commit | e90879097c7151148aaad57393967cf72d233a69 | [log] [tgz] |
---|---|---|
author | Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com> | Fri Jul 06 09:29:32 2018 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Jul 06 11:03:41 2018 |
tree | 2a7a2f29ba4ce857564a1d672401d02d0f857d6b | |
parent | b2daaaacbd1f9bf016e0f169006ccf2ab0ad2270 [diff] |
IWYU: Add <cmath> for fabsf() and powf(), switch to C++ versions Fix the build with libstdc++ after 496cedfe5 ("AEC3: Reverberation model: Changes on the decay estimation") by including the missing header: ../../modules/audio_processing/aec3/reverb_model_estimator.cc: In constructor ‘webrtc::ReverbModelEstimator::ReverbModelEstimator(const webrtc::EchoCanceller3Config&)’: ../../modules/audio_processing/aec3/reverb_model_estimator.cc:61:21: error: ‘fabsf’ was not declared in this scope reverb_decay_(fabsf(config.ep_strength.default_len)), ^~~~~ ../../modules/audio_processing/aec3/reverb_model_estimator.cc:61:21: note: suggested alternative: ‘labs’ reverb_decay_(fabsf(config.ep_strength.default_len)), ^~~~~ labs ../../modules/audio_processing/aec3/reverb_model_estimator.cc: In member function ‘void webrtc::ReverbModelEstimator::UpdateReverbDecay(const std::vector<float>&)’: ../../modules/audio_processing/aec3/reverb_model_estimator.cc:206:15: error: ‘powf’ was not declared in this scope decay = powf(2.0f, -exp_candidate * kFftLengthBy2); ^~~~ While here, also switch to the C++ versions of those functions: std::fabs() and std::pow() respectively. Spotted by Jose Dapena Paz <jose.dapena@lge.com>. Bug: chromium:819294 Change-Id: Id803243be8dd17eac95c70a88a37ee2fe1505a5a Reviewed-on: https://webrtc-review.googlesource.com/87421 Reviewed-by: Jesus de Vicente Pena <devicentepena@webrtc.org> Reviewed-by: Gustaf Ullberg <gustaf@webrtc.org> Commit-Queue: Gustaf Ullberg <gustaf@webrtc.org> Cr-Commit-Position: refs/heads/master@{#23870}
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.