-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Prebuilt binaries for Electron (0.26+) #2440
Comments
Hi, separate prebuilds are no longer required for Electron as all binaries support N-API version 3. https://nodejs.org/api/n-api.html#n_api_n_api_version_matrix |
@lovell thanks, as always, for your work on sharp! I've had to pin to Electron v9.3 and sharp v0.23.4 to support Ubuntu 18.04.5 LTS. (In other words, prior code and config does work, but electron v10 + sharp v0.26 + ubuntu 18.04 fails due to #2058).
If there's a known-working happy path per OS, I'm happy to do whatever it takes to make each platform work individually. Thanks again. I'd be happy to write up whatever turns out to be the magick recipes into a docs pull request. |
@mceachen I think the problem you're facing is because Electron depends on Chromium, which on Linux depends on GTK that depends on libcairo. The prebuilt binaries currently provided by Electron for Linux depend on the system GTK and therefore the system libcairo. There's some discussion about migrating Chromium in Electron from GTK to Aura at electron/electron#10915 |
Hi @lovell, thanks for your answer. I think my issue is related to #1697 (comment). electron-builder tries to find prebuilt binaries and fails. So that's not an issue with sharp. |
My best guess would be that |
Downstream issue for this at electron-userland/electron-builder#5438 |
Thanks for your awesome work on sharp. It sounds like there isn't electron prebuilt binaries since the release of 0.26.
The latest prebuilt binary was on https://github.com/lovell/sharp/releases/tag/v0.25.4.
Is it intentional or is it an issue with CI?
The text was updated successfully, but these errors were encountered: