MuPDF 1.24.0 Documentationcleanup. Conceptually, they work a lot like C++’s try/catch system, but do not require any special compiler support. The basic formulation is as follows: fz_try(ctx) { // Try to perform a task. Never 'return' that excep- tion. As a way of mitigating this problem, we provide a fz_var() macro that tells the compiler to ensure that that variable is not unset by the act of throwing the exception. A model piece of pdf_new_stext_page_from_annot() as a constructor of fz_stext_page. – Use new scripts/wrap/wdev.py to find C# compiler csc.exe on Windows. – Fixed handling of functions that return const fz_foo*. – Use our own handling0 码力 | 249 页 | 830.15 KB | 8 月前3
MuPDF 1.23.0 Documentationcleanup. Conceptually, they work a lot like C++’s try/catch system, but do not require any special compiler support. The basic formulation is as follows: fz_try(ctx) { // Try to perform a task. Never 'return' that excep- tion. As a way of mitigating this problem, we provide a fz_var() macro that tells the compiler to ensure that that variable is not unset by the act of throwing the exception. A model piece of pdf_new_stext_page_from_annot() as a constructor of fz_stext_page. – Use new scripts/wrap/wdev.py to find C# compiler csc.exe on Windows. 208 Chapter 7. Language Bindings MuPDF Documentation, Release 1.23.0 – Fixed0 码力 | 245 页 | 817.74 KB | 8 月前3
MuPDF 1.25.0 Documentationcleanup. Conceptually, they work a lot like C++’s try/catch system, but do not require any special compiler support. The basic formulation is as follows: fz_try(ctx) { // Try to perform a task. Never 'return' that excep- tion. As a way of mitigating this problem, we provide a fz_var() macro that tells the compiler to ensure that that variable is not unset by the act of throwing the exception. A model piece of API, for example USE_SYSTEM_LIBJPEG=yes. In addition, XCXXFLAGS can be used to set additional C++ compiler flags when building the C++ and Python bindings (the name is analogous to the XCFLAGS used by MuPDF’s0 码力 | 259 页 | 1.11 MB | 8 月前3
MuPDF 1.22.0 Documentationcleanup. Conceptually, they work a lot like C++’s try/catch system, but do not require any special compiler support. The basic formulation is as follows: fz_try(ctx) { // Try to perform a task. Never 'return' that excep- tion. As a way of mitigating this problem, we provide a fz_var() macro that tells the compiler to ensure that that variable is not unset by the act of throwing the exception. A model piece of Visual Studio GUI. [In the git history there is code that builds _mupdf.pyd by running the Windows compiler and linker cl.exe and link.exe directly, which avoids the complications of going via devenv, at0 码力 | 175 页 | 698.87 KB | 8 月前3
PyMuPDF 1.12.2 documentationprocess is much faster and requires the download of only one 3 MB file (either .zip or .whl) - no compiler, no Visual Studio, no download of MuPDF, even no download of PyMuPDF. Option 1: Install from Sources extension of the binary will be .pyd on Windows and .so on other platforms. Depending on your OS, your compiler and your font support choice (see above), this binary can be quite large and range from 5 MB to0 码力 | 387 页 | 2.70 MB | 1 年前3
PyMuPDF 1.24.2 Documentationcause problems because one can end up with MuPDF and PyMuPDF code being compiled with different compiler versions. 9 PyMuPDF Documentation, Release 1.24.2 As of PyMuPDF-1.20.0, the required MuPDF source object has no attribute ‘_annot’ in delete widget. • Misc changes to core code: – Fixed various compiler warnings and a sequence-point bug. – Added support for Memento builds. – Fixed leaks detected0 码力 | 565 页 | 6.84 MB | 1 年前3
共 6 条
- 1













