On 14/01/15 08:09, Kim Gunsoo wrote:
> - If you are deploying libav, build and runtime environments are different.
> Using --enable-vaapi can might cause to fail on the execution.
> - This is an optional feature to check the execution environment in the
> runtime.
> It can prevent to fail.
>
> - Added new configure option(--enable-runtimedetect-vaapi) to supports
> backward compatibility.
> Added new function(ff_vaapi_probe()) to check libva availability.
> Modified avcodec_register_all() function to determine whether AVHWAccel is
> registered or not.
The approach is interesting, I'd change the the configure so it would be
--enable-vaapi-dlopen
and have it not fail if` --enable-vaapi` is also set.
We recently got some patches that would use dlopen so probably we can
consolidate the dlopen support (and convince those the dislike it that
isn't bad to provide an option for it).
The patch in itself has few nits but the general concept is fine for me.
lu
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
