zemeroth VS osxcross

i've used both in zemeroth: i migrated it from ggez to macroquad mostly because ggez at that time didn't support android and web targets. but i'd say that the main difference is tech stacks they're using: while ggez extensively reuses the existing rust gamedev ecosystem (winit, wgpu, rodio, etc), mq was written mostly on top of minimalist or its own specialized libraries (see miniquad).

nope, /u/not-fl3 is the author. i'm just using it in my zemeroth.

Trying to get back to the development of my turn-based game Zemeroth: going to finish the first iteration of settings screen for configuring widgets' size and screen offset, and get back to writing devlogs for the v0.7 release.

Depends on CI system you prefer. Here's Zemeroth's Github Actions release config for example: https://github.com/ozkriff/zemeroth/blob/master/.github/workflows/release.yml

Tutorial is based on a public test of zemeroth game.

zemeroth: a 2D game with desktop versions, but also a wasm online version

Oh, I was really waiting for this episode as my Zemeroth game shares a lot of history with mini~ and macroquad. Here're some of my thoughts.

If you actually have MacOS device and can install Xcode and so on then you can proceed here and read the instructions.

Have you considered using a dockerized osxcross cross compiler toolchain in your CI? Granted it is a bit clunky to setup...

Technically it's possible, but possibly not legal:

https://github.com/tpoechtrager/osxcross

> Please ensure you have read and understood the Xcode license terms before continuing.

According to the EULA you may only use the SDK on Apple-branded computers. But you can use Linux to cross compile to Apple.

is there a way to cross compile without vms? something similar to https://github.com/tpoechtrager/osxcross?

If you figure out how to get SDL working, one possibility is to develop on Linux, then use mingw-w64 to cross compile from Linux to windows, then use osxcross to cross-compile from Windows to OSX.

Thank you osxcross for creating the path forward

This is actually a solved problem, using osxcross[0]. The experience is honestly very smooth, and we don't require any apple proprietary binaries. The only thing apple-proprietary is their SDK (containing the header files for compiling, and tbd files for linking), which can be downloaded from apple's website (at least if you have a developer account), or from various GitHub projects archiving them.

[0]: https://github.com/tpoechtrager/osxcross