uxp - uxp [Local Fork]

	Commit message (Collapse)	Author	Age
*	Issue #1937 - Part 1: Update build system for libaom.	Job Bautista	2022-06-25
\|
*	Move aom source to a sub-directory under media/libaom	Matt A. Tobin	2020-04-07
\| \| \| \|	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 changes	trav90	2018-10-19
\|
*	[aom] No longer necessary to run lint_config.sh anymore	trav90	2018-10-19
\| \| \| \|	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.sh	trav90	2018-10-19
\| \| \| \|	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 option	trav90	2018-10-17
\|
*	Make aom_config.asm match upstream	trav90	2018-10-17
\|
*	[aom] Add x86-win32-gcc config	trav90	2018-10-17
\|
*	[av1] Clean up duplicate filenames check	trav90	2018-10-17
\|
*	Port the libvpx mozbuild generator to aom	trav90	2018-10-15
	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/.