{"id":20667050,"url":"https://github.com/lu-zero/libvpx","last_synced_at":"2025-08-03T13:17:05.172Z","repository":{"id":80218909,"uuid":"71257091","full_name":"lu-zero/libvpx","owner":"lu-zero","description":"Local libvpx changes (POWER8 Altivec/VSX support)","archived":false,"fork":false,"pushed_at":"2018-07-08T14:04:27.000Z","size":40627,"stargazers_count":5,"open_issues_count":8,"forks_count":3,"subscribers_count":8,"default_branch":"master","last_synced_at":"2025-06-07T14:44:58.610Z","etag":null,"topics":["altivec","libvpx","powerpc","vsx"],"latest_commit_sha":null,"homepage":"","language":"C","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"bsd-3-clause","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/lu-zero.png","metadata":{"files":{"readme":"README","changelog":"CHANGELOG","contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":"AUTHORS","dei":null,"publiccode":null,"codemeta":null,"zenodo":null}},"created_at":"2016-10-18T14:30:07.000Z","updated_at":"2021-08-31T23:46:13.000Z","dependencies_parsed_at":null,"dependency_job_id":"47b75a17-96a9-4813-8bec-69b2b58e14d6","html_url":"https://github.com/lu-zero/libvpx","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/lu-zero/libvpx","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/lu-zero%2Flibvpx","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/lu-zero%2Flibvpx/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/lu-zero%2Flibvpx/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/lu-zero%2Flibvpx/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/lu-zero","download_url":"https://codeload.github.com/lu-zero/libvpx/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/lu-zero%2Flibvpx/sbom","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":268551874,"owners_count":24268654,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","status":"online","status_checked_at":"2025-08-03T02:00:12.545Z","response_time":2577,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["altivec","libvpx","powerpc","vsx"],"created_at":"2024-11-16T19:42:46.485Z","updated_at":"2025-08-03T13:17:05.153Z","avatar_url":"https://github.com/lu-zero.png","language":"C","funding_links":[],"categories":[],"sub_categories":[],"readme":"README - 24 January 2018\n\nWelcome to the WebM VP8/VP9 Codec SDK!\n\nCOMPILING THE APPLICATIONS/LIBRARIES:\n  The build system used is similar to autotools. Building generally consists of\n  \"configuring\" with your desired build options, then using GNU make to build\n  the application.\n\n  1. Prerequisites\n\n    * All x86 targets require the Yasm[1] assembler be installed[2].\n    * All Windows builds require that Cygwin[3] be installed.\n    * Building the documentation requires Doxygen[4]. If you do not\n      have this package, the install-docs option will be disabled.\n    * Downloading the data for the unit tests requires curl[5] and sha1sum.\n      sha1sum is provided via the GNU coreutils, installed by default on\n      many *nix platforms, as well as MinGW and Cygwin. If coreutils is not\n      available, a compatible version of sha1sum can be built from\n      source[6]. These requirements are optional if not running the unit\n      tests.\n\n    [1]: http://www.tortall.net/projects/yasm\n    [2]: For Visual Studio the base yasm binary (not vsyasm) should be in the\n         PATH for Visual Studio. For VS2017 it is sufficient to rename\n         yasm-\u003cversion\u003e-\u003carch\u003e.exe to yasm.exe and place it in:\n         Program Files (x86)/Microsoft Visual Studio/2017/\u003clevel\u003e/Common7/Tools/\n    [3]: http://www.cygwin.com\n    [4]: http://www.doxygen.org\n    [5]: http://curl.haxx.se\n    [6]: http://www.microbrew.org/tools/md5sha1sum/\n\n  2. Out-of-tree builds\n  Out of tree builds are a supported method of building the application. For\n  an out of tree build, the source tree is kept separate from the object\n  files produced during compilation. For instance:\n\n    $ mkdir build\n    $ cd build\n    $ ../libvpx/configure \u003coptions\u003e\n    $ make\n\n  3. Configuration options\n  The 'configure' script supports a number of options. The --help option can be\n  used to get a list of supported options:\n    $ ../libvpx/configure --help\n\n  4. Compiler analyzers\n  Compilers have added sanitizers which instrument binaries with information\n  about address calculation, memory usage, threading, undefined behavior, and\n  other common errors. To simplify building libvpx with some of these features\n  use tools/set_analyzer_env.sh before running configure. It will set the\n  compiler and necessary flags for building as well as environment variables\n  read by the analyzer when testing the binaries.\n    $ source ../libvpx/tools/set_analyzer_env.sh address\n\n  5. Cross development\n  For cross development, the most notable option is the --target option. The\n  most up-to-date list of supported targets can be found at the bottom of the\n  --help output of the configure script. As of this writing, the list of\n  available targets is:\n\n    arm64-android-gcc\n    arm64-darwin-gcc\n    arm64-linux-gcc\n    armv7-android-gcc\n    armv7-darwin-gcc\n    armv7-linux-rvct\n    armv7-linux-gcc\n    armv7-none-rvct\n    armv7-win32-vs11\n    armv7-win32-vs12\n    armv7-win32-vs14\n    armv7-win32-vs15\n    armv7s-darwin-gcc\n    armv8-linux-gcc\n    mips32-linux-gcc\n    mips64-linux-gcc\n    ppc64le-linux-gcc\n    sparc-solaris-gcc\n    x86-android-gcc\n    x86-darwin8-gcc\n    x86-darwin8-icc\n    x86-darwin9-gcc\n    x86-darwin9-icc\n    x86-darwin10-gcc\n    x86-darwin11-gcc\n    x86-darwin12-gcc\n    x86-darwin13-gcc\n    x86-darwin14-gcc\n    x86-darwin15-gcc\n    x86-darwin16-gcc\n    x86-iphonesimulator-gcc\n    x86-linux-gcc\n    x86-linux-icc\n    x86-os2-gcc\n    x86-solaris-gcc\n    x86-win32-gcc\n    x86-win32-vs10\n    x86-win32-vs11\n    x86-win32-vs12\n    x86-win32-vs14\n    x86-win32-vs15\n    x86_64-android-gcc\n    x86_64-darwin9-gcc\n    x86_64-darwin10-gcc\n    x86_64-darwin11-gcc\n    x86_64-darwin12-gcc\n    x86_64-darwin13-gcc\n    x86_64-darwin14-gcc\n    x86_64-darwin15-gcc\n    x86_64-darwin16-gcc\n    x86_64-iphonesimulator-gcc\n    x86_64-linux-gcc\n    x86_64-linux-icc\n    x86_64-solaris-gcc\n    x86_64-win64-gcc\n    x86_64-win64-vs10\n    x86_64-win64-vs11\n    x86_64-win64-vs12\n    x86_64-win64-vs14\n    x86_64-win64-vs15\n    generic-gnu\n\n  The generic-gnu target, in conjunction with the CROSS environment variable,\n  can be used to cross compile architectures that aren't explicitly listed, if\n  the toolchain is a cross GNU (gcc/binutils) toolchain. Other POSIX toolchains\n  will likely work as well. For instance, to build using the mipsel-linux-uclibc\n  toolchain, the following command could be used (note, POSIX SH syntax, adapt\n  to your shell as necessary):\n\n    $ CROSS=mipsel-linux-uclibc- ../libvpx/configure\n\n  In addition, the executables to be invoked can be overridden by specifying the\n  environment variables: CC, AR, LD, AS, STRIP, NM. Additional flags can be\n  passed to these executables with CFLAGS, LDFLAGS, and ASFLAGS.\n\n  6. Configuration errors\n  If the configuration step fails, the first step is to look in the error log.\n  This defaults to config.log. This should give a good indication of what went\n  wrong. If not, contact us for support.\n\nVP8/VP9 TEST VECTORS:\n  The test vectors can be downloaded and verified using the build system after\n  running configure. To specify an alternate directory the\n  LIBVPX_TEST_DATA_PATH environment variable can be used.\n\n  $ ./configure --enable-unit-tests\n  $ LIBVPX_TEST_DATA_PATH=../libvpx-test-data make testdata\n\nCODE STYLE:\n  The coding style used by this project is enforced with clang-format using the\n  configuration contained in the .clang-format file in the root of the\n  repository.\n\n  Before pushing changes for review you can format your code with:\n  # Apply clang-format to modified .c, .h and .cc files\n  $ clang-format -i --style=file \\\n    $(git diff --name-only --diff-filter=ACMR '*.[hc]' '*.cc')\n\n  Check the .clang-format file for the version used to generate it if there is\n  any difference between your local formatting and the review system.\n\n  See also: http://clang.llvm.org/docs/ClangFormat.html\n\nSUPPORT\n  This library is an open source project supported by its community. Please\n  email webm-discuss@webmproject.org for help.\n\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Flu-zero%2Flibvpx","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Flu-zero%2Flibvpx","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Flu-zero%2Flibvpx/lists"}