Skip to content
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

_ #1455

Closed
ghost opened this issue Aug 14, 2022 · 2 comments
Closed

_ #1455

ghost opened this issue Aug 14, 2022 · 2 comments

Comments

@ghost
Copy link

ghost commented Aug 14, 2022

_

@juj
Copy link

juj commented Aug 14, 2022

Forkers like this one https://github.com/juj/emscripten-scummvm [ ... ]. The error is in the project founder's ability to upstream their discoveries.

Nope. If you browse open source projects and judge work you would like to see done in them be a failure of other people's abilities, your thinking is where the error is.

@juj
Copy link

juj commented Aug 14, 2022

I see porting open-source apps to web as a way to honor other people's hard work. But for some reason @juj thinks I'm judging people instead of asking for more ideas on how to contribute.

Thank you. Now I understand, and such effort is appreciated. Your original post instead read like it was judging off people, thanks for the edit.

Obviously this has been merged in upstream

Emscripten-scummvm has not been merged to upstream scummvm to the best of my knowledge. Nor should it be. Best approach would be to redo the port from scratch in a completely new way, using the newer Emscripten PROXY_TO_PTHREAD build mode that did not exist when Emscripten-scummvm was worked on a decade ago.

@ghost ghost changed the title "i just think wasm is still bit annoying to work with" _ Aug 15, 2022
@ghost ghost closed this as completed Aug 15, 2022
This issue was closed.
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

No branches or pull requests

1 participant