Working with dylibs : Deployment Issues - Part 2

Read Part 1 of the post
Read Part 3 of the post

In addition to what I had already written on dylib deployment. My friend, Vishvesh, pointed out some additional notes.

• dylib execution path can be specified in Xcode project "Installation Directory" field. Using this will not require to use complex command line tools to specify the dylib installation path [I have yet verified this].


• otool when run against a static libraries (.a) lists all the object files.


• Command file can be used to detect the architecture type a dylib or a static lib is built for.
  
  example :
  %file myCustom.dylib
myCustom.dylib: Mach-O universal binary with 2 architectures
myCustom.dylib(for architecture i386): Mach-O dynamically linked shared library i386
myCustom.dylib(for architecture ppc): Mach-O dynamically linked shared library ppc


%file libdoCustomProcessing.a
libdoCustomProcessing.a: Mach-O universal binary with 2 architectures
libdoCustomProcessing.a (for architecture i386): current ar archive
libdoCustomProcessing.a (for architecture ppc): current ar archive
  

Read Part 1 of the post
Read Part 3 of the post