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

Check for the wasm32-unknown-unknown target #181

Merged
merged 3 commits into from
Jul 5, 2024
Merged

Check for the wasm32-unknown-unknown target #181

merged 3 commits into from
Jul 5, 2024

Conversation

lassemoldrup
Copy link
Contributor

Purpose

Closes #126.

Changes

Tries to use rustup to check for the target. Falls back to looking for the target's directory: https://users.rust-lang.org/t/determining-installed-target-list-when-rustup-is-not-in-use/100594

Checklist

  • My code follows the style of this project.
  • The code compiles without warnings.
  • I have performed a self-review of the changes.
  • I have documented my code, in particular the intent of the
    hard-to-understand areas.
  • (If necessary) I have updated the CHANGELOG.

@lassemoldrup lassemoldrup requested a review from DOBEN July 5, 2024 12:58
@lassemoldrup lassemoldrup merged commit 0f38608 into main Jul 5, 2024
4 checks passed
@lassemoldrup lassemoldrup deleted the check-wasm-target branch July 5, 2024 13:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@limemloh limemloh limemloh approved these changes

@DOBEN DOBEN Awaiting requested review from DOBEN

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Cargo-concordium should check if wasm32 is installed
2 participants
@lassemoldrup @limemloh