Tobias Mock

Thanks for keeping up on this. I agree that those interactions are not obvious and are best handled in the bindings (somehow). For the first issue, we can probably wrap...

As reported on issue #39, building is possible in general. I'll repurpose this ticket to add a m1 build to the ci

With gcc14, `-Wincompatible-pointer-types` is now an error instead of a warning, see https://gcc.gnu.org/gcc-14/porting_to.html#warnings-as-errors.

Curious, the opam file in this repo and in the opam repo indeed differ by two version constraints. ``` @@ -11,13 +11,13 @@ ] depends: [ "bigarray-compat" - "ctypes" {>=...

This is something I'd love to add to these bindings, but right now it's not feasible in my understanding. Support for wasm in OCaml is still a work-in-progress, [see here](https://discuss.ocaml.org/t/an-update-from-the-ocaml-wasm-organization/13114)....

It's even worse than you say, a null byte is added on each frame and the string length grows and grows. Ouch! The doc comments were copied from raylib, which...

The fix is on master now. I'll leave the issue open until I pushed a new release to the opam repo

Does anyone understand what went wrong on the cygwin build? The msys2 build was failing in the last version already (and we decided to not bother at the moment)

Thanks for digging a bit deeper on this. I don't have a windows machine (nor access to one atm) so I can only guess. The opam package you linked splits...

> I'm still puzzled that `conf-libffi` and `conf-mingw-w64-libffi-x86_64` is not installing `mingw64-x86_64-libffi`. Yes, same here. The CI logs even mention extracting the package ` - Extracting from file://D:\opamroot\.cygwin\cache/https%3a%2f%2fcygwin.mirror.constant.com%2f/noarch/release/mingw64-x86_64-libffi/mingw64-x86_64-libffi-3.2.1-2.tar.xz`