I think that several folks have articulated the many valid reasons why traditional static libraries are desireable: organization/ modularization of code within a single project by team members, use of large third party (often open source) in situations where one wishes to use a particular snapshot of the library - not as a dynamic "system resource". All this can be done with dylibs on MacOS X. See below
I think that several folks have articulated the many valid reasons why traditional static libraries are desireable: organization/ modularization of code within a single project by team members, use of large third party (often open source) in situations where one wishes to use a particular snapshot of the library - not as a dynamic "system resource".
They are not needed. So Apple tools like Xcode don't support them. You can use them as long as you stay inside the ./configure/ make/make install build method.