osxcross VS zig

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

There is an issue proposing this approach: https://github.com/ziglang/zig/issues/4284

https://github.com/ziglang/zig/issues/224

e.g.:

> > When debugging/prototyping, it's useful to comment out a line without having to refactor, e.g.

When writing code in a scripting language, sometimes you need that extra bit of performance (or maybe an async feature from Zig).

NodeJS is by no means a slow runtime, it wouldn’t be so popular if it was. But compared to Bun, it’s slow. Bun was built from the ground up with speed in mind, using both JavascriptCore and Zig. The Bun team spent an enormous amount of time and energy trying to make Bun fast, including lots of profiling, benchmarking, and optimizations.

ntdll.dll!RtlUserThreadStart()

There are valid reasons to use APIs from NTDLL. Where I disagree with zig#1840 is the idea that it is always better to use NTDLL versions of API. Every other software ecosystem uses the standard Win32 APIs and diverging from that without a good reason seems like a good way to have unexpected behavior. One concrete example is most users and programmers expect Windows to redirect some file system paths when running on WOW64. But this is implemented in Kernel32, not ntdll.

https://github.com/ziglang/zig/issues/11894

Zig also has an IRC channel on libera (#zig) that is moderated by Andrew Kelley.[1]

[1] https://github.com/ziglang/zig/wiki/Community