What are the advantages / disadvantages of Cocoa frameworks, libraries and packages?

Question

I have the following requirement.

I need to implement a dll type of thing on mac.I need to create a backend library that can be loaded dynamically. This background library will contain cocoa and C ++ classes.

What is the advantage / disadvantage of the cocoa structure, I still worked at Google, I could not find a better option. Please give me some suggestion. Does the cocoa kernel also load dynamically?

Answer 1

The main difference between a dynamic library and a framework is that the structure can contain resources (images, sound files, nibs, etc.) and header files. When you use a dynamic library, they are separate.

Both the environment and the dynamic library are loaded at runtime. If your library will be used only in Mac OS X, I recommend creating a framework because it is easier to manage, since everything is in the same folder.

Bundles (white LEGO bricks) are almost exclusively used as plugins. If you want to create a plug-in interface, you must accept the packages, and you must provide the infrastructure with which the packages can communicate. Bundles are also loaded at runtime.

Answer 2

Here's a decent tutorial (PDF form) that goes a little deeper, explaining the differences between regular libraries and frames.