Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use ProductMonikerRid instead of CoreSetupRid for SDK RID. #141

Merged
merged 1 commit into from
Nov 8, 2018

Conversation

peterhuene
Copy link

This commit changes NETCoreSdkRuntimeIdentifier to be based off of
ProductMonikerRid instead of CoreSetupRid.

CoreSetupRid is set to the host RID for the build, by default. For most
architectures, this was fine. However, for ARM/ARM64 builds, we cross-build,
so CoreSetupRid is actually x64 and not ARM/ARM64.

As a result, the default apphost being used isn't built for ARM so dotnet run
fails with an exec format error when trying to exec the apphost.

Instead, we should be using the RID of the product being built rather than the
host RID.

Fixes dotnet/cli#10291.

This commit changes `NETCoreSdkRuntimeIdentifier` to be based off of
`ProductMonikerRid` instead of `CoreSetupRid`.

`CoreSetupRid` is set to the host RID for the build, by default.  For most
architectures, this was fine.  However, for ARM/ARM64 builds, we cross-build,
so `CoreSetupRid` is actually x64 and not ARM/ARM64.

As a result, the default apphost being used isn't built for ARM so `dotnet run`
fails with an exec format error when trying to exec the apphost.

Instead, we should be using the RID of the product being built rather than the
host RID.

Fixes dotnet/cli#10291.
@peterhuene peterhuene added this to the 3.0.1xx milestone Nov 8, 2018
@peterhuene peterhuene requested a review from a team November 8, 2018 02:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants