Generate nuget packages for Arm64 build

[gkhanna79]

@weshaggard @ericstj @pgavlin @rahku PTAL

CC @haripulapaka

[gkhanna79]

Fixes https://github.com/dotnet/coreclr/issues/3080

[gkhanna79]

@dotnet-bot test Windows_NT arm64 Checked

[gkhanna79]

@dotnet-bot test Windows_NT arm64 Release

[gkhanna79]

@dotnet-bot test Windows_NT arm64 Checked please

[gkhanna79]

@dotnet-bot test Windows_NT arm64 Release please

[rahku]

Thanks. native arm64 crossgen seems missing from the package. If it is not placed in the package we will lose it or it needs to be re-built everytime we need it.

[gkhanna79]

native arm64 crossgen seems missing from the package.

For now, I have intentionally kept it out since it is not expected to be used in production scenarios (i.e. we expect to generate native images in cross-compilation scenario and the crossgen under tools\x64_arm64 should suffice).

Is there a specific scenario you have in mind?

[rahku]

Yes in order to be able to run R2R tests on the device we need native crossgen because crossgen is run as part of runtests.cmd

[rahku]

Should be also required to run R2R helix runs on the target.

[gkhanna79]

@dotnet-bot test Windows_NT arm64 Checked please

[gkhanna79]

@rahku Sounds good. I have added native crossgen to the package as well.

[weshaggard]

orthogonal but something I notices while reviewing. This claims to support arm but I don't see an arm configuration below.

[gkhanna79]

I dont think it claims to support arm per https://github.com/dotnet/buildtools/blob/3c700d1ecc358c6c1b3ffbaaeb49e7864a8e9ba7/src/Microsoft.DotNet.Build.Tasks.Packaging/src/PackageFiles/Packaging.targets#L125 which expects a trailing ";" to enable the platform.

That said, I will be looking into enabling Arm32 once I am done with this.

[weshaggard]

LGTM

[rahku]

LGTM