Google Git
Sign in
fuchsia / third_party / ffmpeg / 8f7bd6044a34932072ce9c7bee7933601f8cd050
commit8f7bd6044a34932072ce9c7bee7933601f8cd050[log] [tgz]
authorDale Sather <dalesat@chromium.org>Fri Aug 26 14:21:22 2016 -0700
committerDale Sather <dalesat@chromium.org>Mon Sep 12 13:31:53 2016 -0700
tree5f4822a6ceab09ec2b2d1c5ba250159d78072f08
parent75976ae026fdbedb14f006eec6cd9119c543aa7f [diff]
third_party/ffmpeg: fix fuchsia build

This CL makes some changes to the Chromium gn build files and
associated infrastructure to enable gn builds under fuchsia.
ffmpeg_generated.gni, a generated file, has been altered to
treat fuchsia like linux for the time being. The script that
generates it has been altered to produce the same result as
the altered gni file (but the script was not run). These
changes shouldn't break Chromium if pushed upstream, but
there's currently no plans to do that.

Most of the other changes are about getting the build to work
properly without having to replicate the build/config files
that chromium uses.

New files in chromium/config/Chromium/fuchsia are unaltered
copies of files in chromium/config/Chromium/linux.

Change-Id: I317b2d51105d826e8bb2d59d614020e39cd9d808
11 files changed
tree: 5f4822a6ceab09ec2b2d1c5ba250159d78072f08
  1. chromium/
  2. compat/
  3. doc/
  4. libavcodec/
  5. libavdevice/
  6. libavfilter/
  7. libavformat/
  8. libavresample/
  9. libavutil/
  10. libpostproc/
  11. libswresample/
  12. libswscale/
  13. presets/
  14. tests/
  15. tools/
  16. .gitattributes
  17. .gitignore
  18. .travis.yml
  19. arch.mak
  20. BUILD.gn
  21. Changelog
  22. cmdutils.c
  23. cmdutils.h
  24. cmdutils_common_opts.h
  25. cmdutils_opencl.c
  26. codereview.settings
  27. common.mak
  28. configure
  29. COPYING.GPLv2
  30. COPYING.GPLv3
  31. COPYING.LGPLv2.1
  32. COPYING.LGPLv3
  33. CREDITS
  34. CREDITS.chromium
  35. ffmpeg.c
  36. ffmpeg.gyp
  37. ffmpeg.h
  38. ffmpeg_dxva2.c
  39. ffmpeg_filter.c
  40. ffmpeg_generated.gni
  41. ffmpeg_generated.gypi
  42. ffmpeg_opt.c
  43. ffmpeg_options.gni
  44. ffmpeg_qsv.c
  45. ffmpeg_vdpau.c
  46. ffmpeg_videotoolbox.c
  47. ffmpegsumo.ver
  48. ffplay.c
  49. ffprobe.c
  50. ffserver.c
  51. ffserver_config.c
  52. ffserver_config.h
  53. INSTALL.md
  54. library.mak
  55. LICENSE.md
  56. MAINTAINERS
  57. Makefile
  58. OWNERS
  59. PRESUBMIT.py
  60. README.chromium
  61. README.md
  62. RELEASE
  63. version.sh
  64. xcode_hack.c
README.md

FFmpeg README

FFmpeg is a collection of libraries and tools to process multimedia content such as audio, video, subtitles and related metadata.

Libraries

  • libavcodec provides implementation of a wider range of codecs.
  • libavformat implements streaming protocols, container formats and basic I/O access.
  • libavutil includes hashers, decompressors and miscellaneous utility functions.
  • libavfilter provides a mean to alter decoded Audio and Video through chain of filters.
  • libavdevice provides an abstraction to access capture and playback devices.
  • libswresample implements audio mixing and resampling routines.
  • libswscale implements color conversion and scaling routines.

Tools

  • ffmpeg is a command line toolbox to manipulate, convert and stream multimedia content.
  • ffplay is a minimalistic multimedia player.
  • ffprobe is a simple analysis tool to inspect multimedia content.
  • ffserver is a multimedia streaming server for live broadcasts.
  • Additional small tools such as aviocat, ismindex and qt-faststart.

Documentation

The offline documentation is available in the doc/ directory.

The online documentation is available in the main website and in the wiki.

Examples

Coding examples are available in the doc/examples directory.

License

FFmpeg codebase is mainly LGPL-licensed with optional components licensed under GPL. Please refer to the LICENSE file for detailed information.

Contributing

Patches should be submitted to the ffmpeg-devel mailing list using git format-patch or git send-email. Github pull requests should be avoided because they are not part of our review process. Few developers follow pull requests so they will likely be ignored.