build a static library, and fold it into wrap-mupdf
enable ICC profile support
To make sure all the required symbols are exported, the wrap-mupdf library is linked with some generated scripts using the symbols referenced in the corresponding FFI cdecl file (ffi-cdecl/mupdf_decl.c). This is the same technique I use on my meson branch to cut down the size of the monolibtic library build.
(The plan is to do the same with the k2pdfopt library and a static tesseract library).
Impact on code size (bss+data+text, release builds):
To make sure all the required symbols are exported, the wrap-mupdf library is linked with some generated scripts using the symbols referenced in the corresponding FFI cdecl file (
ffi-cdecl/mupdf_decl.c). This is the same technique I use on my meson branch to cut down the size of the monolibtic library build.(The plan is to do the same with the k2pdfopt library and a static tesseract library).
This change is