| Commit message (Collapse) | Author | Age | Lines |
|---|
| |
|
|
| |
There is no damned reason to treat this differently than any other media lib given its license and there never was.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
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 aom to commit id d14c5bb4f336ef1842046089849dee4a301fbbf0.
|
| | |
|
| | |
|
| |
|
|
| |
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.
|
| |
|
|
| |
This uses the cmakeparser to generate sources.mozbuild and the config files for each platform.
|
| |
|
|
| |
Unfortunately, upstream has removed the configure+make build system our import script relies on to generate code and moz.build files.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This revision of libaom has some conflicts with our vendor script
and build system. A number of new .asm files have the same basename
as .c files, which our build system cannot handle.
To work around this, I manually renamed the conflicting
files in the filesystem and sources.mozbuild.
Also add av1_convolve_scale_sse4.c to sources.mozbuild manually.
This is needed by the build but for some reason isn't picked up
by generate_sources_mozbuild.sh.
|
| | |
|
| |
|
|
| |
Recent changes made this a public header, so it needs to be available to callers like AOMDecoder.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
aom_dsp_rtcd_defs.pl checks only whether this key is present in the config, not whether it is set to true or not. Our script sets CONFIG_FOO=no for disabled options, while the upstream build system omits them, resulting in extra symbol declarations the build will never define.
Work around this by stripping the offending disabled config key if it is disabled.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|
|
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/.
|
