You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a simple package.json with multiple targets (win, mac, linux).
It looks like the build.mac.icon+.icns rule have priority over the build.linux.icon one, which is - to say the least - surprising.
But when I run the linux build, it tries to look for the mac icns icon!
stat /home/marss/nidar-electron/build/icon.512x512.png.icns: no such file or directory
And I see no reason to be using icns format - my mac build works very well with the png.
But!
If I remove the mac build config instead the linux build works fine.
Also, if I use icon.512x512.png instead in linux.icon it works!
I've found several other icon-related issues for the repo but none really addresses this specific point, though this ones is very related: #1399 (comment)
(Very sorry I hadn't realized npm would not upgrade to the 20.x version without explicitly modifying the package.json version condition from the ^19 - i was convinced I was running the latest, but obviously I wasn't! )
I have a simple package.json with multiple targets (win, mac, linux).
It looks like the
build.mac.icon
+.icns
rule have priority over thebuild.linux.icon
one, which is - to say the least - surprising.But when I run the linux build, it tries to look for the mac icns icon!
stat /home/marss/nidar-electron/build/icon.512x512.png.icns: no such file or directory
And I see no reason to be using
icns
format - my mac build works very well with the png.But!
If I remove the
mac
build config instead thelinux
build works fine.Also, if I use
icon.512x512.png
instead inlinux.icon
it works!I've found several other icon-related issues for the repo but none really addresses this specific point, though this ones is very related: #1399 (comment)
and the doc https://www.electron.build/icons does not explicitly list these small inconsistencies.
Even if you don't think it's worth changing the doc or the behaviour, I hope this issue description might help somebody troubleshooting!
thanks
Stefano
The text was updated successfully, but these errors were encountered: