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

Produce LLVM packages for Apple Silicon #99

Merged
merged 3 commits into from
Mar 5, 2021

Conversation

directhex
Copy link

@directhex directhex commented Mar 4, 2021

  Microsoft.NETCore.Runtime.Mono.LLVM.Tools -> /Users/directhex/Projects/llvm-project/artifacts/packages/Release/Shipping/runtime.osx.11.0-arm64.Microsoft.NETCore.Runtime.Mono.LLVM.Tools.9.0.1-ci.nupkg
  Microsoft.NETCore.Runtime.Mono.LLVM.Sdk -> /Users/directhex/Projects/llvm-project/artifacts/packages/Release/Shipping/runtime.osx.11.0-arm64.Microsoft.NETCore.Runtime.Mono.LLVM.Sdk.9.0.1-ci.nupkg

@steveisok steveisok self-requested a review March 5, 2021 01:07
@directhex directhex merged commit f2a7fc3 into dotnet:release/9.x Mar 5, 2021
@@ -12,7 +12,8 @@

<!-- Distro rid is passed as runtimeos-arch-->
<_parseDistroRid>$(__DistroRid)</_parseDistroRid>
<_parseDistroRid Condition="'$(_parseDistroRid)' == '' and '$(__BuildOS)' == 'OSX'">osx.10.12-x64</_parseDistroRid>
<_parseDistroRid Condition="'$(_parseDistroRid)' == '' and '$(__BuildOS)' == 'OSX' and '$(Platform)' == 'arm64'">osx.11.0-arm64</_parseDistroRid>
<_parseDistroRid Condition="'$(_parseDistroRid)' == '' and '$(__BuildOS)' == 'OSX' and '$(Platform)' != 'arm64'">osx.10.12-x64</_parseDistroRid>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@directhex given we use CMAKE_OSX_DEPLOYMENT_TARGET=10.13 we should probably bump the RID to osx.10.13-x64? or actually why do we use a version-specific RID at all rather than osx-x64 like we do elsewhere?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is an EXCELLENT QUESTION for past Jo, because present day Jo is experiencing what a pain in the ass it is to consume it this way, given how llvm-init.proj is written

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.

3 participants