Add build targets for Opus tests.
commitbfcc6156a8f2107ecd70445b08e60299737caffa
authorwtc <wtc@chromium.org>
Fri, 30 Jan 2015 19:37:25 +0000 (30 11:37 -0800)
committerCommit bot <commit-bot@chromium.org>
Fri, 30 Jan 2015 19:38:58 +0000 (30 19:38 +0000)
tree1a0e3792b46687d8c148d98f8fe88f3a7a503e1f
parent243315bb066856bcadc20b3118ec623d96187edd
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/890473002

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