iOS上如何制作自己的Framework呢？（不是靜態(tài)庫）
請看stackoverflow上的提問(wèn)：
解決辦法
1，通過(guò)命令行腳本
http://www.cocoanetics.com/2010/04/making-your-own-iphone-frameworks/
由cocoa的Framework演變而來(lái)
2，通過(guò)hack bundle
http://www.cocoanetics.com/2010/05/making-your-own-iphone-frameworks-in-xcode/
這種方法有熱心的同學(xué)做了中文翻譯
http://www.cocoachina.com/bbs/read.php?tid-75680.html
但是需要制作2個(gè)framework，分別對應于simulator和device
這種方法這里也有詳細介紹 http://db-in.com/blog/2011/05/creating-universal-framework-to-iphone-ios/
3，使用別人的模板
https://github.com/kstenerud/iOS-Universal-Framework
這個(gè)算是集大成吧。當然作者有說(shuō)明，這個(gè)也是假的，并不能象SDK自帶的framework那樣自如使用
而code google上的pldatabase framework是可以象SDK自己的framework一樣，一個(gè)framework同時(shí)運行在模擬器和真機上的
http://code.google.com/p/pldatabase/
有待研究，以后再來(lái)補充
補充：
pldatabase framework 也只是產(chǎn)生2個(gè)靜態(tài)庫（.a）然后通過(guò)lipo合并起來(lái)，但是這已經(jīng)很好了。
Lipo Binary 中的腳本如下：
FRAMEWORK="${BUILT_PRODUCTS_DIR}/${PRODUCT_NAME}.framework"
lipo \
"${BUILD_DIR}/${CONFIGURATION}-iphoneos/libPlausibleDatabase-iPhoneOS.a" \
"${BUILD_DIR}/${CONFIGURATION}-iphonesimulator/libPlausibleDatabase-iPhoneSimulator.a" \
-create -output "${FRAMEWORK}/Versions/Current/${PRODUCT_NAME}"
cd "${FRAMEWORK}" && ln -sf "Versions/Current/${PRODUCT_NAME}" ./
看來(lái)上面的方法沒(méi)有產(chǎn)生真正意義上的Framework，所謂的Framework不是hack bundle就是 hack static lib
至于第二種方法為什么可以實(shí)現，因為Framework其實(shí)也是一個(gè)bundle (a structured directory)，
可以參照apple的官方說(shuō)明 http://developer.apple.com/library/mac/#documentation/General/Conceptual/DevPedia-CocoaCore/Framework.html
What are Frameworks?
A framework is a hierarchical directory that encapsulates shared resources, such as a dynamic shared library, nib files, image files, localized strings, header files, and reference documentation in a single package. Multiple applications can use all of these resources simultaneously. The system loads them into memory as needed and shares the one copy of the resource among all applications whenever possible.
A framework is also a bundle and its contents can be accessed using Core Foundation Bundle Services or the Cocoa NSBundle class. However, unlike most bundles, a framework bundle does not appear in the Finder as an opaque file. A framework bundle is a standard directory that the user can navigate. This makes it easier for developers to browse the framework contents and view any included documentation and header files.
Frameworks serve the same purpose as static and dynamic shared libraries, that is, they provide a library of routines that can be called by an application to perform a specific task. For example, the Application Kit and Foundation frameworks provide the programmatic interfaces for the Cocoa classes and methods. Frameworks offer the following advantages over static-linked libraries and other types of dynamic shared libraries:
Frameworks group related, but separate, resources together. This grouping makes it easier to install, uninstall, and locate those resources.
Frameworks can include a wider variety of resource types than libraries. For example, a framework can include any relevant header files and documentation.
Multiple versions of a framework can be included in the same bundle. This makes it possible to be backward compatible with older programs.
Only one copy of a framework’s read-only resources reside physically in-memory at any given time, regardless of how many processes are using those resources. This sharing of resources reduces the memory footprint of the system and helps improve performance.
Note: Frameworks are not required to provide a programmatic interface and can include only resource files. However, such a use is not common.
The Darwin layer contains many static and dynamic libraries but otherwise, most Mac OS X interfaces are packaged as frameworks. Some key frameworks—including Carbon, Cocoa, Application Services, and Core Services—provide convenient groupings of several smaller but related frameworks. These framework groups are called umbrella frameworks and they act as an abstraction layer between a technology and the subframeworks that implement that technology.
In addition to using the system frameworks, you can create your own frameworks and use them privately for your own applications or make them publicly available to other developers. Private frameworks are appropriate for code modules you want to use in your own applications but do not want other developers to use. Public frameworks are intended for use by other developers and usually include headers and documentation defining the framework’s public interface
聯(lián)系客服
