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

Does Terminal.GUI supports aarch64 arhitecture? #3403

Open
otalado opened this issue Apr 13, 2024 · 3 comments
Open

Does Terminal.GUI supports aarch64 arhitecture? #3403

otalado opened this issue Apr 13, 2024 · 3 comments
Labels

Comments

@otalado
Copy link

otalado commented Apr 13, 2024

I wonder if Terminal.GUI supports an aarch64 architecture? I am wondering as I tried to run the sample app on Raspberry Pi 5 Bookworm 64bit. It fails with strange errors, but from the errors, I cannot figure out what's the issue.
If it does not, are you planning to support the 64-bit ARM chips anytime in the future?

@tig tig added the bug label Apr 13, 2024
@tig
Copy link
Collaborator

tig commented Apr 13, 2024

If dotnet 8 is supported on that platform Terminal.Gui should work.

Questions for you:

  1. What version of Terminal.gui are you trying?
  2. If v1, can you please try v2?
  3. What are the "strange errors" you are seeing. It's really hard to help without more details.

Cheers!

@tznind
Copy link
Collaborator

tznind commented Apr 13, 2024

Not sure about 'Raspberry Pi 5 Bookworm 64bit' specificially, but I have had Terminal.Gui running in Raspbery Pi (both with the UI OS and the console only OS). See #1697 for various videos of Terminal.Gui running on raspberry Pi and debugging of mouse in console only install. Or you can follow this direct link which shows UICatalog with mouse and keyboard control (YouTube)

@dodexahedron
Copy link
Collaborator

dodexahedron commented Apr 18, 2024

As long as you compile against AnyCPU or the appropriate platform-specific TFM, you should be able to use it on any hardware and OS capable of running .net 8.

I don't think we have any hardware intrinsics anywhere that would prevent such use, anyway.

That said, I've not looked specifically at the nuget packaging setup in detail, which would be the only other place I'd imagine there would be any possible hiccups, if nuget can't resolve what it thinks it needs to grab for a project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: No status
Development

No branches or pull requests

4 participants