-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Comments
@dagood you transfered this from core-setup. 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. |
cc: @janvorli |
@dagood Thank you very much for your help(^_^) |
ping @janvorli |
…304.3 (dotnet#831) [main] Update dependencies from dotnet/arcade
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. |
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
The text was updated successfully, but these errors were encountered: