Skip to content

Add emscripten support #19

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 1 commit into from
Jan 6, 2018
Merged

Add emscripten support #19

merged 1 commit into from
Jan 6, 2018

Conversation

malbarbo
Copy link
Contributor

@malbarbo malbarbo commented Jun 7, 2017

No description provided.

@malbarbo
Copy link
Contributor Author

malbarbo commented Jun 7, 2017

Tests fails using node, it seems that libc is broken for emscripten, but posix_fallocate is available on emsdk musl.

I'm working in improving the emscripen support in the rust ecosystem, could you please release a new dot release?

@malbarbo
Copy link
Contributor Author

PR to enable and fixes tests for libc on emscripten.

@danburkert
Copy link
Owner

I'm not quite following, is this ready to merge?

@malbarbo
Copy link
Contributor Author

I though before that this was ready to merge, but now I think we should wait until we can test this. After libc PR got merged, I will send a PR to update libc on rust, then we can run the tests and make sure it works.

@danburkert
Copy link
Owner

SGTM, thanks.

@lilianmoraru
Copy link
Contributor

The new libc is getting merged upstream: rust-lang/rust#44116

@danburkert
Copy link
Owner

Is there any way to add emscripten coverage to travis?

@lilianmoraru
Copy link
Contributor

lilianmoraru commented Aug 31, 2017

@danburkert libc 0.2.30 was merged in the nightly Rust.
With this fix, we could try to test on nightly(binaries through rust-buildbot probably not available yet).
I still think that a new version should not be published until Travis is set to test the target.

@danburkert
Copy link
Owner

Yah I agree, it would be nice to have emscripten coverage in CI if feasible. However, If it would require jumping through a bunch of hoops, I could be convinced to go ahead since this is such a minimal change.

@danburkert
Copy link
Owner

Is this still a concern with all of the recent WASM stuff landing in Rust? I admit I haven't been following that as closely as I might, since I don't target browsers.

@lilianmoraru
Copy link
Contributor

Well, packages that depend on fs2 will still not be able to compile because of that missing cfg.

@danburkert
Copy link
Owner

@lilianmoraru has anything changed WRT feasibility of testing with travis?

@lilianmoraru
Copy link
Contributor

@danburkert

@danburkert
Copy link
Owner

OK sounds good, let's leave this open then. I'm not personally going to have time to drive it forward, but I welcome others to.

Thanks @lilianmoraru !

@lilianmoraru
Copy link
Contributor

All the blockers have been closed(maybe a libc update would be good).
What do you think about getting this in and then somebody could work on the CI?

@danburkert
Copy link
Owner

Yeah I'm fine with that. The libc version is floating (^), so I don't think it should cause problems. I'll go ahead and merge.

@danburkert danburkert merged commit 9a34045 into danburkert:master Jan 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants