UWP, an application framework from Microsoft for Windows, aims higher in terms of security. And as a result, unfortunately, they thought of turning warnings into errors and introducing some safer functions that are not portable.
This pull request removes two obstacles in front of building the current version in UWP
UWP finds usage of uninitialized local pointers as evil, reporting errors upon them. This is quite reasonable and has an easy fix of initializing the pointers as NULL, so I've done this to about three of them.
UWP thinks using sscanf is wrong and suggests using sscanf_s intsead, which I would not agree if I am in charge of maintaining a portable library. Defining _CRT_SECURE_NO_WARNINGS tells UWP to stop talk about this, so I have added this definition. I added it as a public one of srtp2, so it can spread through the project.
UWP, an application framework from Microsoft for Windows, aims higher in terms of security. And as a result, unfortunately, they thought of turning warnings into errors and introducing some safer functions that are not portable.
This pull request removes two obstacles in front of building the current version in UWP