Open lukasf opened 6 years ago
Agreed.
It makes sense
Disagree. For example, our products uses Windows 8.1/7.0 SDKs and these products compatible with Windows 7 SP1.
@lukasf @mcosmin222 @reego-fr I updated the BuildFFmpeg.bat script to work only with Visual Studio 2017. It also builds the libraries for ARM64. You can get the script from here. You can also get the latest compiled libraries for UWP (FFmpeg 4.1 Release) from here.
@ionutdanila On my fork, there is also a VS2017 version of the build file. We are just updating the fork to correctly work with FFmpeg 4.1. There were some breaking changes. You might run into problems when using FFmpeg 4.1 with the MS version of the lib.
@lukasf I already updated the source code for FFmpegInterop to work with FFmpeg 4.1. I also added a sample application to see the NuGet Package in action.
These are really old platforms. Microsoft stopped supporting WP8.1 already, user base on Windows 8.1 is very small and shrinking. I do not think that anyone will start a new project targeting Windows 8.1 or even WP 8.1. Windows 10 is the way to go for all new apps. Let's move on.
Having to maintain these platforms makes adding new features really difficult. Not only would we have to install VS2015 (a whooping 26GB install with all required packages) just to check that they build, but theoretically, we would also have to test new features on Windows 8.1 and even WP 8.1, which is just not feasible anymore.
So I propose to drop support for these platforms for future development. A support branch can be created, so those who still do care about these platforms (anyone there?) can still build it. Project files for Windows 10 version should be updated to use the VS2017 platform toolkit.
Please let me know what you think.