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

Have you compiled the. NET Core version of Armel? #831

Closed
whuanle opened this issue Aug 27, 2019 · 6 comments
Closed

Have you compiled the. NET Core version of Armel? #831

whuanle opened this issue Aug 27, 2019 · 6 comments
Labels
arch-arm32 area-Meta backlog-cleanup-candidate An inactive issue that has been marked for automated closure. discussion no-recent-activity question Answer questions and provide assistance, not an issue with source code or documentation.
Milestone

Comments

@whuanle
Copy link

whuanle commented Aug 27, 2019

I don't know much about cross compilation and C/C++.But now Ineed to run .NET Core 2.x or 3.0 on the armel development board.I have a server that I can use (armhf, arm64, x86-64).

I have found this Issue, but the method is not available:
https://github.com/dotnet/core-setup/issues/3100

@dagood dagood transferred this issue from dotnet/core-setup Aug 28, 2019
@carlossanlop
Copy link
Member

@dagood you transfered this from core-setup. Do you know who can look into this?

@dagood
Copy link
Member

dagood commented Dec 13, 2019

Do you know who can look into this?

No, apologies I missed leaving a comment, my goal was that someone in the community might see this in dotnet/core who is familiar with the platform. I didn't think Core-Setup would get the right traffic.

@whuanle, do I understand you right that you want to build the .NET Core Runtime for armel, by cross compiling on an armhf, arm64, or x86-64 machine. and you're looking for help with that?

I found a few docs that might put you in the right direction:

I'm moving this (again, sorry) to the dotnet/runtime repo where you would be doing the building, and maybe this will spur some doc updates as well. The paths in those docs look out of date after corelr, corefx, and core-setup were consolidated into dotnet/runtime.

@dagood dagood transferred this issue from dotnet/core Dec 13, 2019
@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added the untriaged New issue has not been triaged by the area owner label Dec 13, 2019
@wfurt
Copy link
Member

wfurt commented Dec 17, 2019

cc: @janvorli

@whuanle
Copy link
Author

whuanle commented Dec 29, 2019

@dagood Thank you very much for your help(^_^)

@joperezr joperezr added question Answer questions and provide assistance, not an issue with source code or documentation. and removed untriaged New issue has not been triaged by the area owner labels Jul 7, 2020
@joperezr joperezr added this to the Future milestone Jul 7, 2020
@joperezr
Copy link
Member

joperezr commented Jul 7, 2020

ping @janvorli

Copy link
Contributor

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.

@dotnet-policy-service dotnet-policy-service bot added backlog-cleanup-candidate An inactive issue that has been marked for automated closure. no-recent-activity labels Jan 6, 2025
@whuanle whuanle closed this as completed Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
arch-arm32 area-Meta backlog-cleanup-candidate An inactive issue that has been marked for automated closure. discussion no-recent-activity question Answer questions and provide assistance, not an issue with source code or documentation.
Projects
No open projects
Development

No branches or pull requests

8 participants