Enable winuwp_h264 build for win target

[Holo-Krzysztof]

Fixes #109.

I haven't tested it at runtime yet due to our test app being UWP for the moment, but it builds fine.

[robin-raymond]

@SergioOpenPeer my only concern would be how to push back to google since I don't know they would want to build this by default and we may need a compilation option for it... but I don't know we can easily add an args.gn for it easily in a way that would be acceptable to push back. So we need to discuss more on how to accept it and push it back upstream.

[Holo-Krzysztof]

Do they have functionality in their code that is bound to a specific Windows version at compile time?

[robin-raymond]

@Holo-Krzysztof the WebRTC targets a much lower platform versions. It would likely need to be a flag to specify this code to be compiled or not, and then there's the question of how the code would get integrated and used into the built output result.

[Holo-Krzysztof]

What about adding a "Microsoft/Win10-specific" build flag? There's build_with_mozilla for Firefox, so it wouldn't be without precedent.

[ispysoftware]

i integrated these changes in m75 - it builds but it doesn't work, in media/base/codec.cc:

this is returning false because the params2 object is empty

[ispysoftware]

adding the codec properties resolves the issue

add h264 profiles to winuwp_h264_factory.cc

supported_codecs.push_back(
        SdpVideoFormat(cricket::kH264CodecName,
                       {{cricket::kH264FmtpProfileLevelId, "42100b"},
                        {cricket::kH264FmtpLevelAsymmetryAllowed, "1"},
                        {cricket::kH264FmtpPacketizationMode, "0"}}));
    supported_codecs.push_back(
        SdpVideoFormat(cricket::kH264CodecName,
                       {{cricket::kH264FmtpProfileLevelId, "42100b"},
                        {cricket::kH264FmtpLevelAsymmetryAllowed, "1"},
                        {cricket::kH264FmtpPacketizationMode, "1"}}));

[kzq0717]

hello , Can you help me , How to integrate BWE mode into webrtc-uwp-sdk.