-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Build from source fails on ARM #818
Comments
ARM is unsupported. See #804 for somebody trying to make it work, but it's really hacky.
It is, something like
Nope. #769 |
So I used the right command line to build it? Would it be any different if I used v15 of Node.js (I dont think so)? If you point me to the right place(-ish) I can at least try some (non-hacky) patches, so (at least) this error will not occur, and then it can work on any architecture (including RISC-V & Power). I have built Electron apps on ARM before, they work fine. |
eDEX has some native dependencies written in C/C++, like node-pty... and others I think, I don't really remember as i haven't seriously worked on this repo for about a year now. You should look into arm support in those projects first. |
it appears v2.2.2 has some issues with headers. Am I right in understanding that EDIT: I just did a quick grep, and (in Should maybe I rather be using Starting from source instead, with:
|
Yup, from this line onwards: Line 45 in 459e50e
See also the scripts section in this same file.
Yes, that's what "building" means in the context of this repo, packaging dependencies, eDEX source code and assets and Electron white-label binaries into a single executable.
Normally you try starting it before bundling it (which what "build" really means here). If dependencies successfully installed, |
Bah, Starting from source instructions works fine! EDIT: re: edex-ui/package.json yeah there are
It seems like the Build will work too, but its late/early - I will try take it out or modify it tomorrow EDIT: could not wait (I set arch to
Close, but no cigar. Here it needs But I would say edex-ui does support ARM, it just doesn't know it yet (needs some config tweaks). ie forget the v2.2.2 patch effort, there does not seem a need when some minor changes for 3.0.0-pre will have it working out of the box. |
@parkerlreed cheers. I just edited that post again, and I think its even simpler than what you did. But I am starting to see a pattern here with EDIT: I just noticed I had this (2018) #313 post by @thallada (last post), open the whole time, but did not get around to reading it until just now (the original workaround is mentioned here ) . It mentions everything so far. And "hey presto", edex-ui 3.0.0-pre Master does actually in fact Build out of the box. Ho hum. recap: |
@parkerlreed That photo looks dope. Well done! |
A note in a file/readme would help out here I think, a RaspberryPi text specific or "ToubleShooting" text (either should be fine), or simply just mention it on the front page (README.md) - thanks for everyones help and screenshots btw. |
@marceltoma Can you post your build instructions or your working build as a release? |
Technical information
Using version:
master
(running from GitHub-published source code, currentlyv3.0.0-pre
)latest
(latest release, currentlyv2.2.2
)vX.X.X
(specify other version)Running on:
How comfortable you are with your system and/or IT in general:
Problem
I am on a RPi4 with RaspberryPiOS Buster (32bit). I tried Building from the README.md
Both the Master (GitHub Repo) and the v2.2.2 (.tgz) fail to build (with different errors).
I wont paste the .tgz build error, but it looked stupid. Lots of:
Building from the repo gets further, but it fails with the following error:
I dont know about you but:
• rebuilding native dependencies [email protected] platform=linux arch=x64
seems to me like it will always fail on ARM (actually anything NOT x64 - which is everything else)
This seems like it is not picking up a setting from somewhere, or making a presumption.
Presuming this is the only thing in the Master Repo that needs fixing, can another release be made asap
I installed Node.js (14.15.0) & NPM (6.14.8) using
curl -L https://git.io/n-install | bash
.Cheers
Paul
The text was updated successfully, but these errors were encountered: