No description
For large intra frame intervals or for a choice of bit rate that causes large bits per frame, it possible that while computing number of bits available in the gop overflow the datatype bounds. For these calculations use number_t as this offers wider space Bug: oss-fuzz-63044 Test: avc_enc_fuzzer Change-Id: Ifee9130f0021f77905aea67832abc044537088e5 |
||
|---|---|---|
| .github/workflows | ||
| cmake | ||
| common | ||
| decoder | ||
| encoder | ||
| examples | ||
| fuzzer | ||
| tests | ||
| .clang-format | ||
| .gitignore | ||
| Android.bp | ||
| CMakeLists.txt | ||
| FrameInfo.md | ||
| libavc_blocklist.txt | ||
| LICENSE | ||
| METADATA | ||
| MODULE_LICENSE_APACHE2 | ||
| NOTICE | ||
| OWNERS | ||
| PREUPLOAD.cfg | ||
| README.md | ||
LIBAVC
Getting Started Document
LibAVC build steps
Supports:
- aarch32/aarch64 on Linux.
- aarch32/aarch64 on Android.
- x86_32/x86_64 on Linux.
Native Builds
Use the following commands for building on the target machine
$ cd external/libavc
$ mkdir build
$ cd build
$ cmake ..
$ make
Cross-compiler based builds
Building for x86_32 on a x86_64 Linux machine
$ cd external/libavc
$ mkdir build
$ cd build
$ CFLAGS="-m32" CXXFLAGS="-m32" LDFLAGS="-m32" cmake ..
$ make
Building for aarch32/aarch64
Update 'CMAKE_C_COMPILER', 'CMAKE_CXX_COMPILER', 'CMAKE_C_COMPILER_AR', and 'CMAKE_CXX_COMPILER_AR' in CMAKE_TOOLCHAIN_FILE passed below
$ cd external/libavc
$ mkdir build
$ cd build
For aarch64
$ cmake .. -DCMAKE_TOOLCHAIN_FILE=../cmake/toolchains/aarch64_toolchain.cmake
$ make
For aarch32
$ cmake .. -DCMAKE_TOOLCHAIN_FILE=../cmake/toolchains/aarch32_toolchain.cmake
$ make