What is the main difference between a framework and a dynamic library

What is the main difference between frame work and dynamic library

+16
objective-c cocoa macos
Mar 26 '10 at 5:40
source share
3 answers

At its core, the OS X infrastructure is a dynamically linked library. A frame is a special directory structure called a "framework" that contains one or more versions of a dynamically linked library, as well as dependent frameworks, resources, metadata, etc. Other bundles on OS X include .app packages (which contain the executable, as well as resources, dependent frameworks, etc.).

+13
Mar 26 '10 at 5:56
source share

A dynamic library is a basic concept, basically independent of a specific platform, that is, you can talk about dynamic libraries in OSX, Linux, Windows and mean the same basic thing - a piece of roaming object code with exported API characters, which consists of a way , which allows you to download and share applications on the platform.

Frame is an OSX-specific term. This is a package that defines some generally accepted directory structure and stores dynamic libraries, resources, package descriptions, and other relevant materials in predefined locations. This means that it has mainly semantic meaning, which allows developers (and the tools they create) to refer to it in the usual sense. It is worth noting that the framework should not contain shared libraries at all.

+8
Mar 26 '10 at 6:05
source share

Anatomy of the Framework may be helpful. In particular, Versions/Current/MyFramework mentioned in this example is a shared library. This section describes some other things that may exist in a structure package.

+2
Mar 26
source share



All Articles