https://community.thinlinc.com/t/tl-client-for-arm64-or-android/69
Now that ThinLinc 4.17.0 was released I would like to raise attention here since more and more aarch64/ARM64 platforms (RaspberryPi5, etc.) are existing and we are in the need for a native aarch64 type of ThinLinc client. So would you please comment when a aarch64 client version might be released or when the ThinLinc might appear on an open source platform like GitHub so that third-party developers could assist in getting such alternative platforms supported before cendio is doing it themselves?!?
Raspberry Pi are still recommending 32-bit, and are still shipping 32-bit by default in their kits. So at the moment, that is still the compatible choice for us. I can not find any information on when they might switch the default. They are still manufacturing their 32-bit devices, so the switch might be once they stop doing that. They have unfortunately introduced a bug in their 64-bit OS that currently prevents 32-bit programs from working: https://github.com/raspberrypi/bookworm-feedback/issues/120 Hopefully they'll have it fixed soon. Until then, a workaround is documented on that issue.
Sorry, but there is more than just RaspberryPiOS. There is Armbian, there is Ubuntu and there is Debian for RaspberryPi or other ARM-driven systems. In addition, the thinroot system [1] I am maintaining (a buildroot based thinclient/kiosk system also supporting ThinLinc) is also shipping with pure aarch64 support (kernel and OS components) without any 32bit multilib support. So please reconsider shipping a native aarch64 / 64bit ARM version of the ThinLinc client or provide all the sources and dependencies for the client so that the open source community can do the work for you. Or what else is stopping you from providing aarch64 native builds of your ThinLinc clients? [1] https://github.com/jens-maus/thinRoot
Statistics from usage of the Raspberry Pi imager: https://rpi-imager-stats.raspberrypi.com/ 64-bit is the clear popular choice. It is unclear what is hiding in "other", though. It includes both 32-bit and 64-bit variants.
I had a look to see what other applications are doing: Firefox: Only very recently did ARM64 releases (March 2025), never did 32-bit ARM Chrome: No ARM support at all RealVNC: Provides 64-bit "Raspberry Pi" support since mid 2022. Still provides 32-bit support. Citrix: Provides 64-bit ARM since 2309 (preview in 2305). Dropped 32-bit ARM in their 2405 release.
Sorry to bother again, but can you please elaborate what exactly is hindering you in getting aarch64/ARM64 support for the ThinLinc client going? AFAICS there is no question if aarch64/ARM64 is a common platform these days (it clearly is!). So it is rather the question if you get the ThinLinc client and its dependencies compiled for aarch64/ARM64 or not. And if you lack the manpower or resources, I would again suggest to finally open source the ThinLinc client and let the community do the porting for you. IMHO it shouldn't take years (like this ticket shows) to port the client and its dependencies to aarch64/ARM64 but simply a few weeks/months. And having the ThinLinc client open sourced could have some other clear benefits for you as the vendor behind ThinLinc: It would broaden the community around it because others can then port it to other platform, provide bug fixes to you or enhance the client. So please seriously consider open sourcing the ThinLinc client and its dependencies.
