-
Notifications
You must be signed in to change notification settings - Fork 21
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
Request: Emscripten/wasm support #60
Comments
I have made some changes to cmakelists.txt and got the build working, can you please try this, |
Sorry for not replying sooner -- I will take a look at this in the next day or two and get back. Thanks |
Looks like I was able to build this using Emscripten, though I had to apply this change to consume it in the parent project in which I'm working. This test didn't try to do anything useful with libultrahdr, but it did ensure it was compiled in, headers could be included, and functions called. Thanks for the support on this -- would it be helpful if I opened a PR into your branch with the above changes? |
If it fixes a problem, please issue a pull request, thank you. |
mkdir build && cd build emcmake cmake ../ cmake --build ./ Successfully builds all targets with Emscripten toolchain. But, currently no bindings are present to really make use of the libraries that were built. fixes google#60
mkdir build && cd build emcmake cmake ../ cmake --build ./ Successfully builds all targets with Emscripten toolchain. But, currently no bindings are present to really make use of the libraries that were built. fixes #60
What the title says: can webassembly support be added to CMakeLists.txt, so users building with an Emscripten toolchain can integrate this?
There are some clear architecture & platform checks at the beginning of the top-level
CMakeLists.txt
file, which prevent this project from building via Emscripten. If I try to hack past those most basic checks, there are also errors related to libjpeg-turbo.I already have libjpeg-turbo building for emscripten in my build system, so these issues can be worked around.
The text was updated successfully, but these errors were encountered: