How to build for win arm64? #123
-
|
Thought i just try:
But no special download available. arm64, for windows 11 on parallels on a mac m1,2,3,4? |
Beta Was this translation helpful? Give feedback.
Replies: 11 comments 18 replies
-
|
Right now I don't have arm builds of windows or linux. This is on my list but it requires me to either figure out how to cross-compile on an x64 github runner, or set up a self-hosted github runner on arm64. What kinds of machines run windows on arm64 currently? Most/all of the consumer desktops and laptops I see are on x64. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, you are totally right. I was not sure, if i missed that in the docs.. I use it myself mainly now (parallels on a m1 mac). While testing out my jdeploy'ed javafx app i see its a lot slower on virtualized Windows 11. Which gives me a bit of a bad feeling, as i cant really test it out in the same speed as on mac. Well, that would not be a reason to implement it as its "ok" to use it - although slower. But I want to deploy the app to a Microsofts Surface's (a maybe user..) - which is also is x86. Fine too. But i have a feeling that this company will have Surface Pro X, which is arm and i think the only one, very soon.. |
Beta Was this translation helpful? Give feedback.
-
|
Found this: https://bugs.openjdk.org/browse/JDK-8314064. I dont now if that helps, but it should work at least without cross-compilation on javafx 22. |
Beta Was this translation helpful? Give feedback.
-
|
Depending on the fixed issue above it should be either possible. Building which i think is not what you are able to to now but crosscompiling should be possible already. Taking that: cross-compiling should be as easy as do: mvn package -Djavafx.platform=windows-aarch64 I dont now if this helps for the githubrunner though. |
Beta Was this translation helpful? Give feedback.
-
|
So it looks like this is supported now - my app runs on Surface Pro ARM and in Parallels on Mac M4. However, it looks like it downloads Java 11, even though I need Java 8. My SnapCode needs Java 8 for now (I'm limited in the browser by CheerpJ) and Java 11 is incompatible with my tools.jar, which is stuck on Java 8. I'm guessing though that there might not be a Java 8 for Windows ARM, so there might not be a solution here (though I'm really hoping for CheerpJ to get me to Java 11 or above :-) ) |
Beta Was this translation helpful? Give feedback.
-
|
Which app are you trying this on? I'd like to try and install to take a look. |
Beta Was this translation helpful? Give feedback.
-
|
This is ~snapcodejava, running on Windows ARM. The app runs fine, but if you click on one of the samples (like Tetris), it will try and fail to compile (because Java 11 doesn't like my tools.jar from Java 8). |
Beta Was this translation helpful? Give feedback.
-
|
Off to a dance recital. Will look later today. One thing to note is that i have not compiled the launcher for arm yet so if it is running on arm, that is news to me. probably it's running on some sort of emulation. |
Beta Was this translation helpful? Give feedback.
-
|
That's pretty amazing - because it seems to be running perfectly, even downloaded the jre-amd64. |
Beta Was this translation helpful? Give feedback.
-
|
Found the issue with java 8. I posted a ticket here #131 I'm close to finding a solution. Just need to bang my head against it for a while longer. |
Beta Was this translation helpful? Give feedback.
-
|
Hi. Maybe any news on that...? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the nudge. i see that arm runners are now available on github, so i should be able to do this now. Not sure when i'll have a chance. Hopefully within next few weeks. |
Beta Was this translation helpful? Give feedback.
-
|
That would be really helpful and thus fantastic! Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
+1 for the ARM builds! The x86_64 installers are working fine without any issues on ARM Windows 11 in a UTM VM (emulation?), but ARM Linux (Ubuntu 22.04) errors out with "package architecture (amd64) does not match system (arm64)". JDeploy is such a great tool, thank you :-) |
Beta Was this translation helpful? Give feedback.
-
|
I totally agree - JDeploy is amazing! I don’t know what I would do without it - things had gotten so bad with my old native app stuff, I had mostly given up. Thanks Steve!
jeff
… On Mar 13, 2025, at 4:49 AM, GCalTools ***@***.***> wrote:
+1 for the ARM builds! The x86_64 installers are working fine without any issues on ARM Windows 11 in a UTM VM (emulation?), but ARM Linux (Ubuntu 22.04) errors out with "package architecture (amd64) does not match system (arm64)".
JDeploy is such a great tool, thank you :-)
—
Reply to this email directly, view it on GitHub <#123 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJ7YSXD7ZKAOEJQAKVWS732UFIBBAVCNFSM6AAAAABT4VAF66VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENBYGU4TCOI>.
You are receiving this because you commented.
|
Beta Was this translation helpful? Give feedback.
-
|
Today, I released the new jDeploy desktop app which aims to make it easier for new users to get started. It is deployed using jDeploy as a desktop app. No longer requires any dependencies (like npm). It provides gui options for creating new projects from templates (@reportmill, it would be cool to add a project template for snapcode based projects), and configuring existing projects to us jDeploy. It supports publishing to both npm and GitHub directly in the app (GitHub used to only work using github actions - now it works in app by pressing "Publish"). It also fixes up the authentication workflow for npm and GitHub with support for 2FA. I'll be writing a blog post about this to announce it, but thought I'd drop it here as a glimpse of what I've been working on lately. Now that this is out the door, I think the arm64 builds is my next highest priority. The manual has been updated with the new instructions for the GUI app, and the homepage has a new "Download" link. |
Beta Was this translation helpful? Give feedback.
-
|
Very cool! It never occurred to me to wonder why jDeploy didn’t use jDeploy. :-)
I’ll start looking into adding template support to SnapCode. Being able to quickly share a project is the holy grail, though I have to admit I don’t even have support in SnapCode to build a stand-alone jar (though it’s been on my mind and shouldn’t be hard).
I gave the new app a try, but hit a little npm issue. It asked for my npm credentials and I think I goofed it up (it said it published to npm, but I don’t think it did since I got no email confirmation). Then I tried to turn off npm publishing, but it kept trying the npm step. My command-line workflow still works fine.
jeff
… On Mar 16, 2025, at 1:53 PM, Steve Hannah ***@***.***> wrote:
Today, I released the new jDeploy desktop app which aims to make it easier for new users to get started. It is deployed using jDeploy as a desktop app. No longer requires any dependencies (like npm). It provides gui options for creating new projects from templates ***@***.*** <https://github.com/reportmill>, it would be cool to add a project template for snapcode based projects), and configuring existing projects to us jDeploy.
It supports publishing to both npm and GitHub directly in the app (GitHub used to only work using github actions - now it works in app by pressing "Publish"). It also fixes up the authentication workflow for npm and GitHub with support for 2FA.
I'll be writing a blog post about this to announce it, but thought I'd drop it here as a glimpse of what I've been working on lately.
Now that this is out the door, I think the arm64 builds is my next highest priority.
The manual <https://www.jdeploy.com/docs/manual/>has been updated with the new instructions for the GUI app, and the homepage <https://www.jdeploy.com/>has a new "Download <https://github.com/shannah/jdeploy-desktop-gui/releases/tag/master>" link.
—
Reply to this email directly, view it on GitHub <#123 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJ7YSSKA2KA7EMHTIQZLHL2UXCDNAVCNFSM6AAAAABT4VAF66VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENJRG43DMNI>.
You are receiving this because you were mentioned.
|
Beta Was this translation helpful? Give feedback.
-
|
Hmm. Can you post a screen shot of the publish dialog when it says that it published to npm? |
Beta Was this translation helpful? Give feedback.
-
|
Wait. I think I see what happened. I was using an AI tool to help merge some of my new documentation into the manual, and it looks like it goofed some stuff up. It completely stripped out the section on setting up the npm token. I have reverted the change, and manually merged in the new "Getting Started" documentation. The Gist: Via the GUI you need to use a token for NPM publishing. You don't use your password. I really tried to get it working with the password, but they don't offer an API for this, nor do they encourage it, so all of my attempts were flakey. The token approach is stable and supported. Just requires that first step of generating a token one time. You can see the instructions for setting up the token here: https://www.jdeploy.com/docs/manual/#_generating_an_npm_token |
Beta Was this translation helpful? Give feedback.
-
|
Below is what it says (I tried again this morning, and entered a proper npm token). I also tried to turn off the npm switch, but it seems to have no effect (even if I quit and restart the app after turning the switch off). Using command [/Users/jeff/.jdeploy/node/v23.1.0/bin/npm, publish] |
Beta Was this translation helpful? Give feedback.
-
|
Does it say anything in your |
Beta Was this translation helpful? Give feedback.
-
|
There is no |
Beta Was this translation helpful? Give feedback.
-
|
Okay, I'll file this under "I don't understand how it ever worked at all". In any case, I have fixed it. If you open it and try to publish again, it should work, as it will download the latest fixes automatically. |
Beta Was this translation helpful? Give feedback.
-
|
One other note. You'll probably need to first delete the |
Beta Was this translation helpful? Give feedback.
-
|
Very nice - works perfectly for me now!
Just for fun, I tried to turn off the “npm” switch but it still does the npm publish (which doesn’t effect me because I think I want to keep doing npm for now).
Thanks again!
jeff
… On Mar 22, 2025, at 10:26 PM, Steve Hannah ***@***.***> wrote:
Okay, I'll file this under "I don't understand how it ever worked at all".
Just bought a new Mac, and was able to reproduce your issue first time, @reportmill <https://github.com/reportmill> . Probably it worked for me in testing because I had node installed on the machine, whereas with the jdeploy desktop, it bundles its own node, so you shouldn't need it installed.
In any case, I have fixed it. If you open it and try to publish again, it should work, as it will download the latest fixes automatically.
—
Reply to this email directly, view it on GitHub <#123 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJ7YSRTB25SEVPXB3X7WBD2VYSXBAVCNFSM6AAAAABT4VAF66VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENJZGAZTAOI>.
You are receiving this because you were mentioned.
|
Beta Was this translation helpful? Give feedback.
-
|
Note: v5.0 now includes support for Arm64 builds on Windows and linux. https://www.jdeploy.com/docs/releases/5.0/release-notes.html |
Beta Was this translation helpful? Give feedback.
Note: v5.0 now includes support for Arm64 builds on Windows and linux.
https://www.jdeploy.com/docs/releases/5.0/release-notes.html