-
Notifications
You must be signed in to change notification settings - Fork 15
ARM builds #142
Comments
Please respond. |
I apologize for the delay. This requires some changes because we package a few (2) precompiled binaries to be bundled with the application. I'll update the code to include arm binaries within a few days. |
Any updates on that @binarybaron? |
@binarybaron is this repo still active or did you abandon this project? |
This project has not been abandoned. We have been busy with other issues. I hope to get to this soon |
Any way I could help with this? This issue was opened nearly a year ago and I still cannot run this software on my Raspberry Pi, which is my primary desktop computer. :(
What were the binaries? |
This should be a fairly easy question to answer. I am interested in adding this to our ARM linux app store. To do that, this needs to be built to run on ARM64 and armhf linux. We already have numerous other electron apps with node on the store, so something like this is almost routine.
Your build system automates the process of building single binaries for linux, Windows, and MacOS. I have a Raspberry Pi to run a test build on, but it keeps building x86_64 binaries. Is there a way to change this behavior? These are the commands I have run:
All commands complete successfully on my Pi without modification. That last
npm run build
creates some binaries in the~/unstoppableswap-gui/build/bin
directory.For linux that results in this file:
~/unstoppableswap-gui/build/bin/swap/linux/swap
, which is a x86_64 binary.How can
npm run build
be changed to build an arm64 or armhf binary instead? I have tried running this command but it made no difference.The text was updated successfully, but these errors were encountered: