-
Notifications
You must be signed in to change notification settings - Fork 240
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
GHC 9.6, Wasm, and GHCJS #2024
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Bump. Any imminent plans for this? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This will likely happen once we e fixed all the windows issues and are able to update nixpkgs pins again. Nixpkgs update to binutils 2.36+ (and now the inability to still use 2.35 trivially) has thrown in a pretty bad wrench 😒 (Same with adding the riscv backend). |
We're using https://gitlab.haskell.org/ghc/ghc-wasm-meta/ to build our Wasm targets for now. It's nice that it provides a flake for the compiler and tools, but obviously we'd like to take advantage of the haskell.nix ecosystem, as well. |
Any plans to implement this once #2156 is merged? |
Hi. I just stumbled upon this now. It seems that the PR above has been merged. I'm also targeting WASM and would like support for it :) |
Hi! We've just about managed to get our
haskell.nix
project building with GHC 9.6.2, and now we'd like to build a Wasm target, or at least GHCJS.From what I can tell, there's no support for cross-compiling to the 9.6
wasm32-wasi
"triple." Is there a plan for that?And for GHCJS, does one use the documented
p.projectCross.ghcjs.hsPkgs
magic and it will do the right thing with GHC 9.6.2, or does the existingprojectCross
GHCJS support only work with the old standalone GHCJS compilers?The text was updated successfully, but these errors were encountered: