-
Notifications
You must be signed in to change notification settings - Fork 99
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
Rename OS target wasi to wasip1 #747
Comments
michaliskambi
added a commit
to michaliskambi/fpcupdeluxe
that referenced
this issue
Mar 3, 2025
I was impatient, so I made a PR to do this rename: #748 . Note that the PR can be probably simplified in 2 places if you want to rename (and change layout inside) the cross-libs on the server. I hope this is helpful :) |
michaliskambi
added a commit
to castle-engine/cge-www
that referenced
this issue
Mar 3, 2025
michaliskambi
added a commit
to castle-engine/castle-engine
that referenced
this issue
Mar 3, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The OS name for the FPC+WebAssembly target has changed, from
wasi
towasip1
. As a consequence, currently building FPC trunk withOS_TARGET=wasi
(using fpcupdeluxe) fails, with the errorThe Makefile doesn't support target wasm32-wasi, please run fpcmake first. Stop.
So, fpcupdeluxe needs to also rename
wasi
->wasip1
.Background:
See https://gitlab.com/freepascal.org/fpc/source/-/commit/1f965d262dc09aa2de789e20fa23163280a5b9c7 and nearby commits performing the change in FPC sources.
Michael Van Canneyt also communicated to me this change over the weekend. In the future, we will have another target: WebAssembly 2.0, which will be called
wasip2
, so the rename of current target (which is WASI 1.0) fromwasi
->wasip1
is necessary to avoid future confusion.I note that this is consistent with Rust and Go ( https://doc.rust-lang.org/nightly/rustc/platform-support/wasm32-wasip1.html , https://go.dev/blog/wasi ), so we're in good company.
Michael Van Canneyt will announce this change soon on the mailing list(s). I wanted to also let you know. We need this fix in fpcupdeluxe soon, to reenable people to build FPC+WebAssembly with fpcupdeluxe. (Which is my recommended way to get FPC+WebAssembly for Castle Game Engine web target.)
The text was updated successfully, but these errors were encountered: