4 ms·
I don't know a whole lot about Electron and friends, but saw this project the other day that does new builds with a Github action: https://github.com/davidaf3/c
by n1c 5y ago
I don't know a whole lot about Electron and friends, but saw this project the other day that does new builds with a Github action: https://github.com/davidaf3/csgo-tracker/blob/master/.github/workflows/csgo-tracker.yml#L8 https://github.com/davidaf3/csgo-tracker/blob/master/.github... maybe it'd be useful to look at?
- jarek-foksa 5y agoThanks, I will check it out. I didn't know GitHub Actions could be configured to run on proprietary operating systems.
- davidaf3 5y agoHi, I'm the author of the repo. I use electron-builder [0] to build my Electron app. IIRC there are a few CLI flags to build for different operating systems without needing to run it in the target OS. So you don't even need to use GitHub Actions. [0] https://www.electron.build/ https://www.electron.build/
- jarek-foksa 5y agoI'm using electron-builder too. Things get more complicated when you want to publish your app on different app stores. I was unable to build a Snap Store package for arm on an amd64 machine. Canonical provides their own remote build service, but proprietary projects can't use it yet. In order to build a package for distribution on the Mac App Store I have to use macOS with XCode installed and signing certificates stored in the system keychain. Uploading the package to the app store also must be done with macOS-specific tools. At least it is possible to build multi-arch packages, so I don't need two separate machines as it is the case with snaps. Windows 10 with Windows SDK is required to build an appx package for distribution on the Microsoft Store.