LibUV should use win8-arm as the RID

[davidfowl]

It currently places WinArm32 assets under win7-arm that is not a valid RID/platform configuration.

/cc @gkhanna79

Moved from https://github.com/dotnet/corefx/issues/13311

[muratg]

I thought there were other problems with running kestrel on arm, but perhaps I'm wrong. cc @moozzyk

[moozzyk]

libuv works fine on windows arm. It originally used win10-arm but I had to move it to win7-arm or to avoid issues during publish (aspnet/KestrelHttpServer#340 + linked bugs). Note that the publish there was the dnu publish so things might work now. Hard to verify since AFAIK there is no runtime for arm at the moment.

[Petermarcu]

When do we think we can get a fix for this? I'd love to be able to do some hacking on Win10 IoT :)

[Petermarcu]

Simple change I think. I don't really know how to build and validate. #16

[Petermarcu]

I also wasn't sure what branch is the right one to go against for vNext.

[moozzyk]

This has been fixed in both repos now.

[Petermarcu]

Thanks!

[gkhanna79]

But #16 seems to be open. Which PRs fixed them and where?

[moozzyk]

@gkhanna79 - I rebased on changes I made to update libuv to 1.10.0. This PR was pushed as a16eed2