blocks|key|3175222|text|基本上，框架就是库，并为使用它们提供了一种方便的机制。如果你“深入”一个框架，它只是一个包含静态库和头文件的目录(在一些带有元数据的文件夹结构中)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3175223|如果你想创建你自己的框架，你必须创建一个“静态库”，并以一种特定的方式打包它。请参阅this+question|offset|length|3175224|一般来说，平台上的框架用于可重用的行为，您可以将自己的代码“添加到现有框架中”。如果你想拥有一些特定的功能，你可能需要使用库(例如three20)并将其打包到你的应用程序可分发中|style|BOLD|3175225|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/1300457/can-i-develop-my-own-objective-c-framework-for-cocoa-touch-applications^0|0|16|D|0|0|24|C|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@$D|X|E|Y|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

basically, frameworks ARE libraries and provide a handy mechanism for working with them. If you look "inside" a framework, it's just a directory containing a static library and header files (in some folder structure with metadata).

If you want to create your own framework, you have to create a "static library" and pack it in a specific way. see <a href="https://stackoverflow.com/questions/1300457/can-i-develop-my-own-objective-c-framework-for-cocoa-touch-applications">this question</a>

In general, framworks on platforms are used for reusable behaviour where you add your own code "into an existing framework". if you want to have some specific functionality, you may want to use a library (e.g. three20) and pack it into your app distributable

blocks|key|267616|text|与静态库相比，框架的最大优势是它们可以作为一种整洁的方式来打包已编译的库、二进制文件和任何相关的头文件。它们可以放到你的项目中(就像SDK的内置框架一样，比如基础和UIKit)，它们应该(在大多数情况下)可以正常工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|267617|大多数框架都包含动态库；使用Mac+Framework模板在Xcode中创建的框架将创建动态库。iPhone不支持动态框架，这就是为什么将可重用的iOS代码库作为静态库分发的原因。|267618|静态库很好，但它们需要用户做一些额外的工作。您需要将项目链接到库，并且需要将头文件复制到项目中，或者通过在构建设置中设置适当的头搜索路径来引用它们。|267619|所以:总而言之，我的观点是，分发你的库的最好方式是作为一个框架。要为iOS创建一个“静态”框架，基本上可以采用一个普通框架，并用编译好的静态库替换二进制文件。这就是我分发我的一个库Resty的方式，也是我打算将来分发我的库的方式。|offset|length|267620|您可能希望查看该项目中提供的Rakefile+(如果您不知道，Rake是Ruby的Make等价物)。我有几个任务来编译我的项目(使用xcodebuild)，并将它们打包为iOS的静态框架。您应该会发现这一点很有用。|style|CODE|267621|或者，您可能希望使用these+Xcode+4+templates来创建iOS框架。|267622|更新2013年12月9日：这是一个流行的答案，所以我想我应该编辑一下，说我对库分发的首选已经改变了。对于任何第三方库，无论是作为消费者还是生产者，我的首选都是CocoaPods。我使用CocoaPods分发我的库，并提供一个带有头作为备用选项的预编译静态库。|BOLD|267623|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/lukeredpath/LRResty|1|https://github.com/kstenerud/iOS-Universal-Framework^0|0|0|0|2I|5|0|0|1U|A|0|A|N|1|0|0|C|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|14|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|15|8|@]|9|@$H|16|I|17|1|18]]|A|$]]|$1|J|3|K|5|6|7|19|8|@$H|1A|I|1B|L|M]]|9|@]|A|$]]|$1|N|3|O|5|6|7|1C|8|@]|9|@$H|1D|I|1E|1|1F]]|A|$]]|$1|P|3|Q|5|6|7|1G|8|@$H|1H|I|1I|L|R]]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]|10|$5|V|W|X|A|$Y|11]]]]

The biggest advantage a framework has over static libraries is that they act as a neat way of packaging up the compiled library binary and any related headers. They can be dropped into your project (just like the SDK's built-in frameworks like Foundation and UIKit) and they should just work (most of the time).

Most frameworks contain dynamic libraries; frameworks created in Xcode using the Mac Framework template will create a dynamic library. The iPhone does not support dynamic frameworks which is why it has become common for reusable libraries of iOS code to be distributed as static libraries instead.

Static libraries are fine, but they require a bit of extra work on the part of the user. You need to link your project to the library and you need to copy the header files into your project or reference them somewhere by setting the appropriate header search paths in your build settings.

So: in summary, my opinion is that the best way of distributing your library is as a framework. To create a "static" framework for iOS, you can essentially take a normal framework and replace the binary with your compiled static library. This is how I distribute one of my libraries, <a href="https://github.com/lukeredpath/LRResty">Resty</a> and is how I intend to distribute my libraries in the future.

You may want to look at the supplied Rakefile in that project (in case you aren't aware, Rake is Ruby's equivalent of Make). I have a handful of tasks for compiling my project (using <code>xcodebuild</code>) and packaging them as a static framework for iOS. You should find this useful.

Alternatively, you may wish to use <a href="https://github.com/kstenerud/iOS-Universal-Framework">these Xcode 4 templates</a> for creating an iOS framework.

Update 9 Dec 2013: this is a popular answer so I thought I'd edit to say that my first choice for library distribution has changed. My first choice for any third party library as either a consumer or producer is CocoaPods. I distribute my libraries using CocoaPods and offer a precompiled static library with headers as a fallback option.

I am quite new to xcode and objective-c. I want to ask a very basic question.

I saw that when "linking binary to libraries" in project settings, there are differences about framework and libraries, imported from other projects in workspace.

First question, why is there a framework? And why is there a library? Cannot my library be a framework?

And then, from a .h file, how can I call classes from my imported static library?

I suppose there must be a prefix, but I couldn't find it.
Neither nor "ProjName/Myclass.h" are working.

Please, be as specific as you can.

Thanks

Difference between framework and static library in xcode4, and how to call them

Xcode

我对xcode和objective-c非常陌生。我想问一个非常基本的问题。我看到在项目设置中“将二进制文件链接到库”时，从工作区中的其他项目导入的框架和库是有区别的。第一个问题，为什么会有一个框架？为什么会有一个图书馆？我的库不能是一个框架吗？然后，如何从.h文件中调用导入的静态库中的类？我想一定有个前缀，但我找不到。...

问xcode4中框架和静态库的区别以及如何调用它们
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问xcode4中框架和静态库的区别以及如何调用它们EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问xcode4中框架和静态库的区别以及如何调用它们
EN