Split a separate codecs target off of :video_jni

This will allow clients to include only the software codecs they need
rather than being forced to bundle them all.

- libjingle_peerconnection_jni keeps its allow_poison for now, until
  dependent targets bundle their own codecs explicitly.
- native_api_codecs and native_api_video lose their allow_poison
  because dependent targets are already bundling codecs explicitly.
- libjingle_peerconnection_metrics_default_jni and
  native_api_peerconnection lose their allow_poison because they
  were not actually poisoned.

legacy_hwcodecs_jni and default_video_codec_factory_jni exist for
clients that want to continue bundling the same codecs they get by
default today.

Bug: webrtc:7925
Change-Id: Idf853a6bc77f43decd35ad2a0f467937fec8f8b5
Reviewed-on: https://webrtc-review.googlesource.com/c/108221
Reviewed-by: Sami Kalliomäki <sakal@webrtc.org>
Commit-Queue: Jonathan Yu <yujo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#25564}
1 file changed
tree: 4fb2260e86d995181aeb9feabc6f912d71841663
  1. api/
  2. audio/
  3. build_overrides/
  4. call/
  5. common_audio/
  6. common_video/
  7. data/
  8. examples/
  9. infra/
  10. logging/
  11. media/
  12. modules/
  13. p2p/
  14. pc/
  15. resources/
  16. rtc_base/
  17. rtc_tools/
  18. sdk/
  19. stats/
  20. style-guide/
  21. system_wrappers/
  22. test/
  23. tools_webrtc/
  24. video/
  25. .clang-format
  26. .git-blame-ignore-revs
  27. .gitignore
  28. .gn
  29. .vpython
  30. abseil-in-webrtc.md
  31. AUTHORS
  32. BUILD.gn
  33. CODE_OF_CONDUCT.md
  34. codereview.settings
  35. common_types.h
  36. DEPS
  37. ENG_REVIEW_OWNERS
  38. LICENSE
  39. license_template.txt
  40. native-api.md
  41. OWNERS
  42. PATENTS
  43. PRESUBMIT.py
  44. presubmit_test.py
  45. presubmit_test_mocks.py
  46. pylintrc
  47. README.chromium
  48. README.md
  49. style-guide.md
  50. WATCHLISTS
  51. webrtc.gni
  52. whitespace.txt
README.md

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.

Development

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.

More info