crank
crank copied to clipboard
pd-rs
A wrapper for cargo to use creating games for the Playdate handheld gaming system.
Adding +nightly to simulator builds seems to fix [pd-rs/crank/issues/57 ](https://github.com/pd-rs/crank/issues/57 )
When providing the `--device` flag, `+nightly` is added to `cargo build`: https://github.com/pd-rs/crank/blob/f46cda4a2dd028d5580d89268975fcb21f6f0eb5/src/main.rs#L611-L615 and I run into the following error: ``` INFO crank > build command: RUSTFLAGS="-Ctarget-cpu=cortex-m7 -Clink-args=--emit-relocs -Crelocation-model=pic -Cpanic=abort" "cargo"...
Crank doesn't recognize when cargo compiles to a target that doesn't match the host system. This is necessary on arm64 windows since the playdate simulator is only built for amd64...
tl; dr It seems possible to use dynamically linked libraries with the simulator but I can't figure out how to modify the search paths. Hopefully this is doable on device...
I'm getting failing simulator builds of the [crankstart](https://github.com/pd-rs/crankstart) examples. The device builds (eg `--device`) are fine. I'm new to both playdate & rust so bare with me. I've followed the...
Instead of ``` Error: No such file or directory (os error 2) ``` do ``` Error: copying from "one/path" to "another/path" Caused by: No such file or directory (os error...
As discovered in https://github.com/pd-rs/crankstart/issues/41#issuecomment-1763542159. This happens in at least 2 cases that I'm aware of: 1. `PLAYDATE_SERIAL_DEVICE` isn't set and the hard-coded value is used. 2. The device is locked.
The Playdate has a small stack. Is it feasible to bake flip link into `crank` for "stack overflow protection"? https://github.com/knurling-rs/flip-link The main problem appears to be "if you [are] using...
This line is hardcoded for a specific playdate number so it won't work unless you're lucky enough to have that exact playdate.: https://github.com/pd-rs/crank/blob/6ac43230b11c3e5c431fd163faf708674637647c/src/main.rs#L370
