-
-
Notifications
You must be signed in to change notification settings - Fork 43
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 a new target "platform" for WebAssembly (compile libzim to Wasm) #503
Comments
Maybe there is a better way to avoid compiling useless components (examples etc) of icu and libzim than modifying Makefile.in and meson.build |
When it's ready, it should also compile the bindings, see kiwix/kiwix-js#768 |
This issue has been automatically marked as stale because it has not had recent activity. It will be now be reviewed manually. Thank you for your contributions. |
Now that kiwix/kiwix-js#513 is solved, it's a major blocker that goes out of the way for libzim wasm. |
@mossroy @mgautierfr OK, we shoukd move forward on this ASAP |
I'm not in favour of expecting developers to compile the libzim themself; for any binding, Javascript included. IMO, the goal should be to provide a directly usable libzim in Javascript. From a technical POV, this implies to create & publish the WASM file and a/the corresponding Javascript file allowing to exploit the @mossroy Do I understand properly? Would that satisfy your request? |
Yes, you understood properly, and that would be perfect. As I told you, we are not currently blocked, as we can compile by ourself. It means that the CI would provide all the necessary bindings, like you do for python. |
@mossroy Thank you for the confirmation.
Which one do you want to follow? |
This issue has been automatically marked as stale because it has not had recent activity. It will be now be reviewed manually. Thank you for your contributions. |
Compiled with emscripten, to produce libzim.a and other libraries.
libkiwix is probably not necessary : libzim should be enough for now.
It should :
The text was updated successfully, but these errors were encountered: