On 2 July 2017 at 00:29, Matt Oliver <protogo...@gmail.com> wrote: > On 2 July 2017 at 00:14, Hendrik Leppkes <h.lepp...@gmail.com> wrote: > >> On Sat, Jul 1, 2017 at 3:18 PM, Matt Oliver <protogo...@gmail.com> wrote: >> > This only enables dlls that are packaged with the application to be >> > loaded. Due to the limitations of WinRT/UWP it is not allowed to load >> > external/system dlls so this cannot be used as a complete replacement >> > for normal win32 dll loading. >> >> Most of the things we do load are system libraries, so does it really >> make sense to pretend it works? >> > > No, but this was in response to a previous patch posted to the mailing > list that just set the return to null. Its mainly just to prevent build > errors when including the header and I figured that at least a function > that works would be better than just returning null as this may be of use > in the future. > Of course all code we have wont work and should be handled specifically > (like the recent dx lib linking) but i figured this was better than nothing. >
Does anyone have any issue with me applying this? _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
