Add build targets for Opus tests.
commit8b76b75f78ffdb9760ee7eea4f149c5d2b64bc89
authorwtc <wtc@chromium.org>
Tue, 3 Feb 2015 01:31:37 +0000 (2 17:31 -0800)
committerCommit bot <commit-bot@chromium.org>
Tue, 3 Feb 2015 01:33:14 +0000 (3 01:33 +0000)
tree351839fe042778a08827205ac6b83bb80747fbe8
parentbc3def1a9c250292c314835387a9bfbbf372b6f3
Add build targets for Opus tests.

test_opus_api, test_opus_encode, test_opus_decode, and test_opus_padding
can be run directly, with no command-line options, and they print out
"OK" during the test and an overall status message such as
"All API tests passed." or "Tests completed successfully." at the end.

The celt component has several unit tests. I didn't add build targets
for them because some of them don't print any output, so you'd need a
test harness script to examine their exit status.

R=henrika@chromium.org,sergeyu@chromium.org
BUG=452984

Review URL: https://codereview.chromium.org/894473002

Cr-Commit-Position: refs/heads/master@{#314235}
third_party/opus/BUILD.gn
third_party/opus/opus.gyp