-
Notifications
You must be signed in to change notification settings - Fork 51
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
Add js-cross devShell #176
Conversation
This merely injects `--host` and `--target` flags into the recommended `configure` arguments.
As suggested by @doyougnu on alpmestan#169.
cross compiler smoke test: | ||
runs-on: ubuntu-latest | ||
|
||
steps: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If there's some way to not duplicate the setup steps between jobs, I'm all ears.
Hopefully I fixed the job failure :) |
Sigh... once more |
(But which is it? I've been calling it the "wasm backend", not the "wasi backend") |
Neatly sidestepping the question of *which* example to provide.
Sorry, yes, that was a poor choice of name on my part. I think "wasm backend" is indeed more accurate. Feel free to rename it. |
@bgamari hehe ok. But not in this PR I think, since it doesn't include any changes to the wasm/wasi side. I think this particular PR is good to go now. |
Hello, is this PR stuck on something? What can be done to move this forward? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I built a JS backend with this (given that I didn't overlook some change) and the documentation updates look good to me.
A continuation of #169.
I tried to add some CI, but I haven't messed with GitHub Actions much yet. Let's see how it goes.