Johannes Hermann
Johannes Hermann
Ok. Got it building successfully when using pyodide tag 0.27.4 without using `PYMUPDF_SETUP_MUPDF_BUILD`.
There was some errors with v1.26.6 pymupdf when installing. I don't remember excactly. I relaxed the constraint again and the only thing now failing is our nix flake workflow for...
https://github.com/echemdb/svgdigitizer/actions/runs/19527751303/job/55903848090
https://github.com/echemdb/svgdigitizer/commit/0189a81c1d1390dfad6671dedda0251d3028685f
I see the empty `libmupdf.so` already for `pyodide-build=0.24.0`. For 0.23.4 it has a size of 27 MB. Please find attach a log from a build with the steps found here:...
`EMCC_DEBUG=1 HAVE_LIBCRYPTO=no OS=pyodide PYMUPDF_SETUP_FLAVOUR=pb PYMUPDF_SETUP_MUPDF_BUILD_TESSERACT=0 PYMUPDF_SETUP_MUPDF_TESSERACT=0 pyodide build --exports pyinit` resulted in the attached log [pyodide-debug-0.29.2.log](https://github.com/user-attachments/files/18675657/pyodide-debug-0.29.2.log) [libmupdf.zip](https://github.com/user-attachments/files/18675666/libmupdf.zip)
Thanks @ryanking13 . Using `whole_archive` leads to a working build.