Do you mean that we should distribute external libraries? In this case, libva.
-----Original Message----- From: libav-devel [mailto:[email protected]] On Behalf Of Remi Denis-Courmont Sent: Wednesday, January 14, 2015 6:19 PM To: [email protected] Subject: Re: [libav-devel] [PATCH] vaapi: check the libva availability during the execution. Le mercredi 14 janvier 2015, 16:09:47 Kim Gunsoo a écrit : > - 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. I utterly fail to see any point in doing this. libva is just a glorified convenience wrapper around dlfcn.h. It consumes little memory and disk space of its own. The vendor-specific drivers do take a lot of disk space. But libva does not depend on them - that is the whole point... -- Rémi _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
