-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Enable riscv64 R2R in installer #96941
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
Changes from 9 commits
959d350
5aa1708
5bd9942
f3d8697
ff30751
f2a372c
6d5c05a
3ef88b8
6d771e6
e23ab08
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -69,5 +69,11 @@ | |
<UnofficialBuildRID Include="linux-musl-ppc64le"> | ||
<Platform>ppc64le</Platform> | ||
</UnofficialBuildRID> | ||
<UnofficialBuildRID Include="linux-riscv64"> | ||
<Platform>riscv64</Platform> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Am I right that this things like this and the ones in eng/targetingpacks.targets will help with build issues like in #97791 ( Also after update of sdk to 9.0.1-preview1 (#98476), similar issue started to happen during coreclr tests build:
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Might be also related to #96978 even tough Crossgen2 should be disabled currently ? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yup, it will help those. |
||
</UnofficialBuildRID> | ||
<UnofficialBuildRID Include="linux-musl-riscv64"> | ||
<Platform>riscv64</Platform> | ||
</UnofficialBuildRID> | ||
</ItemGroup> | ||
</Project> |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -11,8 +11,6 @@ | |
<PublishReadyToRun Condition="'$(TargetOS)' == 'netbsd' or '$(TargetOS)' == 'illumos' or '$(TargetOS)' == 'solaris' or '$(TargetOS)' == 'haiku'">false</PublishReadyToRun> | ||
<!-- Disable crossgen on FreeBSD when cross building from Linux. --> | ||
<PublishReadyToRun Condition="'$(TargetOS)'=='freebsd' and '$(CrossBuild)'=='true'">false</PublishReadyToRun> | ||
<!-- Disable crossgen on riscv64. --> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Not sure about removal of this right now, because currently crossgen2 is still not fully functional. Crossgen2 itself is compiled with crossgen2 with no issues, but then it crashes during launch. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We don't use this crossgen2 build in tests yet (#80154). So the tests will continue to use In the nuget package for end-user, we will have PublishReadyToRun variant with this PR, which makes sense since the whole riscv64 project is in-progress? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ok, I think this is fine. We usually use crossgen2.dll directly, so we'll be able to continue doing so. And having crossgened crossgen2 in nuget is not much of a difference, since plain crossgen2 in nuget can also show issues on certain dlls. |
||
<PublishReadyToRun Condition="'$(TargetArchitecture)'=='riscv64'">false</PublishReadyToRun> | ||
<!-- These components are installed by the root shared framework, but not others. --> | ||
<IncludeWerRelatedKeys>true</IncludeWerRelatedKeys> | ||
<IncludeBreadcrumbStoreFolder>true</IncludeBreadcrumbStoreFolder> | ||
|
Uh oh!
There was an error while loading. Please reload this page.