Skip to content

Conversation

@tjammer
Copy link
Contributor

@tjammer tjammer commented Nov 30, 2025

CHANGES:

  • Expose name field of ModelAnimation.t (thanks @thethrung)
  • Add new raylib-callbacks package to expose raylib callback APIs. It brings a new dependency (ctype-foreign), hence the new package
  • Temporarily fix raylib FLAC bug (thanks @rossberg)

CHANGES:

* Expose `name` field of ModelAnimation.t (thanks @thethrung)
* Add new raylib-callbacks package to expose raylib callback APIs. It brings a
  new dependency (ctype-foreign), hence the new package
* Temporarily fix raylib FLAC bug (thanks @rossberg)
@tjammer
Copy link
Contributor Author

tjammer commented Nov 30, 2025

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)

@rossberg
Copy link
Contributor

rossberg commented Dec 1, 2025

When I tried this locally before, I had to manually install a libffi package for Cygwin. Not sure why, I would think that ctypes-foreign includes it as a dependency. Unfortunately, the CI log cuts the relevant lines, so this may or may not be the reason.

@jmid
Copy link
Member

jmid commented Dec 1, 2025

Does anyone understand what went wrong on the cygwin build?

Looking at the CI logs:

  <><> Processing actions <><><><><><><><><><><><><><><><><><><><><><><><><><><><>
  -> retrieved ctypes-foreign.0.24.0  (cached)
  -> retrieved mingw-w64-shims.0.2.0  (cached)
  -> removed   mingw-w64-shims.0.2.0
  -> installed conf-pkg-config.4
  -> retrieved raylib-callbacks.1.6.0  (cached)
  -> installed conf-mingw-w64-libffi-x86_64.1
  -> installed conf-libffi.2.0.0
  -> installed mingw-w64-shims.0.2.0
  -> installed ctypes-foreign.0.24.0
  [ERROR] The compilation of raylib-callbacks.1.6.0 failed at "dune build -p raylib-callbacks -j 3 @install".
  
  #=== ERROR while compiling raylib-callbacks.1.6.0 =============================#
  # context     2.5.0 | win32/x86_64 | ocaml.5.4.0 | file://D:/a/opam-repository/opam-repository
  # path        D:\opamroot\default\.opam-switch\build\raylib-callbacks.1.6.0
  # command     D:\opamroot\default\bin\dune.exe build -p raylib-callbacks -j 3 @install
  # exit-code   1
  # env-file    D:\opamroot\log\raylib-callbacks-5416-32703f.env
  # output-file D:\opamroot\log\raylib-callbacks-5416-32703f.out
  ### output ###
  # [...]
  # -> required by
  #    _build/install/default/lib/stublibs/dllraylib_callbacks_c_stubs.dll
  # -> required by _build/default/raylib-callbacks.install
  # -> required by alias install
  # (cd _build/default/src/c/raylib_callbacks && .\raylib__function_gen__Functions__Functions.exe ml raylib_stubs) > _build/default/src/c/raylib_callbacks/raylib__c_generated_functions__Functions__Functions.ml
  # Command exited with code 0xc0000135.
  # -> required by
  #    _build/default/src/c/raylib_callbacks/raylib__c_generated_functions__Functions__Functions.ml
  # -> required by
  #    _build/install/default/lib/raylib-callbacks/__private__/raylib_callbacks_c/raylib__c_generated_functions__Functions__Functions.ml
  # -> required by _build/default/raylib-callbacks.install
  # -> required by alias install

the successful install of conf-mingw-w64-libffi-x86_64.1 and conf-libffi.2.0.0 indicate that the problem is elsewhere.

Command exited with code 0xc0000135 which I (as a Windows illiterate) had to look up
https://stackoverflow.com/questions/11432940/what-does-error-code-0xc0000135-or-1073741515-exit-code-mean-when-starting-a
indicate that a relevant dll (perhaps dllraylib_callbacks_c_stubs.dll?) is not being found. 🤔

@rossberg
Copy link
Contributor

rossberg commented Dec 1, 2025

Code 0xc0000135 is exactly what I got locally before installing libffi manually, after that it worked. I have no theory as for why, maybe it is a different libffi package that's required? I installed all of libffi6, libffi8, mingw64-i686-libffi and mingw64-x86_64-libffi just to be sure.

@jmid
Copy link
Member

jmid commented Dec 2, 2025

To help understand what's going wrong you can

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants