... | ... | @@ -6,11 +6,11 @@ Build instructions can be found on [javascript-backend/building](https://gitlab. |
|
|
|
|
|
A demo that compiles and runs `Hello World` can be found [here](https://gitlab.haskell.org/ghc/ghc/-/wikis/javascript-backend/building#compiling-hello-world).
|
|
|
|
|
|
A breakdown of build artifacts a JavaScript cross-compiling GHC produces can be found [here](https://gitlab.haskell.org/ghc/ghc/-/wikis/javascript-backend/building#compiler-output-and-build-artifacts)
|
|
|
A breakdown of build artifacts a JavaScript cross-compiling GHC produces can be found [here](https://gitlab.haskell.org/ghc/ghc/-/wikis/javascript-backend/building#compiler-output-and-build-artifacts).
|
|
|
|
|
|
## Libraries
|
|
|
|
|
|
The status of support for the JavaScript backend in various libraries can be found at [javascript-backend/ecosystem](https://gitlab.haskell.org/ghc/ghc/-/wikis/State-of-the-JavaScript-Ecosystem)
|
|
|
The status of support for the JavaScript backend in various libraries can be found at [javascript-backend/ecosystem](https://gitlab.haskell.org/ghc/ghc/-/wikis/State-of-the-JavaScript-Ecosystem).
|
|
|
|
|
|
## Roadmap
|
|
|
|
... | ... | @@ -112,7 +112,6 @@ Yes. In the longer term, it would probably be better for the external interprete |
|
|
|
|
|
Note that Cabal currently doesn't support cross-compilation. It would be good to make it support two toolchains: one for the host (plugins, Setup.hs), one for the target. It would also need to use the correct platform to resolve conditionals in `.cabal` files.
|
|
|
|
|
|
|
|
|
## References
|
|
|
|
|
|
- Haskell Symposium 2013 paper: [demo proposal](https://www.haskell.org/haskell-symposium/2013/ghcjs.pdf)
|
... | ... | |