-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Windows error at runtime : "No native build was found" #4370
Comments
Looks similar to #4389 |
Can u solve this problem ? @taratatach |
I haven't found the time to work on this so no solution yet. |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
I missed the bot notification. Can we reopen this? |
Coming across this issue now in our app, seems to be related to |
Adds 194kb (or 406kb unpacked) to our npm package size. Previously removed because only 2% of installs were on 32-bit Windows and we agreed those users could compile from source. However, there is currently a gap in electron(-builder) tooling when used on native addons that use node-gyp-build: these addons don't get automatically recompiled. Though we don't need that anymore for runtimes (the builds are compatible with both node and electron) our users do need it when targeting multiple CPU architectures. Ref digidem/mapeo-desktop#305 Ref electron-userland/electron-builder#4370 Ref #554
Released |
cc @taratatach |
@okdistribute thanks for the catch and the notification! |
I'm packaging a Windows 32bit (as well as x64) application from an x64 AppVeyor VM with Node x64.
My app has a dependency on leveldown v5.0.2 which does not provide 32bit prebuilt binaries anymore.
As can be seen in the following logs, electron-rebuild seems to succeed at compiling it itself:
However, when the app is launched on a x86 Windows, it fails with the following error:
This seems to happen when we load leveldown.
I couldn't find any solution to this problem and figured this could be a configuration problem when running electron-builder for another architecture.
The text was updated successfully, but these errors were encountered: