Hi Henry,
(repost without quotes... sorry!)
> I don't dispute that static linking might be useful, but I'm still not
> liking needing a separate configure option, if perhaps another
> solution can be found.
I'm glad if you point me in to another solution.
Meanwhile this solution is simple and ef
Hi,
Sorry, but ProtonMail has troubles with "non-top" replies...
Original Message
Subject: Re: [FFmpeg-devel] [PATCH] configure: support static libnpp [v2]
Local Time: June 2, 2017 12:03 PM
UTC Time: June 2, 2017 10:03 AM
From: h.lepp...@gmail.com
To: FFmpeg d
Sent with [ProtonMail](https://protonmail.com) Secure Email.
Original Message
Subject: Re: [FFmpeg-devel] [PATCH] configure: support static libnpp [v2]
Local Time: June 2, 2017 12:03 PM
UTC Time: June 2, 2017 10:03 AM
From: h.lepp...@gmail.com
To: FFmpeg development discussions
On Fri, Jun 2, 2017 at 11:56 AM, Andreas Håkon
wrote:
> Hi Hendrik,
>
> 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.
>
> I understand. However, thi
pile a regular FFmpeg with shared objects and dependent
to the NVidia DRIVER, but not with the CUDA SDK, you can use this patch.
I hope you agree this explanation. This patch is really useful.
Regards,
A.H.
Sent with [ProtonMail](https://protonmail.com) Secure Email.
---- Original Message
On Fri, Jun 2, 2017 at 10:56 AM, Andreas Håkon
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-Jun
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
