Couple questions about building final app

[adamk33n3r]

I noticed that the first time I ran fyne package --release it took multiple minutes to finish. But then after that it was fast. Is this expected behavior? If so, is there any way to speed it up? Reason I ask is because I'm building my app in a GitHub Action and it takes a very long time every time. I'm guessing on a local machine whatever it takes a long time doing is cached thereafter?

Second, can you build an "installer" executable that behaves like fyne install does? I would like to both distribute a portable exe and an installer if possible. I'm not sure if that's what fyne release does, but I don't have a certificate and I'm not currently planning on deploying to a store.

What is the difference between fyne build and fyne package? Just the adding of metadata and icons?

[andydotxyz]

I'm guessing on a local machine whatever it takes a long time doing is cached thereafter?

Correct. The cache makes it fast. You can work through setting it up properly on Github, or use a Fyne optimised solution like https://fynelabs.com/geoffrey/

Second, can you build an "installer" executable that behaves like fyne install does?

All that Fyne install does is copy the app into the appropriate folder. Though I guess on Windows it adds a start menu item too. In general Fyne apps should not need installers because they are relocatable so simply copying is all you need.

I'm not sure if that's what fyne release does

Fyne release is for preparing apps for store distribution.

What is the difference between fyne build and fyne package? Just the adding of metadata and icons?

Yes

[adamk33n3r]

Thank you for the responses!

You can work through setting it up properly on Github

I'm guessing I would use something like https://github.com/actions/cache, what paths would I need to include?

EDIT: after doing some more research, it looks like setup-go should already be caching https://github.com/actions/setup-go#caching-dependency-files-and-build-outputs 🤔

[adamk33n3r]

It's still not caching even after a couple builds so idk why setup-go says it does. Maybe only for same commits? Anyway, can you explain how to set it up properly?