Context Navigation

GS-README.txt

Timestamp:

2018-07-10T18:32:20+12:00 (6 years ago)

Author:

ak19

Message:

Getting LIBJPEG to compile on Mac requires not passing --enable-static. On Mac too, compiling LIBJPEG also only produces .a (and no .so/.dylib) no matter what, but that happens to be what we want anyway. 2. Turning off building shared libraries (--disable-shared) for all libraries we build that are used by xpdftools, so that on Mac it hopefully chooses to link these in (which won't happen if there's a preferred dylib elsewhere, particularly on the system, which will then get linked in in preference on Macs). Still need to test these changes on Linux again.

File:

-              r32250
+              r32251
 https://unix.stackexchange.com/questions/279397/ldd-dont-find-path-how-to-add
+D. On why you can't build static binaries on Mac, but can build static libraries and link against them
+https://developer.apple.com/library/archive/qa/qa1118/_index.html (official page on how Mac doesn't support static binaries)
+https://stackoverflow.com/questions/3801011/ld-library-not-found-for-lcrt0-o-on-osx-10-6-with-gcc-clang-static-flag
+https://stackoverflow.com/questions/844819/how-to-static-link-on-os-x (mention of -Bstatic)
+https://www.allegro.cc/forums/thread/610923
+https://dropline.net/2015/10/static-linking-on-mac-os-x/ (explains that on Mac, .dylibs must be hidden for .a versions of libraries to be selected when linking)
+    This means that where possible we want to essentially do "--enable-static --disable-shared", or equivalent, when generating freetype, libz, libpng, libjpg, libtiff library files
+    so that Xpdf-Tools links against the .a files we generated rather than additional .dylib files
+http://www.simplesystems.org/libtiff/build.html
+configuration options for building libtiff. Want to turn off the compile process for libtiff producing tiff binaries, but there appears to be no such option.

Note: See TracChangeset for help on using the changeset viewer.