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

Target webassembly #46

Closed
unicomp21 opened this issue Aug 4, 2019 · 2 comments
Closed

Target webassembly #46

unicomp21 opened this issue Aug 4, 2019 · 2 comments

Comments

@unicomp21
Copy link

From a procgen perspective, ie generating assets within the browser, being able to compile gltf sdk as webassembly would be "huge".

@chriche-ms
Copy link
Member

We've experimented with compiling glTF-SDK as webassembly some time ago. The good news is that very few changes are required to get everything building and working (just a few minor changes to the CMakeList.txt files). You could easily do this in a fork of the repo.

Bringing the changes back into master branch would be more problematic as many of the unit tests fail due to having dependencies on external file and resources. Also, updating the DevOps build to install and use emscripten was more effort than we wanted to spend on functionality that we didn't intend to use in the short term.

Finally, you will likely need to write custom std::iostream derived types to interface between the wasm module and browser environment which could be tricky depending on the level of performance you need.

@bghgary
Copy link
Contributor

bghgary commented Dec 7, 2023

Fixed with #127.

@bghgary bghgary closed this as completed Dec 7, 2023
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

3 participants