The lazy loading also avoids needing to 'fix' gdal after building by using install_name_tool to adjust the libjvm id.

Since the Mac install_name id of the Oracle libjvm.dylib starts with already, the dylib is set up for lazy dynamic loading, otherwise the embedded rpath is ignored and gdal throws a dylib loading error.

The rpath is only embedded for Oracle (non-framework) installs.

I tried to allow for auto-finding of install, with Oracle taking preference: Note, I don't do much editing of configure scripts, so some code review would be appreciated. configure to add support for finding Java installs for Mac. The Apple-supported Java is framework-based, the Oracle install has a similar layout to Unix/Linux installs.Īttached to ticket is a patch to. The two Java JDK setups on Mac are Apple-supported (<= 10.8, up to recent Java 1.6) and Oracle third-party manual install (10.8+, Java 1.6+). However, the MDB driver does function well, though Java installs aren't found by.

On Mac, with GDAL 1.10.1, the PGeo and Geomedia OGR drivers do not work due to non-functioning MDB Tools (I can install and config, but fails to load.

Download java for mac 10.7.5