summaryrefslogtreecommitdiffstats
path: root/media/libaom/generate_sources_mozbuild.sh
Commit message (Collapse)AuthorAgeLines
* Move aom source to a sub-directory under media/libaomMatt A. Tobin2020-04-07-1/+1
| | | | There is no damned reason to treat this differently than any other media lib given its license and there never was.
* Update libaom vendor scripts to account for upstream changestrav902018-10-19-4/+4
|
* [aom] No longer necessary to run lint_config.sh anymoretrav902018-10-19-31/+4
| | | | Upstream can now code generate the rtcd interface files directly from the aom_config.h header, so we no longer have to generate an intermediate file by running lint_config.sh. This also means we can remove the code for creating a temporary directory.
* Update generate_sources_mozbuild.shtrav902018-10-19-177/+13
| | | | This changes generate_sources_mozbuild.sh to call generate_sources_mozbuild.py to generate sources.mozbuild and config files and removes the parts of the script that are no longer necessary.
* [aom] Remove unused optiontrav902018-10-17-3/+3
|
* Make aom_config.asm match upstreamtrav902018-10-17-2/+2
|
* [aom] Add x86-win32-gcc configtrav902018-10-17-0/+2
|
* [av1] Clean up duplicate filenames checktrav902018-10-17-8/+7
|
* Port the libvpx mozbuild generator to aomtrav902018-10-15-0/+270
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. The upstream source is located 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/.