Skip to content

Use WASI SDK 0.2.2-swiftwasm to fix setjmp headers in 5.3 branch #2127

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

Merged
merged 3 commits into from
Oct 29, 2020

Conversation

MaxDesiatov
Copy link

WASI SDK 0.2.2-swiftwasm is already used in the swiftwasm branch. This makes it easier for us to build OpenCombine and other C++ code when targeting WASI.

WASI SDK 0.2.2-swiftwasm is already used in the `swiftwasm` branch
@MaxDesiatov MaxDesiatov added continuous integration Improvements to continuous integration release Issues with the release version labels Oct 29, 2020
@MaxDesiatov MaxDesiatov marked this pull request as ready for review October 29, 2020 22:15
@kateinoigakukun kateinoigakukun merged commit 1536e19 into swiftwasm-release/5.3 Oct 29, 2020
@kateinoigakukun kateinoigakukun deleted the maxd/5.3-update-wasi-sdk branch October 30, 2020 00:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
continuous integration Improvements to continuous integration release Issues with the release version
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants