You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 on windows.
My workaround is to build with cargo, copy the files to the default debug/release target and then execute crank run. For example:
cargo build --target x86_64-pc-windows-msvc
cp -fo .\target\x86_64-pc-windows-msvc\debug\* .\target\debug\
crank run
This works but it would be nice for crank to just work.
I would also be down to implement this but I've had some trouble finding a simple way to determine the output folder or all the sources we'd need to check to determine it. Any guidance on that and I think this would be a pretty simple patch.
The text was updated successfully, but these errors were encountered:
I've did it in other project cargo-playdate. I agree that there's no simple way to determine rustc-target, as well as cargo-target, so I'm using underlying cargo there.
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 on windows.
My workaround is to build with cargo, copy the files to the default debug/release target and then execute
crank run
. For example:This works but it would be nice for crank to just work.
I would also be down to implement this but I've had some trouble finding a simple way to determine the output folder or all the sources we'd need to check to determine it. Any guidance on that and I think this would be a pretty simple patch.
The text was updated successfully, but these errors were encountered: