-
-
Notifications
You must be signed in to change notification settings - Fork 401
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error while rebuilding for arm #1140
Comments
This is not an error but a warning that no prebuild was found. You should still be able to compile locally. @m4heshd any idea why there is no linux arm prebuild for v119? Looking at the assets https://github.com/WiseLibs/better-sqlite3/releases/tag/v9.4.0 I'm confused why for some versions they are missing? E.g. v115 and v120 have linux arm builds, but not v119 |
@Prinzhorn Thanks for helping! I'm sorry if this is trivial, but I've never done it before. I just need to download the corresponding package version for my architecture at https://github.com/WiseLibs/better-sqlite3/releases/tag/v9.4.0? After that, how do I compile locally? |
@VitorAndrey this all happens automatically when prebuild fails, but you've seem to have that disabled
|
Module version Now that arm is sort of becoming major on desktop, practically we should build for Electron on arm but the current method we're using to build for arm is notoriously slow. Qemu has a reputation for being just that. BS3's build workflow would take days to finish if we were to do that. I recently added a feature to BS3 for building UPDATE: |
@Prinzhorn, @m4heshd, thank you so much for your time and assistance. It turns out that using Electron Rebuild worked. I ran |
Hello! Thnx for your time in advance.
I am trying to use better-sqlite3 in my electron aplication wich is supposed to run in raspberry pi 3 so arch amrv7l. I tested in windows at first and it worked perfectly, got this error while rebuilding for this new platform.
What I already tried: setting the LIZ_COMPAT=1 env variable as I found in old issues.
The text was updated successfully, but these errors were encountered: