On Tue, 27 Feb 2018 12:27:10 +0100 Hendrik Leppkes <h.lepp...@gmail.com> wrote:
> On Tue, Feb 27, 2018 at 12:13 PM, Nicolas George <geo...@nsup.org> wrote: > > Hendrik Leppkes (2018-02-27): > >> Something works today, you want to refactor it, you get to keep it > >> working. Its a simple rule. > > > > It is a simple rule, but not one that must be followed blindly. Please > > do not be dogmatic. > > > > Sometimes, we have to "break" an obscure case in order to make progress. > > I know you Linux people don't want to hear it, but Windows is not an > "obscure" platform. No, but using MSVC with FFmpeg is obscure. MinGW is preferred for multiple reasons. I hear you don't even use it for production yourself, only debugging occasionally. Also this is not about MSVC, but MSVC + hardware specific API supported by 1 vendor only. If someone really cares about nvenc with FFmpeg+MSVC, it'd get fixed in no time anyway. Sure, there's no time pressure, but if we don't do anything, it'll take years, and we'll always hear "but nvidia has in-tree headers" from various vendors of single-vendor hardware specific APIs. It seems someone is actually looking into this now and trying this with MSVC, so maybe this will be a non-issue. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
