commit | b00dc386d3fe04412f5688266fe5ed5af131a3ee | [log] [tgz] |
---|---|---|
author | Niels Möller <nisse@webrtc.org> | Thu Jun 16 10:44:30 2016 |
committer | Niels Möller <nisse@webrtc.org> | Thu Jun 16 10:44:44 2016 |
tree | 2691f24ac18f763236b7a49f55abdf7af33fff7d | |
parent | 342f74005fc47dc32555907a3eb07718fcb028a5 [diff] |
Delete GetExecutablePath and related unused code. The function GetExecutablePath is a hack with poor portability. Delete it and its caller GetTestFilePath. The latter was used in videoframe_unittest.h, where it is replaced by webrtc::test::ResourcePath. Delete unused functions declared in base/testutils.h: ReadFile, GetSiblingDirectory, GetGoogle3Directory, GetTalkDirectory, CmpHelperFileEq, EXPECT_FILEEQ, ASSERT_FILEEQ. Delete unused functions declared in media/base/testutils.h: GetTestFilePath (see above), LoadPlanarYuvTestImage, DumpPlanarYuvTestImage, ComputePSNR, ComputeSumSquareError. The functions LoadPlanarYuvTestImage, DumpPlanarYuvTestImage were used in yuvscaler_unittests.cc and planarfunctions_unittests.cc, under webrtc/pc. However, these tests are never compiled or run, and appear not to have been for the last few years, and are therefore deleted rather than updated. It might make sense to check if libyuv have comparable tests, and if not, resurrect them as part of libyuv unittests. BUG= R=perkj@webrtc.org Review URL: https://codereview.webrtc.org/2058043002 . Cr-Commit-Position: refs/heads/master@{#13163}
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. This page is maintained by the Google Chrome team.
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.