You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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)
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.
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?
The text was updated successfully, but these errors were encountered: