I don't have the time to check in detail what's going on, but given that rustc didn't have a platform tool chain for M1 Macs then, I would assume that winit did

I don't have the time to check in detail what's going on, but given that rustc didn't have a platform tool chain for M1 Macs then, I would assume that winit didn't support it correctly back then either. I pulled the repo and, on an Intel Mac, as-is it didn't work due to some coreaudio issue. After running cargo update, it successfully built (but failed to run due to an assertion failure, which I assume wasn't present in debug builds when this was written). Edit: the reddit conversation at https://www.reddit.com/r/programming/comments/1ehif46/i_cant_run_my_rust_game_either/ https://www.reddit.com/r/programming/comments/1ehif46/i_cant... confirms what I suspected: Mac changed its API on the platform transition, so the binding had to follow through, but that was after that winit library version was released.