libheif VS electron-builder

Apple doesn't own HEIF, there are open implementations for reading all variants of it. Here's a browser-side implementation: https://alexcorvi.github.io/heic2any/

The image crate is the de facto crate for raster images. It doesn't have HEIF support, which is probably why libheif-rs was brought in (it's simply a wrapper for libheif, which is what lots of programs, including GIMP and ImageMagick, use for HEIF support).

Libheif has Go bindings https://github.com/strukturag/libheif/tree/master/go/heif. I used this library for AVIF (via libaom) but it should work for HEIF (via libde265.)

libheif provides a pixbuf loader that should make it work.

Note that there is no checking for valid parameters when using the prefix. BUGS Please reports bugs or issues at https://github.com/strukturag/libheif AUTHORS Dirk Farin, struktur AG COPYRIGHT Copyright © 2017 struktur AG

They use https://github.com/strukturag/libheif to decode it and just ignore the patent or licensing requirements. This is similar to how vlc's libavcodec implements HEVC/h264 (they say "we're french, software patents have no jurisdiction here")

As far as I understand, imagemagick uses libheif under the hood, which can be installed with apt install libheif-dev

The last step for each platform's build process is to upload the app to our GitHub releases repository. We automated this step from the beginning, but when we started creating builds for the new M1 chip Macs, we had to add a manual step. This involved merging files needed for the auto-updater to work with the M1 builds.

https://github.com/electron-userland/electron-builder/issues... that issue kinks to the PR that adds the automation.

It's a non-trivial thing to test, since it involves so many secrets and the notarization step can take over an hour, so I don't expect anyone here to actually want to look into it.

My original comment really was just venting my frustration, not a cry for help (but I might be crying soon if I can get to the bottom of this!).

> The ‘autoupdater’ does three things,

>

> - check the app for updates (using Sparkle)

> - report any crashes (using Sentry)

> - start a local HTTP proxy on port 40701 (this can be changed using the configuration json file in the app bundle).

>

> The latter is of course, not to be expected of any app on the machine, especially not one that just claims to be an auto updater.

Well, yes. And no.

For example, electron-builder [^0], a popular framework used for Electron app packaging and auto-updates, uses a local update server on Mac [^1] to add a more sane system backed by a more insane system, Squirrel.

[^0]: https://github.com/electron-userland/electron-builder

[^1]: https://github.com/electron-userland/electron-builder/blob/m...

The Project uses Electorn-Builder to package the app and Electorn-Updater to update.

You can read about this issue here: https://github.com/electron-userland/electron-builder/issues/7114

Ostara is based off of electron-react-boilerplate and uses electron-builder to package the application.

Install electron and electron-builder

I believe Visual Studio Code uses Electron and posts releases on a regular basis. Maybe check their A quick Google search for "electron build github release" turns up "Electron Builder" https://www.electron.build/ I don't really know though; I've never used Electron.

I also would like to have an NSIS installer so if it happens to package the Chromium executable along with my app, how can I accomplish that? I am using electron-builder.

We use electron-builder at work.