Downloads
Install Instructions
I read some articles discouraging of the use of DYLDLIBRARYPATH, as the the path of dynamic library should be fixed using -installname, @rpath, and @loaderpath. In terms of making a program that runs both on Linux and Mac OS X, DYLDLIBRARYPATH of Mac OS X does exactly what LDLIBRARYPATH of Linux. How do I set the static library path in OS X Lion? To my library path. I have tried. DYLD is for dynamic libraries when the app runs ie.dylib.
Mac Os Shared Library Path
- Download and unzip to any directory. The unzipped directory structure is shown here:
- The C/C++ headers are contained in include directory.
- The static and dynamic libs are located in the libStatic and libDyn directories.
- Universal libs may be created by running the makeUniversalLibs.sh script. (Make sure this script has execute permission first 'chmod a+x makeUniversalLibs.sh') The contents of this shell script are shown here:
- This download is both the trial and full version.
Chilkat libraries are fully functional for 30-day evaluations. - Release Notes are available on the Chilkat blog.
- See also: Chilkat Reference Documentation
- See also: Chilkat Sample Code
- See also: Chilkat Blog
How to Distribute a dylib with your Application
(This information is general and applies to any dylib on Mac OS X.) On Mac OS X, a dynamic library (dylib) has an 'install name'. The install name is a path baked into the dynamic library that says where to find the library at runtime. When an application is linked against a dylib, the path is saved in the app's binary so that it can find the dylib at runtime.
The install name of a dylib can be viewed by using otool. For example:
This means that unless the DYLD_LIBRARY_PATH environment variable is set to allow the runtime linker find the dylib, the dylib must be placed in the exact location as specified by the install name.
However, the install name of a dylib can be changed by using the install_name_tool utility. The @loader_path keyword can be used to make it relative to an install directory.
Mac Os Dynamic Library Path System
Chilkat recommends becoming familiar with the install_name_tool command and it's various options. For example, this command changes the install name of libchilkat.dylib to be relative to the location of the binary using it:
Macos Dynamic Library Path
What Is Dll
$ otool -L myexe
mds:
libchartdir.4.dylib (compatibility version 4.0.0, current version 4.1.0)
/opt/local/lib/libQuantLib-0.9.0.dylib (compatibility version 0.0.0, current version 0.0.0)
/opt/local/lib/libboost_date_time-1_34_1.dylib (compatibility version 0.0.0, current version 0.0.0)
/opt/local/lib/libboost_program_options-1_34_1.dylib (compatibility version 0.0.0, current version 0.0.0)
/opt/local/lib/liblog4cpp.4.dylib (compatibility version 5.0.0, current version 5.6.0)
/System/Library/Frameworks/IOKit.framework/Versions/A/IOKit (compatibility version 1.0.0, current version 275.0.0)
/System/Library/Frameworks/Carbon.framework/Versions/A/Carbon (compatibility version 2.0.0, current version 128.0.0)
/System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa (compatibility version 1.0.0, current version 11.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.3.11)
/System/Library/Frameworks/QuickTime.framework/Versions/A/QuickTime (compatibility version 1.0.0, current version 861.0.0)
/System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL (compatibility version 1.0.0, current version 1.0.0)
/System/Library/Frameworks/AGL.framework/Versions/A/AGL (compatibility version 1.0.0, current version 1.0.0)
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.4.0)
/usr/local/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0)
libchartdir, the first library in the otool list, does not have an absolute path set. I have to set the DYLD_FALLBACK_LIBRARY_PATH to /opt/local/lib to let dyld find it at runtime.
What makes the other libraries installed under /opt/local/lib (QuantLib, boost) have their path recorded in the executable?