ffmpeg can generate lookup tables at build time instead of runtime, but this is no longer a recommended option. The size impact is significant (12% of the total libavcodec size, nearly 2MB), the runtime impact of dynamic tables isn't too costly, and only a few codecs actually use the pre-generated tables (MP3, notably).
Signed-off-by: Ross Burton <[email protected]> --- meta/recipes-multimedia/ffmpeg/ffmpeg_4.1.3.bb | 1 - 1 file changed, 1 deletion(-) diff --git a/meta/recipes-multimedia/ffmpeg/ffmpeg_4.1.3.bb b/meta/recipes-multimedia/ffmpeg/ffmpeg_4.1.3.bb index 147388d9b7c..6d230c33169 100644 --- a/meta/recipes-multimedia/ffmpeg/ffmpeg_4.1.3.bb +++ b/meta/recipes-multimedia/ffmpeg/ffmpeg_4.1.3.bb @@ -106,7 +106,6 @@ EXTRA_OECONF = " \ --extra-cflags="${TARGET_CFLAGS} ${HOST_CC_ARCH}${TOOLCHAIN_OPTIONS}" \ --extra-ldflags="${TARGET_LDFLAGS}" \ --sysroot="${STAGING_DIR_TARGET}" \ - --enable-hardcoded-tables \ ${EXTRA_FFCONF} \ --libdir=${libdir} \ --shlibdir=${libdir} \ -- 2.20.1 -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
