electron-builder: Linux build fails at icon conversion
Building a deb with the latest release (2.9.5) I get the following error:
Unhandled rejection Error: Command failed: gm convert: Unable to open file (/tmp/electron-builder-30935NzzLT2KzUll7/icon_128x128x32.png) [No such file or directory].
I have provided a build/icon.icns file (generated using these steps: http://blog.macsales.com/28492-create-your-own-custom-icons-in-10-7-5-or-later). When I look what’s in the /tmp/electron-builder-30935NzzLT2KzUll7/ folder, I see that it created the following icons:
icon_16x16x32.png
icon_256x256x32.png
icon_32x32x32.png
icon_512x512x32.png
Looks like 64 and 128 is missing.
I am building the linux deb from an Ubuntu 15.10 machine.
Any ideas what’s going on? Alternatively, could I just provide the icons “manually” (I already have all those pngs anyways)?
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 50 (22 by maintainers)
Commits related to this issue
- fix: Linux build fails at icon conversion #239 Closes #239 — committed to develar/electron-builder by develar 8 years ago
- Merge pull request #241 from develar/239 fix: Linux build fails at icon conversion #239 — committed to electron-userland/electron-builder by develar 8 years ago
- fix: Linux build fails at icon conversion #239 Closes #239 — committed to develar/electron-builder by develar 8 years ago
AppImagetarget will be set as a default target Linux soon (once all known AppImage issues will be solved) — I decided to to bump major version to 6 and don’t wait NSIS auto-update feature. Because AppImage is better than deb and electron-builder should promote it.@JimiC develar had an example where he named the
pngfiles inbuild/iconsfolder to beAnd it worked for me after trying that, if you’re just trying to get something up and running. Of course you can always just specify an
icon.icnsfile in yourbuild.osxoptions, which should be located in thebuildfolder, and the linux build will pick it up.It is DMG icon “which will be shown when mounted”. Yeah, it is not user-friendly and confusing.
Thanks. And to clarify, what I had trouble with was the Linux build not picking up the icon path from the osx build options. And also, the Linux build would only work if my icon file was called
build/icon.icns