tree: 3037c6f90382b704ad712aec6feea8fd4fc338d3 [path history] [tgz]
  1. aom.cmd
  2. avm.cmd
  3. compliance_warden.sh
  4. dav1d.cmd
  5. dav1d_android.sh
  6. fuzztest.cmd
  7. googletest.cmd
  8. libargparse.cmd
  9. libgav1.cmd
  10. libgav1_android.sh
  11. libjpeg.cmd
  12. libsharpyuv.cmd
  13. libxml2.cmd
  14. libyuv.cmd
  15. libyuv_android.sh
  16. mp4box.sh
  17. rav1e.cmd
  18. README.md
  19. svt.cmd
  20. svt.sh
  21. zlibpng.cmd
ext/README.md

libavif ext dir

This contains references to various external repositories which are known to build and work properly with the current libavif. If you are building for Windows or any kind of fully static (embedded) release, using these scripts in conjunction with the BUILD_SHARED_LIBS=0 and AVIF_* CMake flags make for a convenient way to get all of the dependencies necessary. This method is how many of libavif's continuous builders work.

However, if you are building this for a distribution or Unix-like environment in general, you can safely ignore this directory. Allow BUILD_SHARED_LIBS to keep its default (ON), enable the appropriate AVIF_BUILD_* CMake flags depending on which shared AV1 codec libraries you plan to leverage and depend on, and use the system's zlib, libpng, and libjpeg.