Thrameos
commented
1 day ago Our releases are limited by the range of machines available on azure dev. The comment in the log was for systems available at the time. I am not sure if we were on azure or the previous cloud system which we had to abandon since.
I am not sure that there is currently an arm linux system in the image pool. It may be possible to use cross compiler tools on azure but we don't have such a pattern. You are always free to fork a copy and trigger dev builds using a free azure dev account (or am alternative github connected cloud) and getting the produced binaries or contributing build patterns to our release script. If the architecture is not on azure, it may require a different cloud.
Openning a second issue is also not necessary. You are always free to respond to a closed issue and the maintainer can reopen it. Until I run the release scripts I won't have any idea what images we will be producing. I don't have access the any machines for building images beyond the cloud so unless we have a build solution it won't happen.
https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml
@Thrameos Please help here. I posted the issue https://github.com/jpype-project/jpype/issues/1227 on the arm support here. However, it was closed brutally and disrespectfully by someone. Same for https://github.com/jpype-project/jpype/issues/1228
I don't think the issue is fixed and still see people asking for it or experiencing the same issue. For example, https://github.com/jpype-project/jpype/discussions/1203 https://github.com/jpype-project/jpype/issues/1227#issuecomment-2446429093 https://github.com/jpype-project/jpype/issues/1215 https://github.com/jpype-project/jpype/issues/1119
The doc said it should support aarch64 since 1.2.1 but the later releases didn't.
Hopefully the issue can be fixed soon. Thanks.