Windows searches for DLLs in the following sequence:
1. The directory where the executable module for the current process is located. 2. The current directory. 3. The Windows system directory. The GetSystemDirectory function retrieves the path of this directory. 4. The Windows directory. The GetWindowsDirectory function retrieves the path of this directory. 5. The directories listed in the PATH environment variable.
OS X ----
libPDFNetC.dylib is loaded by the OS X dynamic linker:
The dynamic linker uses the directories pointed to by DYLD_LIBRARY_PATH. By default, this environment variable points to:
$(HOME)/lib /usr/local/lib /lib /usr/lib
Thus you can place libPDFNetC.dylib into one of these directories. We recommend using /usr/local/lib.
Alternatively, you can customize the directories searched for by the dynamic linker. It's recommended to add the path to DYLD_FALLBACK_LIBRARY_PATH instead of changing DYLD_LIBRARY_PATH, since changing DYLD_LIBRARY_PATH could have wide effects on your system if misconfigured. For more details, see:
The program loader uses the directories pointed to by the LD_LIBRARY_PATH, as well as the contents of /etc/ld.so.conf. The standard directories can vary by distribution, but might be one of:
Although the above methods work on OS X, you could also install PDFNet support for Java by copying libPDFNetC.dylib to to /Library/Java/Extensions/libPDFNetC.jnilib.