Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better support for cross-compilation when neccesary #56

Open
Clockwork757 opened this issue Dec 24, 2023 · 1 comment
Open

Better support for cross-compilation when neccesary #56

Clockwork757 opened this issue Dec 24, 2023 · 1 comment

Comments

@Clockwork757
Copy link

Clockwork757 commented Dec 24, 2023

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.

@boozook
Copy link
Member

boozook commented Apr 15, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants