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.

Sign up for GitHub

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

Jump to bottom

Add .cargo/config.toml to spacetime init Rust project with default target #1730

Open
jdetter opened this issue Sep 23, 2024 · 2 comments · May be fixed by #2328
Open

Add .cargo/config.toml to spacetime init Rust project with default target #1730

jdetter opened this issue Sep 23, 2024 · 2 comments · May be fixed by #2328
Assignees
@mamcx

Comments

@jdetter
Copy link
Collaborator

jdetter commented Sep 23, 2024

Re: #185 Users are confused by cargo build attempting to compile modules for their default native target and failing to statically link against the non-existent bindings-sys host functions. We should set Cargo’s default target to wasm32-unknown-unknown, so that cargo build works.

[build]
target = "wasm32-unknown-unknown"
@bfops
Copy link
Collaborator

bfops commented Nov 20, 2024

P2 since this only happens with (light) user error of running cargo build instead of spacetime build

@bfops
Copy link
Collaborator

bfops commented Nov 20, 2024

@gefjon points out that this might affect rust-analyzer (e.g. within vscode)

@mamcx mamcx self-assigned this Feb 28, 2025
@mamcx mamcx linked a pull request Feb 28, 2025 that will close this issue
Open
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mamcx mamcx

Labels
None yet
Projects
None yet
Milestone
No milestone
3 participants
@bfops @mamcx @jdetter