Using buildmode exe directly is faster to build, avoids the runMain
linker mode hack, and leaves more control to Gio instead of gogio's
synthetic main function.
Signed-off-by: Elias Naur <mail@eliasnaur.com>
As suggested in review, explicitly specifying the version code with
-version major.minor.patch.versioncode provides more flexibility than
the a version code implied from the major, minor, patch fields.
Signed-off-by: Elias Naur <mail@eliasnaur.com>
Since Go 1.20 c-shared object files may lack a reference to the resolv
library and it must be added manually to the linking step.
Signed-off-by: Elias Naur <mail@eliasnaur.com>
Go 1.16 is already old, and the GOOS detection code fails for me on
Nix:
$ go run gioui.org/cmd/gogio -target ios ../gio-example/kitchen
gogio: go tool dist list failed: go tool dist: FAILED: not a Git repo; must put a VERSION file in $GOROOT
The error message points to a Nix packaging issue, but removing the
fallback is easier to fix.
Signed-off-by: Elias Naur <mail@eliasnaur.com>
Now, it's possible to notarize the app, using -notaryid,
-notarypass and -notaryteamid flags. Those flags are
similar to -signkey and -signpass.
Signed-off-by: inkeliz <inkeliz@inkeliz.com>
Previously, gogio creates the `.app` and then generates
the signature.
Now, it will generate the `.app` on the temporary folder,
then move it. It also generates one `.zip` folder, which
will be used in the next patch.
Signed-off-by: inkeliz <inkeliz@inkeliz.com>
Builds.sr.ht is having problems with the debian/testing image because it is
switching which concrete debian release it points at. In the meantime, we can
use use the same release as before by a concrete name.
Signed-off-by: Chris Waldon <christopher.waldon.dev@gmail.com>
Build arguments are passed to the program, which is useful for
platforms where there is no other way to pas them (Android, iOS).
Signed-off-by: Elias Naur <mail@eliasnaur.com>
This commit adds an end to end test for the custom rendering
use-case. I confirmed that the new test failed when custom
rendering frame lifecycle was broken, and succeeds now.
However, the old X11 tests started failing when the new
one started passing. I'm not sure how they interfere with
one another, but I'm out of time to investigate.
Signed-off-by: Chris Waldon <christopher.waldon.dev@gmail.com>
Previously, it was possible to misuse gigio with arguments after the
package, such as `gogio -target android . -o foo.apk`. That cause an
undesired effect, since `-o` is silently ignore by gogio.
Now, any arguments after the package will trigger an error.
Signed-off-by: Inkeliz <inkeliz@inkeliz.com>
Elias Naur