Rob Tsuk
Rob Tsuk
I can't reproduce this with Klondike on my M1 MacBook Air running 13.3.1 (22E261). What does `crank -V` tell you?
I was able to compile it and run it fine on the device. What does `rustc +nightly -V` say?
I was just going to ask that, but with `--device`.
It's working fine for me on almost exactly the same host hardware and rustc 1.71.0-nightly (458d4dae8 2023-04-25).
So, I went back and reread your initial message and see you're trying to use`Device > Upload`, which I've not tried in years and which shouldn't be necessary. `crank run`...
I also see that when you run, logging stops after ` INFO crank > run_target`. I get ~~~ INFO crank > datadisk cmd: Command { program: "/Users/rob/Developer/PlaydateSDK/bin/pdutil", args: [ "/Users/rob/Developer/PlaydateSDK/bin/pdutil",...
Also, `Device > Upload` works for me.
I'm not sure why there needs to be a main.pdz file. I don't have one and it works fine for me. ``` rob@RoboAir ~ % ls -l /Volumes/PLAYDATE/Games/Chip8\ Playdate.pdx total...
Make sure that macOS isn't asking for permissions while crank is running. I think I saw some of those while testing just now and it caused crank to hang.
That is certainly the cause. It works on the simulator because the simulator uses the dylib, not the binary.