summaryrefslogtreecommitdiff
path: root/include/mupdf/xps.h
diff options
context:
space:
mode:
authorRobin Watts <robin.watts@artifex.com>2015-05-14 17:12:42 +0100
committerRobin Watts <robin.watts@artifex.com>2015-05-15 13:06:56 +0100
commit7d5ff30c37c9e5b271fdb2b8cb3219068048322e (patch)
tree5f60d1d03235f2cff161207e00515c5a4a69ef73 /include/mupdf/xps.h
parent250e8a11e1debfbd9c4fc84ad895bf923aac135e (diff)
downloadmupdf-7d5ff30c37c9e5b271fdb2b8cb3219068048322e.tar.xz
Support pdf files larger than 2Gig.
If FZ_LARGEFILE is defined when building, MuPDF uses 64bit offsets for files; this allows us to open streams larger than 2Gig. The downsides to this are that: * The xref entries are larger. * All PDF ints are held as 64bit things rather than 32bit things (to cope with /Prev entries, hint stream offsets etc). * All file positions are stored as 64bits rather than 32. The implementation works by detecting FZ_LARGEFILE. Some #ifdeffery in fitz/system.h sets fz_off_t to either int or int64_t as appropriate, and sets defines for fz_fopen, fz_fseek, fz_ftell etc as required. These call the fseeko64 etc functions on linux (and so define _LARGEFILE64_SOURCE) and the explicit 64bit functions on windows.
Diffstat (limited to 'include/mupdf/xps.h')
-rw-r--r--include/mupdf/xps.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/include/mupdf/xps.h b/include/mupdf/xps.h
index 13c8eea0..fd21fe7c 100644
--- a/include/mupdf/xps.h
+++ b/include/mupdf/xps.h
@@ -216,7 +216,7 @@ typedef struct xps_entry_s xps_entry;
struct xps_entry_s
{
char *name;
- int offset;
+ fz_off_t offset;
int csize;
int usize;
};