mozilla
/
gecko-dev
зеркало из https://github.com/mozilla/gecko-dev.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
gecko-dev/media/libaom/README_MOZILLA

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

20 строки
644 B
Plaintext
Исходник Обычный вид История

Bug 1314147 - Port the libvpx mozbuild generator to aom. r=froydnj,kinetik This is a port of the libvpx scripts, themselves a port of Chromium's scripts to generate an external build description using hooks in the upstream configure and make scripts. The libaom library is a fork of libvpx so we can use a similar approach. I've put the upstream source in $(topsrc_dir)/third_party/aom but the build description and any patches are under the media directory with the other codecs, similar to how zlib works. Config files and headers generated by the upstream build system are also under $(topsrc_dir)/media/libaom/. MozReview-Commit-ID: ATLgOTPD2i1 --HG-- extra : rebase_source : c0fdcdb41a5bac5fdf64f773458cb62937fc9dd8
2017-04-13 03:01:43 +03:00
This directory contains build files for the aom video
codec reference implementation. The actual library
source is in $TOPSRCDIR/third_party/aom/
Any patches or additional configuration to be applied to the
upstream source should be kept here in the media/libaom
directory.
To update the library source and build config files, execute
Bug 1637845 - Add a moz.yaml for libaom and remove version information from the README r=glob Differential Revision: https://phabricator.services.mozilla.com/D76432
2020-06-10 17:47:57 +03:00
./mach vendor media/libaom/moz.yaml
Bug 1314147 - Port the libvpx mozbuild generator to aom. r=froydnj,kinetik This is a port of the libvpx scripts, themselves a port of Chromium's scripts to generate an external build description using hooks in the upstream configure and make scripts. The libaom library is a fork of libvpx so we can use a similar approach. I've put the upstream source in $(topsrc_dir)/third_party/aom but the build description and any patches are under the media directory with the other codecs, similar to how zlib works. Config files and headers generated by the upstream build system are also under $(topsrc_dir)/media/libaom/. MozReview-Commit-ID: ATLgOTPD2i1 --HG-- extra : rebase_source : c0fdcdb41a5bac5fdf64f773458cb62937fc9dd8
2017-04-13 03:01:43 +03:00
To update to a specific upstream git tag or commit, use
Bug 1637845 - Add a moz.yaml for libaom and remove version information from the README r=glob Differential Revision: https://phabricator.services.mozilla.com/D76432
2020-06-10 17:47:57 +03:00
./mach vendor media/libaom/moz.yaml -r <commit>
Bug 1314147 - Port the libvpx mozbuild generator to aom. r=froydnj,kinetik This is a port of the libvpx scripts, themselves a port of Chromium's scripts to generate an external build description using hooks in the upstream configure and make scripts. The libaom library is a fork of libvpx so we can use a similar approach. I've put the upstream source in $(topsrc_dir)/third_party/aom but the build description and any patches are under the media directory with the other codecs, similar to how zlib works. Config files and headers generated by the upstream build system are also under $(topsrc_dir)/media/libaom/. MozReview-Commit-ID: ATLgOTPD2i1 --HG-- extra : rebase_source : c0fdcdb41a5bac5fdf64f773458cb62937fc9dd8
2017-04-13 03:01:43 +03:00
Bug 1380118 - aom: Record the upstream repo we vendored from. r=froydnj We've been recording the commit id from the last vendor in README_MOZILLA inside the various media directories. Since we now support a --repo switch to pull from forks, record this info as well, to make it easier to find contiguous upstream source. MozReview-Commit-ID: 1RanpkWfAeC --HG-- extra : rebase_source : b6bd16b56626a871802822385be6f3a24db6cd50
2017-08-15 00:33:55 +03:00
The upstream git repository is https://aomedia.googlesource.com/aom
Bug 1314147 - Port the libvpx mozbuild generator to aom. r=froydnj,kinetik This is a port of the libvpx scripts, themselves a port of Chromium's scripts to generate an external build description using hooks in the upstream configure and make scripts. The libaom library is a fork of libvpx so we can use a similar approach. I've put the upstream source in $(topsrc_dir)/third_party/aom but the build description and any patches are under the media directory with the other codecs, similar to how zlib works. Config files and headers generated by the upstream build system are also under $(topsrc_dir)/media/libaom/. MozReview-Commit-ID: ATLgOTPD2i1 --HG-- extra : rebase_source : c0fdcdb41a5bac5fdf64f773458cb62937fc9dd8
2017-04-13 03:01:43 +03:00
Bug 1637845 - Add a moz.yaml for libaom and remove version information from the README r=glob Differential Revision: https://phabricator.services.mozilla.com/D76432
2020-06-10 17:47:57 +03:00
To view the information about the current version, check the
'origin' section of moz.yaml.