On Fri, Jun 2, 2017 at 10:56 AM, Andreas Håkon <andreas.ha...@protonmail.com> wrote: > Hi, > > This patch is based on the original work done by Timo Rothenpieler, and his > patch for static linking with libnpp: > [http://ffmpeg.org/pipermail/ffmpeg-devel/2016-June/195078.html](https://ffmpeg.org/pipermail/ffmpeg-devel/2016-June/195078.html) > > Based in my recomendations now it's possible to link directly to libnpp* > libraries without linking to the CUDA SDK: > [http://trac.ffmpeg.org/ticket/6405](https://trac.ffmpeg.org/ticket/6405) > http://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=2d978d1c721ae69a9007b530153067736d4ddc79 > > Then I created an updated version of the patch. > > By default the linking is the regular dynamic link (aka > "--disable-libnpp-static" config). > However, if you like to compile statically with "libnpp*_static.a" then add > these parameters: > $ configure ... --enable-nonfree --enable-libnpp --enable-libnpp-static > --enable-cuda --extra-cflags="-I/usr/local/cuda/include/" > --extra-ldflags="-L/usr/local/cuda/lib64/" > > This assumes the CUDA SDK is installed in "/usr/local/cuda".
I don't like that there is a separate configure option. We can link to other libraries dynamically or statically depending on what is found, without needing two configure options per library. - Hendrik _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
