YouTube video by NyasperoVT

YouTube video by NyasperoVT

The linker flags can be seen in the output of `cargo build --verbose`, which is: -L /Users/kevinstephen/projects/rswk/ksl_raylib/extern/raylib-5.5_macos/lib -L native=/usr/local/lib -l static=raylib -l framework=OpenGL -l framework=Cocoa -l framework=IOKit -l framework=CoreFoundation -l framework=CoreVideo Just in case, I'll also show the output using `RUSTFLAGS='--print link-args'`: output for cargo build It seems that for `cc`, the linker flags are these: "-lraylib" "-framework" "OpenGL" "-framework" "Cocoa" "-framework" "IOKit" "-framework" "CoreFoundation" "-framework" "CoreVideo"

I am happy that 33.7.0 is out and have built it on my Mac, as I have been doing since 2017. I did notice that videos were not playing, VIDEOJS libraries were reporting codec incompatibilities, because the underlying canPlayType returned the empty string. Others in the fora had also noticed this. I stepped through the code and it was apparently due to sub-frameworks moving out of the ApplicationSupport framework to top-level, like CoreGraphics and CoreVideo. Can be looked up here: https://developer.apple.com/library/arc ... works.html I also had to add my current SDK to the list of known SDKs. I had to comment out the malloc, calloc, realloc redefines as they ended up in C++ code and not compiling when the code called std::malloc etc. I have still one unsolved issue where I have a workaround: A synology box with a self signed certificate that has not been accepted before will end up in the TLS 1.3 protocol degrade path and end up with a cryptic SSL_ERROR_RX_MALFORMED_SERVER_HELLO error. This does not seem to affect mainstream browsers. Workaround is to disable SSL hello downgrade enforcement, accept the self signed cert, then reenable downgrade protection. I put my specific changes to the code at my fork here: https://github.com/stroucki/UXP * * *