coreclr not producing NuGet packages, core-setup not using built coreclr as a result.

[pauldotknopf]

I noticed this:

source-build/repos/coreclr.proj

Line 9 in e50ba2d

<BuildArguments Condition="$(Platform.Contains('arm'))">$(BuildArguments) skipnuget cross -skiprestore cmakeargs -DFEATURE_GDBJIT=TRUE</BuildArguments>

The skipnuget causes the core-setup project to not find the coreclr nuget packages.

This causes the core-setup project to fetch the coreclr nuget packages from public feeds, instead of the one built locally.

Am I missing something?

[crummel]

Our ARM build isn't being kept up right now and likely doesn't even build without modifications. We have a couple of related issues: #324 and #655. This is definitely something we should fix when we do look at ARM again though, thanks!

[pauldotknopf]

Out of curiosity, how do you guys currently deploy the ARM SDK? Does each repo produce NuGet packages in their own custom CI pipeline?

[crummel]

Yes, the individual repos have ARM builds. I don't think you'll be able to see the build itself, but you can see the status of core-sdk's ARM build on their readme, for instance: https://github.com/dotnet/core-sdk.

[MichaelSimons]

[Triage] Arm64 is officially supported. This issue is very old. If you are still having troubles building on ARM, please open a new issue with the current problems.