-
Notifications
You must be signed in to change notification settings - Fork 61
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
WASM example not working with Pdfium release V5668 due to malloc() function change #95
Comments
Hi @inzanez , thank you for reporting the problem. Can I check the following:
|
No, there isn't any versioning hint, and annoyingly Pdfium itself doesn't provide any function to return the library version :/ I wouldn't describe this as a "solution" exactly, more a work-around. The problem is that the emscripten-provided Probably something subtle changed in the emscripten packaging, and it's just a question of tracking down what it was and figuring out how to work around it in |
Perfect, many thanks for that insight! I hope I can join you soon on digging into that issue. Sounds really interesting, but not that easy, remembering the whole emscripten around :-) |
The emscripten wrappers are in the |
The
But the
The missing |
@ajrcarey I would assume that must be updated in |
The |
Adjusted |
As there have been no further comments and I believe the issue is now resolved, I am closing the issue and publishing release 0.8.8. Feel free to re-open if you do not believe the issue is resolved in release 0.8.8. |
I just tried running the WASM example and I always get
Initialization of pdfium-render failed!
. I used to build everything manually so far with emscripten which is quite a pain. Now it feels more like magic, but...can't tell why that wouldn't work.Addition: I do get an error about malloc not being defined:
pdfium-render::initialize_pdfium_render(): Module._malloc() not defined
. I guess that will be related to the actual wasm build?The text was updated successfully, but these errors were encountered: