blocks|key|12650|text|我找到了一个GitHub项目，它在Swift框架中成功地使用了CommonCrypto：SHA256+256-Swift。另外，这篇关于sqlite3中的相同问题的文章也很有用。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|12651|根据以上所述，这些步骤如下：|12652|1)在项目目录中创建一个CommonCrypto目录。在内部创建一个module.map文件。模块映射将允许我们使用CommonCrypto库作为Swift中的一个模块。其内容如下：|style|CODE|12653|module+CommonCrypto+[system]+{
++++header+"/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator8.0.sdk/usr/include/CommonCrypto/CommonCrypto.h"
++++link+"CommonCrypto"
++++export+*
}|code-block|syntax|javascript|12654|2)在Build中，在Swift编译器搜索路径中，将CommonCrypto目录添加到导入路径(SWIFT_INCLUDE_PATHS)中。|12655|​|12656|📷|atomic|12657|12658|3)最后，将CommonCrypto导入Swift文件中作为任何其他模块。例如：|12659|import+CommonCrypto

extension+String+{

++++func+hnk_MD5String()+->+String+{
++++++++if+let+data+=+self.dataUsingEncoding(NSUTF8StringEncoding)
++++++++{
++++++++++++let+result+=+NSMutableData(length:+Int(CC_MD5_DIGEST_LENGTH))
++++++++++++let+resultBytes+=+UnsafeMutablePointer<CUnsignedChar>(result.mutableBytes)
++++++++++++CC_MD5(data.bytes,+CC_LONG(data.length),+resultBytes)
++++++++++++let+resultEnumerator+=+UnsafeBufferPointer<CUnsignedChar>(start:+resultBytes,+length:+result.length)
++++++++++++let+MD5+=+NSMutableString()
++++++++++++for+c+in+resultEnumerator+{
++++++++++++++++MD5.appendFormat("%2502x",+c)
++++++++++++}
++++++++++++return+MD5
++++++++}
++++++++return+""
++++}
}|12660|局限性|12661|在另一个项目中使用自定义框架会在编译时由于错误missing+required+module+'CommonCrypto'而失败。这是因为自定义框架中似乎没有包含CommonCrypto模块。解决方法是在使用框架的项目中重复步骤2(设置Import+Paths)。|12662|模块映射不是独立于平台的(它目前指向特定的平台，iOS+8模拟器)。我不知道如何使标题路径相对于当前平台。|12663|iOS+8+<=的更新我们应该删除行链接"CommonCrypto"，以获得成功的编译。|BOLD|12664|更新/编辑|12665|我一直收到以下生成错误：|12666|ld:未找到用于体系结构的-lCommonCrypto库x86_64+clang:+x86_64:+linker命令失败，退出代码1(使用-v查看调用)|blockquote|12667|除非我从我创建的link+"CommonCrypto"文件中删除了行module.map。一旦我删除了这条线，它就可以了。|12668|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/CryptoCoinSwift/SHA256-Swift|1|http://programmingthomas.com/blog/2014/7/23/sqlite-in-swift-frameworks|2|IMAGE|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/a9350efa81772710f526467cb3f3f2ea.png|imageAlt^0|18|G|0|1W|D|1|0|0|C|C|Y|A|0|0|Q|C|1C|J|0|0|0|1|2|0|0|0|0|0|N|12|3A|C|0|0|I|G|0|0|5|0|0|0|8|J|Y|A|0^^$0|@$1|2|3|4|5|6|7|1Y|8|@]|9|@$A|1Z|B|20|1|21]|$A|22|B|23|1|24]]|C|$]]|$1|D|3|E|5|6|7|25|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|26|8|@$A|27|B|28|H|I]|$A|29|B|2A|H|I]]|9|@]|C|$]]|$1|J|3|K|5|L|7|2B|8|@]|9|@]|C|$M|N]]|$1|O|3|P|5|6|7|2C|8|@$A|2D|B|2E|H|I]|$A|2F|B|2G|H|I]]|9|@]|C|$]]|$1|Q|3|R|5|6|7|2H|8|@]|9|@]|C|$]]|$1|S|3|T|5|U|7|2I|8|@]|9|@$A|2J|B|2K|1|2L]]|C|$]]|$1|V|3|R|5|6|7|2M|8|@]|9|@]|C|$]]|$1|W|3|X|5|6|7|2N|8|@]|9|@]|C|$]]|$1|Y|3|Z|5|L|7|2O|8|@]|9|@]|C|$M|N]]|$1|10|3|11|5|6|7|2P|8|@]|9|@]|C|$]]|$1|12|3|13|5|6|7|2Q|8|@$A|2R|B|2S|H|I]|$A|2T|B|2U|H|I]]|9|@]|C|$]]|$1|14|3|15|5|6|7|2V|8|@]|9|@]|C|$]]|$1|16|3|17|5|6|7|2W|8|@$A|2X|B|2Y|H|18]]|9|@]|C|$]]|$1|19|3|1A|5|6|7|2Z|8|@$A|30|B|31|H|18]]|9|@]|C|$]]|$1|1B|3|1C|5|6|7|32|8|@]|9|@]|C|$]]|$1|1D|3|1E|5|1F|7|33|8|@]|9|@]|C|$]]|$1|1G|3|1H|5|6|7|34|8|@$A|35|B|36|H|I]|$A|37|B|38|H|I]]|9|@]|C|$]]|$1|1I|3|-4|5|6|7|39|8|@]|9|@]|C|$]]]|1J|$1K|$5|1L|1M|1N|C|$1O|1P]]|1Q|$5|1L|1M|1N|C|$1O|1R]]|1S|$5|1T|1M|1U|C|$1V|1W|1X|-4]]]]

I found a GitHub project that successfully uses CommonCrypto in a Swift framework: <a href="https://github.com/CryptoCoinSwift/SHA256-Swift" rel="noreferrer">SHA256-Swift</a>. Also, this article about <a href="http://programmingthomas.com/blog/2014/7/23/sqlite-in-swift-frameworks" rel="noreferrer">the same problem with sqlite3</a> was useful.

Based on the above, the steps are:

1) Create a <code>CommonCrypto</code> directory inside the project directory. Within, create a <code>module.map</code> file. The module map will allow us to use the CommonCrypto library as a module within Swift. Its contents are:

<pre><code>module CommonCrypto [system] {
 header "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator8.0.sdk/usr/include/CommonCrypto/CommonCrypto.h"
 link "CommonCrypto"
 export *
}
</code></pre>

2) In Build Settings, within Swift Compiler - Search Paths, add the <code>CommonCrypto</code> directory to Import Paths (<code>SWIFT_INCLUDE_PATHS</code>).

<img src="https://i.stack.imgur.com/FdWBf.png" alt="Build Settings">

3) Finally, import CommonCrypto inside your Swift files as any other modules. For example:

<pre><code>import CommonCrypto

extension String {

 func hnk_MD5String() -&gt; String {
 if let data = self.dataUsingEncoding(NSUTF8StringEncoding)
 {
 let result = NSMutableData(length: Int(CC_MD5_DIGEST_LENGTH))
 let resultBytes = UnsafeMutablePointer&lt;CUnsignedChar&gt;(result.mutableBytes)
 CC_MD5(data.bytes, CC_LONG(data.length), resultBytes)
 let resultEnumerator = UnsafeBufferPointer&lt;CUnsignedChar&gt;(start: resultBytes, length: result.length)
 let MD5 = NSMutableString()
 for c in resultEnumerator {
 MD5.appendFormat("%02x", c)
 }
 return MD5
 }
 return ""
 }
}
</code></pre>

<h2>Limitations</h2>

Using the custom framework in another project fails at compile time with the error <code>missing required module 'CommonCrypto'</code>. This is because the CommonCrypto module does not appear to be included with the custom framework. A workaround is to repeat step 2 (setting <code>Import Paths</code>) in the project that uses the framework.

The module map is not platform independent (it currently points to a specific platform, the iOS 8 Simulator). I don't know how to make the header path relative to the current platform.

Updates for iOS 8 &lt;= We should remove the line link "CommonCrypto", to get the successful compilation.

UPDATE / EDIT

I kept getting the following build error:

<blockquote>
 ld: library not found for -lCommonCrypto for architecture x86_64
 clang: error: linker command failed with exit code 1 (use -v to see invocation) 
</blockquote>

Unless I removed the line <code>link "CommonCrypto"</code> from the <code>module.map</code> file I created. Once I removed this line it built ok.

blocks|key|463816|text|这很简单。添加|type|unstyled|depth|inlineStyleRanges|entityRanges|data|463817|#import+<CommonCrypto/CommonCrypto.h>|code-block|syntax|javascript|463818|到.h文件(项目的桥接头文件)。按照惯例，您可以称它为YourProjectName-桥接-Header.h。|463819|然后转到您的项目构建设置，并寻找Swift编译器-代码生成。在它下面，将桥接头的名称添加到条目"Objetive-C桥接标题“中。|463820|你的任务完成了。Swift代码中不需要导入。此桥接头文件中列出的任何公共目标-C头对Swift都是可见的。|463821|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

It's very simple. Add

<pre><code>#import &lt;CommonCrypto/CommonCrypto.h&gt;
</code></pre>

to a .h file (the bridging header file of your project). As a convention you can call it YourProjectName-Bridging-Header.h.

Then go to your project Build Settings and look for Swift Compiler - Code Generation. Under it, add the name of your bridging header to the entry "Objetive-C Bridging Header".

You're done. No imports required in your Swift code. Any public Objective-C headers listed in this bridging header file will be visible to Swift.

blocks|key|463478|text|您实际上可以构建一个“只起作用”的解决方案(不需要像其他解决方案所要求的那样，将module.modulemap和SWIFT_INCLUDE_PATHS设置复制到您的项目中)，但它确实要求您创建一个虚拟框架/模块，您将适当地将其导入到框架中。我们还可以确保它不受平台(iphoneos、iphonesimulator或macosx)的影响。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|463479|向项目中添加一个新的框架目标，并以系统库的名称命名它，例如，"CommonCrypto“。(您可以删除伞头，CommonCrypto.h.)|ordered-list-item|463480|添加一个新的配置设置文件并命名它，例如，"CommonCrypto.xcconfig“。(不要检查你的目标是否包括在内。)用以下内容填充它：
$(SRCROOT)/CommonCrypto/iphonesimulator.modulemap+MODULEMAP_FILEsdk=iphoneos*+=\$(+MODULEMAP_FILEsdk=iphonesimulator*+)/CommonCrypto/iphoneos.Modemap+MODULEMAP_FILEsdk=iphonesimulator*=\\+MODULEMAP_FILEsdk=macosx*+=\$(SRCROOT)/CommonCrypto/macosx.Modemap|463481|创建上面引用的三个模块映射文件，并使用以下内容填充它们：|463482|"/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk/usr/include/CommonCrypto/CommonCrypto.h“|463483|-+**iphoneos.modulemap**|code-block|syntax|javascript|463484|
模块CommonCrypto系统{+header+CommonCrypto导出*}|463485|-+iphonesimulator.modulemap|463486|模块CommonCrypto系统{标头CommonCrypto导出*}|463487|-+macosx.modulemap|463488|463489|(如果您正在运行测试版，请将"Xcode.app“替换为"Xcode-beta.app”。如果没有运行El+Capitan，则用当前的OS替换10.11。)|463490|在项目设置的Configurations，信息选项卡上，将CommonCrypto的调试和发布配置设置为CommonCrypto+(引用CommonCrypto.xcconfig).+)|463491|在框架目标的CommonCrypto构建阶段选项卡上，将框架添加到目标依赖项中。此外，将libcommonCrypto.dylib添加到具有库构建阶段的链接二进制文件中。|463492|在CommonCrypto.framework产品中选择，并确保包装器的目标成员资格设置为可选。|463493|现在您应该能够在包装器框架中构建、运行和import+CommonCrypto。|463494|有关示例，请参见SQLite.swift如何使用虚拟SQLite.swift|463495|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/stephencelis/SQLite.swift|1^0|14|G|1L|J|3Q|8|3Z|F|4F|6|0|1I|E|0|6|6|0|0|0|0|0|2|P|0|0|2|G|0|0|1Z|5|0|6|E|T|C|16|2|19|2|1G|C|1W|L|0|6|C|X|5|18|L|24|9|0|0|P|10|6|19|2|0|K|J|0|8|C|0|Q|C|1|0^^$0|@$1|2|3|4|5|6|7|1O|8|@$9|1P|A|1Q|B|C]|$9|1R|A|1S|B|D]|$9|1T|A|1U|B|D]|$9|1V|A|1W|B|D]|$9|1X|A|1Y|B|D]]|E|@]|F|$]]|$1|G|3|H|5|I|7|1Z|8|@$9|20|A|21|B|C]]|E|@]|F|$]]|$1|J|3|K|5|I|7|22|8|@$9|23|A|24|B|C]]|E|@]|F|$]]|$1|L|3|M|5|I|7|25|8|@]|E|@]|F|$]]|$1|N|3|O|5|6|7|26|8|@]|E|@]|F|$]]|$1|P|3|Q|5|R|7|27|8|@]|E|@]|F|$S|T]]|$1|U|3|V|5|6|7|28|8|@]|E|@]|F|$]]|$1|W|3|X|5|6|7|29|8|@$9|2A|A|2B|B|C]]|E|@]|F|$]]|$1|Y|3|Z|5|6|7|2C|8|@]|E|@]|F|$]]|$1|10|3|11|5|6|7|2D|8|@$9|2E|A|2F|B|C]]|E|@]|F|$]]|$1|12|3|Z|5|6|7|2G|8|@]|E|@]|F|$]]|$1|13|3|14|5|6|7|2H|8|@$9|2I|A|2J|B|D]]|E|@]|F|$]]|$1|15|3|16|5|I|7|2K|8|@$9|2L|A|2M|B|C]|$9|2N|A|2O|B|C]|$9|2P|A|2Q|B|C]|$9|2R|A|2S|B|C]|$9|2T|A|2U|B|C]|$9|2V|A|2W|B|C]]|E|@]|F|$]]|$1|17|3|18|5|I|7|2X|8|@$9|2Y|A|2Z|B|C]|$9|30|A|31|B|C]|$9|32|A|33|B|C]|$9|34|A|35|B|C]]|E|@]|F|$]]|$1|19|3|1A|5|I|7|36|8|@$9|37|A|38|B|C]|$9|39|A|3A|B|C]|$9|3B|A|3C|B|C]]|E|@]|F|$]]|$1|1B|3|1C|5|6|7|3D|8|@$9|3E|A|3F|B|D]]|E|@]|F|$]]|$1|1D|3|1E|5|6|7|3G|8|@]|E|@$9|3H|A|3I|1|3J]|$9|3K|A|3L|1|3M]]|F|$]]|$1|1F|3|-4|5|6|7|3N|8|@]|E|@]|F|$]]]|1G|$1H|$5|1I|1J|1K|F|$1L|1M]]|1N|$5|1I|1J|1K|F|$1L|1M]]]]

You can actually build a solution that "just works" (no need to copy a module.modulemap and <code>SWIFT_INCLUDE_PATHS</code> settings over to your project, as required by other solutions here), but it does require you to create a dummy framework/module that you'll import into your framework proper. We can also ensure it works regardless of platform (<code>iphoneos</code>, <code>iphonesimulator</code>, or <code>macosx</code>).

<ol>
<li>Add a new framework target to your project and name it after the system library, e.g., "CommonCrypto". (You can delete the umbrella header, CommonCrypto.h.)</li>
<li>Add a new Configuration Settings File and name it, e.g., "CommonCrypto.xcconfig". (Don't check any of your targets for inclusion.) Populate it with the following:

<pre><code>MODULEMAP_FILE[sdk=iphoneos*] = \
 $(SRCROOT)/CommonCrypto/iphoneos.modulemap
MODULEMAP_FILE[sdk=iphonesimulator*] = \
 $(SRCROOT)/CommonCrypto/iphonesimulator.modulemap
MODULEMAP_FILE[sdk=macosx*] = \
 $(SRCROOT)/CommonCrypto/macosx.modulemap
</code></pre></li>
<li>Create the three referenced module map files, above, and populate them with the following:

<ul>
<li>iphoneos.modulemap

<pre><code>module CommonCrypto [system] {
 header "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk/usr/include/CommonCrypto/CommonCrypto.h"
 export *
}
</code></pre></li>
<li>iphonesimulator.modulemap

<pre><code>module CommonCrypto [system] {
 header "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator.sdk/usr/include/CommonCrypto/CommonCrypto.h"
 export *
}
</code></pre></li>
<li>macosx.modulemap

<pre><code>module CommonCrypto [system] {
 header "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk/usr/include/CommonCrypto/CommonCrypto.h"
 export *
}
</code></pre></li>
</ul>

(Replace "Xcode.app" with "Xcode-beta.app" if you're running a beta version. Replace <code>10.11</code> with your current OS SDK if not running El Capitan.)</li>
<li>On the Info tab of your project settings, under Configurations, set the Debug and Release configurations of CommonCrypto to CommonCrypto (referencing CommonCrypto.xcconfig).</li>
<li>On your framework target's Build Phases tab, add the CommonCrypto framework to Target Dependencies. Additionally add libcommonCrypto.dylib to the Link Binary With Libraries build phase.</li>
<li>Select CommonCrypto.framework in Products and make sure its Target Membership for your wrapper is set to Optional.</li>
</ol>

You should now be able to build, run and <code>import CommonCrypto</code> in your wrapper framework.

For an example, see how <a href="https://github.com/stephencelis/SQLite.swift">SQLite.swift</a> uses a dummy sqlite3.framework.

blocks|key|12775|text|这个答案讨论了如何使它在框架内工作，以及如何使用Cocoapods和Carthage|type|unstyled|depth|inlineStyleRanges|entityRanges|data|12776|模块映射方法|offset|length|style|BOLD|12777|我在CommonCrypto+https://github.com/onmyway133/arcane，https://github.com/onmyway133/Reindeer的包装器中使用了https://github.com/onmyway133/Reindeer|12778|对于获得header+not+found的用户，请查看https://github.com/onmyway133/Arcane/issues/4或运行xcode-select+--install|CODE|12779|创建一个包含CCommonCrypto的文件夹module.modulemap
模块CCommonCrypto+{+header+"/usr/include/CommonCrypto/CommonCrypto.h“导出*}|unordered-list-item|12780|转到构建设置->导入路径
${SRCROOT}/Sources/CCommonCrypto|12781|Cocoapods的模块化映射方法|12782|这是podspec+https://github.com/onmyway133/Arcane/blob/master/Arcane.podspec
s.source_files+=‘s.source_files/**/*.+s.xcconfig+={+'SWIFT_INCLUDE_PATHS’=>+}+s.preserve_paths+=‘Source/CCommonCrypto/module.Modemap’|12783|使用module_map无效，请参阅https://github.com/CocoaPods/CocoaPods/issues/5271|12784|在path中使用本地开发Pod不起作用，请参见https://github.com/CocoaPods/CocoaPods/issues/809|12785|这就是为什么您看到我的示例Podfile+https://github.com/onmyway133/CommonCrypto.swift/blob/master/Example/CommonCryptoSwiftDemo/Podfile指向git
目标'CommonCryptoSwiftDemo‘做荚'CommonCryptoSwift'，:git+=>+'https://github.com/onmyway133/CommonCrypto.swift’结束|12786|公共报头方法|12787|吉吉是libxml2的包装器，它使用公共头方法。|12788|它有一个头文件https://github.com/honghaoz/Ji/blob/master/Source/Ji.h，Target+Membership设置为Public。|12789|它有一个libxml2+https://github.com/honghaoz/Ji/tree/master/Source/Ji-libxml的头文件列表。|12790|它有生成设置->头搜索路径
$(SDKROOT)/usr/include/libxml2+2|12791|它有构建设置->其他链接器标志
-lxml2|12792|带有公共头方法的Cocoapods+|12793|看看podspec+https://github.com/honghaoz/Ji/blob/master/Ji.podspec
s.libraries+=+"xml2“s.xcconfig+={+'HEADER_SEARCH_PATHS‘=>’$(SDKROOT)/usr/include/libxml2+2‘，'OTHER_LDFLAGS’=>+'-lxml2‘}|12794|有趣的相关文章|12795|如何从Swift呼叫C？|12796|https://spin.atomicobject.com/2015/02/23/c-libraries-swift/|12797|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/onmyway133/arcane|1|https://github.com/onmyway133/Reindeer|2|3|https://github.com/onmyway133/Arcane/issues/4|4|https://github.com/onmyway133/Arcane/blob/master/Arcane.podspec|5|https://github.com/CocoaPods/CocoaPods/issues/5271|6|https://github.com/CocoaPods/CocoaPods/issues/809|7|https://github.com/onmyway133/CommonCrypto.swift/blob/master/Example/CommonCryptoSwiftDemo/Podfile|8|https://github.com/onmyway133/CommonCrypto.swift|9|https://github.com/honghaoz/Ji|10|https://github.com/honghaoz/Ji/blob/master/Source/Ji.h|11|https://github.com/honghaoz/Ji/tree/master/Source/Ji-libxml|12|https://github.com/honghaoz/Ji/blob/master/Ji.podspec|13|https://stackoverflow.com/questions/24004732/how-to-call-c-from-swift|14^0|0|0|6|0|F|10|0|1G|12|1|2Q|12|2|0|4|G|23|M|R|19|3|0|6|D|N|G|0|0|0|H|0|A|1R|4|0|2|A|I|1E|5|0|1|4|N|1D|6|0|L|2Q|7|51|1C|8|0|0|6|0|0|2|9|0|1Q|H|2A|6|7|1I|A|0|C|1N|B|0|0|0|8|A|0|A|1H|C|0|0|7|0|0|C|D|0|0|1N|E|0^^$0|@$1|2|3|4|5|6|7|2L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|2M|8|@$D|2N|E|2O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|2P|8|@]|9|@$D|2Q|E|2R|1|2S]|$D|2T|E|2U|1|2V]|$D|2W|E|2X|1|2Y]]|A|$]]|$1|J|3|K|5|6|7|2Z|8|@$D|30|E|31|F|L]|$D|32|E|33|F|L]]|9|@$D|34|E|35|1|36]]|A|$]]|$1|M|3|N|5|O|7|37|8|@$D|38|E|39|F|L]|$D|3A|E|3B|F|L]]|9|@]|A|$]]|$1|P|3|Q|5|O|7|3C|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|3D|8|@$D|3E|E|3F|F|G]]|9|@]|A|$]]|$1|T|3|U|5|O|7|3G|8|@]|9|@$D|3H|E|3I|1|3J]]|A|$]]|$1|V|3|W|5|O|7|3K|8|@$D|3L|E|3M|F|L]]|9|@$D|3N|E|3O|1|3P]]|A|$]]|$1|X|3|Y|5|O|7|3Q|8|@$D|3R|E|3S|F|L]]|9|@$D|3T|E|3U|1|3V]]|A|$]]|$1|Z|3|10|5|O|7|3W|8|@]|9|@$D|3X|E|3Y|1|3Z]|$D|40|E|41|1|42]]|A|$]]|$1|11|3|12|5|6|7|43|8|@$D|44|E|45|F|G]]|9|@]|A|$]]|$1|13|3|14|5|O|7|46|8|@]|9|@$D|47|E|48|1|49]]|A|$]]|$1|15|3|16|5|O|7|4A|8|@$D|4B|E|4C|F|L]|$D|4D|E|4E|F|L]]|9|@$D|4F|E|4G|1|4H]]|A|$]]|$1|17|3|18|5|O|7|4I|8|@]|9|@$D|4J|E|4K|1|4L]]|A|$]]|$1|19|3|1A|5|O|7|4M|8|@]|9|@]|A|$]]|$1|1B|3|1C|5|O|7|4N|8|@]|9|@]|A|$]]|$1|1D|3|1E|5|6|7|4O|8|@$D|4P|E|4Q|F|G]]|9|@]|A|$]]|$1|1F|3|1G|5|O|7|4R|8|@]|9|@$D|4S|E|4T|1|4U]]|A|$]]|$1|1H|3|1I|5|6|7|4V|8|@$D|4W|E|4X|F|G]]|9|@]|A|$]]|$1|1J|3|1K|5|O|7|4Y|8|@]|9|@$D|4Z|E|50|1|51]]|A|$]]|$1|1L|3|1M|5|O|7|52|8|@]|9|@$D|53|E|54|1|55]]|A|$]]|$1|1N|3|-4|5|6|7|56|8|@]|9|@]|A|$]]]|1O|$1P|$5|1Q|1R|1S|A|$1T|1U]]|1V|$5|1Q|1R|1S|A|$1T|1W]]|1X|$5|1Q|1R|1S|A|$1T|1W]]|1Y|$5|1Q|1R|1S|A|$1T|1Z]]|20|$5|1Q|1R|1S|A|$1T|21]]|22|$5|1Q|1R|1S|A|$1T|23]]|24|$5|1Q|1R|1S|A|$1T|25]]|26|$5|1Q|1R|1S|A|$1T|27]]|28|$5|1Q|1R|1S|A|$1T|29]]|2A|$5|1Q|1R|1S|A|$1T|2B]]|2C|$5|1Q|1R|1S|A|$1T|2D]]|2E|$5|1Q|1R|1S|A|$1T|2F]]|2G|$5|1Q|1R|1S|A|$1T|2H]]|2I|$5|1Q|1R|1S|A|$1T|2J]]|2K|$5|1Q|1R|1S|A|$1T|1M]]]]

This answer discusses how to make it work inside a framework, and with Cocoapods and Carthage

 modulemap approach

I use <code>modulemap</code> in my wrapper around CommonCrypto <a href="https://github.com/onmyway133/arcane" rel="noreferrer">https://github.com/onmyway133/arcane</a>, <a href="https://github.com/onmyway133/Reindeer" rel="noreferrer">https://github.com/onmyway133/Reindeer</a>

For those getting <code>header not found</code>, please take a look <a href="https://github.com/onmyway133/Arcane/issues/4" rel="noreferrer">https://github.com/onmyway133/Arcane/issues/4</a> or run <code>xcode-select --install</code>

<ul>
<li>Make a folder <code>CCommonCrypto</code> containing <code>module.modulemap</code>

<pre><code> module CCommonCrypto {
 header "/usr/include/CommonCrypto/CommonCrypto.h"
 export *
 }
</code></pre></li>
<li>Go to Built Settings -> Import Paths

<pre><code> ${SRCROOT}/Sources/CCommonCrypto
</code></pre></li>
</ul>

 Cocoapods with modulemap approach

<ul>
<li>Here is the podspec <a href="https://github.com/onmyway133/Arcane/blob/master/Arcane.podspec" rel="noreferrer">https://github.com/onmyway133/Arcane/blob/master/Arcane.podspec</a>

<pre><code> s.source_files = 'Sources/**/*.swift'
 s.xcconfig = { 'SWIFT_INCLUDE_PATHS' =&gt;
 '$(PODS_ROOT)/CommonCryptoSwift/Sources/CCommonCrypto' }
 s.preserve_paths = 'Sources/CCommonCrypto/module.modulemap'
</code></pre></li>
<li>Using <code>module_map</code> does not work, see <a href="https://github.com/CocoaPods/CocoaPods/issues/5271" rel="noreferrer">https://github.com/CocoaPods/CocoaPods/issues/5271</a></li>
<li>Using Local Development Pod with <code>path</code> does not work, see <a href="https://github.com/CocoaPods/CocoaPods/issues/809" rel="noreferrer">https://github.com/CocoaPods/CocoaPods/issues/809</a></li>
<li>That's why you see that my Example Podfile <a href="https://github.com/onmyway133/CommonCrypto.swift/blob/master/Example/CommonCryptoSwiftDemo/Podfile" rel="noreferrer">https://github.com/onmyway133/CommonCrypto.swift/blob/master/Example/CommonCryptoSwiftDemo/Podfile</a> points to the git repo

<pre><code> target 'CommonCryptoSwiftDemo' do
 pod 'CommonCryptoSwift', :git =&gt; 'https://github.com/onmyway133/CommonCrypto.swift'
 end
</code></pre></li>
</ul>

 public header approach

<ul>
<li><a href="https://github.com/honghaoz/Ji" rel="noreferrer">Ji</a> is a wrapper around libxml2, and it uses public header approach</li>
<li>It has a header file <a href="https://github.com/honghaoz/Ji/blob/master/Source/Ji.h" rel="noreferrer">https://github.com/honghaoz/Ji/blob/master/Source/Ji.h</a> with <code>Target Membership</code> set to <code>Public</code></li>
<li>It has a list of header files for libxml2 <a href="https://github.com/honghaoz/Ji/tree/master/Source/Ji-libxml" rel="noreferrer">https://github.com/honghaoz/Ji/tree/master/Source/Ji-libxml</a></li>
<li>It has Build Settings -> Header Search Paths

<pre><code> $(SDKROOT)/usr/include/libxml2
</code></pre></li>
<li>It has Build Settings -> Other Linker Flags

<pre><code> -lxml2
</code></pre></li>
</ul>

 Cocoapods with public header approach

<ul>
<li>Take a look at the podspec <a href="https://github.com/honghaoz/Ji/blob/master/Ji.podspec" rel="noreferrer">https://github.com/honghaoz/Ji/blob/master/Ji.podspec</a>

<pre><code> s.libraries = "xml2"
 s.xcconfig = { 'HEADER_SEARCH_PATHS' =&gt; '$(SDKROOT)/usr/include/libxml2', 'OTHER_LDFLAGS' =&gt; '-lxml2' }
</code></pre></li>
</ul>

 Interesting related posts

<ul>
<li><a href="https://stackoverflow.com/questions/24004732/how-to-call-c-from-swift">How to call C from Swift?</a></li>
<li><a href="https://spin.atomicobject.com/2015/02/23/c-libraries-swift/" rel="noreferrer">https://spin.atomicobject.com/2015/02/23/c-libraries-swift/</a></li>
</ul>

blocks|key|463857|text|模块地图解决方案可以是好的，并且对SDK更改具有很强的鲁棒性，但我发现它们在实践中使用起来很尴尬，而且在分发给其他人时也不像我所希望的那样可靠。为了让一切变得更简单，我走了一条不同的路：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|463858|复制标题就行。|463859|我知道脆弱。但是苹果几乎从来没有对CommonCrypto做过重大的改变，我的梦想是，如果不让CommonCrypto成为一个模块化的头，他们就不会以任何重要的方式改变它。|463860|所谓“复制标题”，我的意思是“剪切并粘贴所有需要的标题到项目中的一个大标题中，就像预处理器所做的那样。”作为您可以复制或修改的示例，请参阅RNCryptor.h。|offset|length|463861|请注意，所有这些文件都是在APSL2.0下授权的，这种方法有意维护版权和许可通知。我的级联步骤是在MIT下授权的，这只适用于下一个许可通知)。|463862|我并不是说这是一个漂亮的解决方案，但到目前为止，它似乎是一个非常简单的解决方案，无论是实现还是支持。|463863|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/RNCryptor/RNCryptor/blob/master/Sources/Cryptor/include/RNCryptor.h^0|0|0|0|1X|B|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@$H|Z|I|10|1|11]]|A|$]]|$1|J|3|K|5|6|7|12|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|13|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]]]

The modulemap solutions can be good, and are robust against SDK changes, but I've found them awkward to use in practice, and not as reliable as I'd like when handing things out to others. To try to make it all more foolproof, I went a different way:

Just copy the headers.

I know, fragile. But Apple almost never makes significant changes to CommonCrypto and I'm living the dream that they will not change it in any significant way without also finally making CommonCrypto a modular header.

By "copy the headers" I mean "cut and paste all of the headers you need into one massive header in your project just like the preprocessor would do." As an example of this that you can copy or adapt, see <a href="https://github.com/RNCryptor/RNCryptor/blob/master/Sources/Cryptor/include/RNCryptor.h" rel="nofollow noreferrer">RNCryptor.h</a>.

Note that all of these files are licensed under APSL 2.0, and this approach intentionally maintains the copyright and license notices. My concatenation step is licensed under MIT, and that only applies up to the next license notice).

I am not saying this is a beautiful solution, but so far it seems to have been an incredibly simple solution to both implement and support.

blocks|key|1251630|text|更简单、更健壮的方法是使用运行脚本阶段创建一个名为"CommonCryptoModuleMap“的聚合目标，以自动生成模块映射，并使用正确的Xcode/SDK路径：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1251631|​|1251632|📷|atomic|offset|length|1251633|1251634|1251635|运行脚本阶段应该包含以下bash：|1251636|#+This+if-statement+means+we'll+only+run+the+main+script+if+the+CommonCryptoModuleMap+directory+doesn't+exist
#+Because+otherwise+the+rest+of+the+script+causes+a+full+recompile+for+anything+where+CommonCrypto+is+a+dependency
#+Do+a+"Clean+Build+Folder"+to+remove+this+directory+and+trigger+the+rest+of+the+script+to+run
if+[+-d+"${BUILT_PRODUCTS_DIR}/CommonCryptoModuleMap"+];+then
++++echo+"${BUILT_PRODUCTS_DIR}/CommonCryptoModuleMap+directory+already+exists,+so+skipping+the+rest+of+the+script."
++++exit+0
fi

mkdir+-p+"${BUILT_PRODUCTS_DIR}/CommonCryptoModuleMap"
cat+<<EOF+>+"${BUILT_PRODUCTS_DIR}/CommonCryptoModuleMap/module.modulemap"
module+CommonCrypto+[system]+{
++++header+"${SDKROOT}/usr/include/CommonCrypto/CommonCrypto.h"
++++export+*
}
EOF|code-block|syntax|javascript|1251637|使用shell代码和${SDKROOT}意味着您不必硬编码系统间的Xcode.app路径，特别是如果您使用xcode-select切换到beta版本，或者构建在一个CI服务器上，在非标准位置安装多个版本。您也不需要硬编码SDK，所以这应该适用于iOS、macOS等。您也不需要在项目的源目录中有任何东西。|style|CODE|1251638|在创建这个目标之后，让您的库/框架使用一个目标依赖项来依赖它：|1251639|1251640|1251641|1251642|这将确保在构建框架之前生成模块映射。|1251643|macOS注意到：如果您也支持macOS，则需要将macosx添加到您刚刚创建的新聚合目标的Supported+Platforms构建设置中，否则它将不会将模块映射与其他框架产品放在正确的Debug派生数据文件夹中。|BOLD|1251644|1251645|1251646|1251647|接下来，将模块映射的父目录${BUILT_PRODUCTS_DIR}/CommonCryptoModuleMap添加到Swift部分(SWIFT_INCLUDE_PATHS)下的“导入路径”构建设置中：|1251648|1251649|1251650|1251651|如果在项目或xcconfig级别上定义了搜索路径，请记住添加$(inherited)行。|1251652|就这样，你现在应该可以import+CommonCrypto了|1251653|Xcode+10的更新|1251654|Xcode+10现在附带了一个CommonCrypto模块映射，这样就没有必要解决这个问题了。如果您想同时支持Xcode+9和10，可以在运行脚本阶段检查模块映射是否存在。|1251655|COMMON_CRYPTO_DIR="${SDKROOT}/usr/include/CommonCrypto"
if+[+-f+"${COMMON_CRYPTO_DIR}/module.modulemap"+]
then
+++echo+"CommonCrypto+already+exists,+skipping"
else
++++#+generate+the+module+map,+using+the+original+code+above
fi|1251656|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/3aa4f5ece52398b3a04d0e7ad42b1716.png|imageAlt|1|https://developer.qcloudimg.com/http-save/yehe-900000/d2933938b4d9e1fb1b618ae9979043d6.png|2|https://developer.qcloudimg.com/http-save/yehe-900000/0ebca05b11f804c356ec8b2eb56e5a89.png|3|https://developer.qcloudimg.com/http-save/yehe-900000/d99027c6c2c15af5b7d567d6f8622b2c.png|4|https://developer.qcloudimg.com/http-save/yehe-900000/5717b14fe29a3c46c16d2be3d0ddd933.png^0|0|0|0|1|0|0|0|1|1|0|0|0|0|A|A|1H|C|0|0|0|0|1|2|0|0|0|0|8|F|5|P|6|1A|J|2M|5|0|0|0|1|3|0|0|D|17|1V|J|0|0|0|1|4|0|0|U|C|0|B|J|0|0|0|0^^$0|@$1|2|3|4|5|6|7|24|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|25|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|26|8|@]|9|@$G|27|H|28|1|29]]|A|$]]|$1|I|3|E|5|F|7|2A|8|@]|9|@$G|2B|H|2C|1|2D]]|A|$]]|$1|J|3|C|5|6|7|2E|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|2F|8|@]|9|@]|A|$]]|$1|M|3|N|5|O|7|2G|8|@]|9|@]|A|$P|Q]]|$1|R|3|S|5|6|7|2H|8|@$G|2I|H|2J|T|U]|$G|2K|H|2L|T|U]]|9|@]|A|$]]|$1|V|3|W|5|6|7|2M|8|@]|9|@]|A|$]]|$1|X|3|C|5|6|7|2N|8|@]|9|@]|A|$]]|$1|Y|3|E|5|F|7|2O|8|@]|9|@$G|2P|H|2Q|1|2R]]|A|$]]|$1|Z|3|C|5|6|7|2S|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|2T|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|2U|8|@$G|2V|H|2W|T|14]|$G|2X|H|2Y|T|U]|$G|2Z|H|30|T|U]|$G|31|H|32|T|U]|$G|33|H|34|T|U]]|9|@]|A|$]]|$1|15|3|C|5|6|7|35|8|@]|9|@]|A|$]]|$1|16|3|E|5|F|7|36|8|@]|9|@$G|37|H|38|1|39]]|A|$]]|$1|17|3|C|5|6|7|3A|8|@]|9|@]|A|$]]|$1|18|3|19|5|6|7|3B|8|@$G|3C|H|3D|T|U]|$G|3E|H|3F|T|U]]|9|@]|A|$]]|$1|1A|3|C|5|6|7|3G|8|@]|9|@]|A|$]]|$1|1B|3|E|5|F|7|3H|8|@]|9|@$G|3I|H|3J|1|3K]]|A|$]]|$1|1C|3|C|5|6|7|3L|8|@]|9|@]|A|$]]|$1|1D|3|1E|5|6|7|3M|8|@$G|3N|H|3O|T|U]]|9|@]|A|$]]|$1|1F|3|1G|5|6|7|3P|8|@$G|3Q|H|3R|T|U]]|9|@]|A|$]]|$1|1H|3|1I|5|6|7|3S|8|@]|9|@]|A|$]]|$1|1J|3|1K|5|6|7|3T|8|@]|9|@]|A|$]]|$1|1L|3|1M|5|O|7|3U|8|@]|9|@]|A|$P|Q]]|$1|1N|3|-4|5|6|7|3V|8|@]|9|@]|A|$]]]|1O|$1P|$5|1Q|1R|1S|A|$1T|1U|1V|-4]]|1W|$5|1Q|1R|1S|A|$1T|1X|1V|-4]]|1Y|$5|1Q|1R|1S|A|$1T|1Z|1V|-4]]|20|$5|1Q|1R|1S|A|$1T|21|1V|-4]]|22|$5|1Q|1R|1S|A|$1T|23|1V|-4]]]]

Something a little simpler and more robust is to create an Aggregate target called "CommonCryptoModuleMap" with a Run Script phase to generate the module map automatically and with the correct Xcode/SDK path:

<a href="https://i.stack.imgur.com/gHLwb.png" rel="noreferrer"><img src="https://i.stack.imgur.com/gHLwb.png" alt="enter image description here"></a>
<a href="https://i.stack.imgur.com/DQZq0.png" rel="noreferrer"><img src="https://i.stack.imgur.com/DQZq0.png" alt="enter image description here"></a>

The Run Script phase should contain this bash:

<pre class="lang-sh prettyprint-override"><code># This if-statement means we'll only run the main script if the CommonCryptoModuleMap directory doesn't exist
# Because otherwise the rest of the script causes a full recompile for anything where CommonCrypto is a dependency
# Do a "Clean Build Folder" to remove this directory and trigger the rest of the script to run
if [ -d "${BUILT_PRODUCTS_DIR}/CommonCryptoModuleMap" ]; then
 echo "${BUILT_PRODUCTS_DIR}/CommonCryptoModuleMap directory already exists, so skipping the rest of the script."
 exit 0
fi

mkdir -p "${BUILT_PRODUCTS_DIR}/CommonCryptoModuleMap"
cat &lt;&lt;EOF &gt; "${BUILT_PRODUCTS_DIR}/CommonCryptoModuleMap/module.modulemap"
module CommonCrypto [system] {
 header "${SDKROOT}/usr/include/CommonCrypto/CommonCrypto.h"
 export *
}
EOF
</code></pre>

Using shell code and <code>${SDKROOT}</code> means you don't have to hard code the Xcode.app path which can vary system-to-system, especially if you use <code>xcode-select</code> to switch to a beta version, or are building on a CI server where multiple versions are installed in non-standard locations. You also don't need to hard code the SDK so this should work for iOS, macOS, etc. You also don't need to have anything sitting in your project's source directory.

After creating this target, make your library/framework depend on it with a Target Dependencies item:

<a href="https://i.stack.imgur.com/BA1fB.png" rel="noreferrer"><img src="https://i.stack.imgur.com/BA1fB.png" alt="enter image description here"></a>

This will ensure the module map is generated before your framework is built.

macOS note: If you're supporting <code>macOS</code> as well, you'll need to add <code>macosx</code> to the <code>Supported Platforms</code> build setting on the new aggregate target you just created, otherwise it won't put the module map in the correct <code>Debug</code> derived data folder with the rest of the framework products.

<a href="https://i.stack.imgur.com/96Lya.png" rel="noreferrer"><img src="https://i.stack.imgur.com/96Lya.png" alt="enter image description here"></a>

Next, add the module map's parent directory, <code>${BUILT_PRODUCTS_DIR}/CommonCryptoModuleMap</code>, to the "Import Paths" build setting under the Swift section (<code>SWIFT_INCLUDE_PATHS</code>):

<a href="https://i.stack.imgur.com/UAqEY.png" rel="noreferrer"><img src="https://i.stack.imgur.com/UAqEY.png" alt="enter image description here"></a>

Remember to add a <code>$(inherited)</code> line if you have search paths defined at the project or xcconfig level.

That's it, you should now be able to <code>import CommonCrypto</code>

Update for Xcode 10

Xcode 10 now ships with a CommonCrypto module map making this workaround unnecessary. If you would like to support both Xcode 9 and 10 you can do a check in the Run Script phase to see if the module map exists or not, e.g.

<pre class="lang-sh prettyprint-override"><code>COMMON_CRYPTO_DIR="${SDKROOT}/usr/include/CommonCrypto"
if [ -f "${COMMON_CRYPTO_DIR}/module.modulemap" ]
then
 echo "CommonCrypto already exists, skipping"
else
 # generate the module map, using the original code above
fi
</code></pre>

blocks|key|463965|text|我知道这是个老问题。但我想出了一种在Swift项目中使用库的替代方法，这可能对那些不想导入这些答案中介绍的框架的人有所帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|463966|在Swift项目中，在Objective中创建Objective桥接标头、创建NSData类别(或使用库的自定义类)。唯一的缺点是您必须在Objective中编写所有实现代码。例如：|463967|#import+"NSData%2BNSDataEncryptionExtension.h"
#import+<CommonCrypto/CommonCryptor.h>

@implementation+NSData+(NSDataEncryptionExtension)
-+(NSData+*)AES256EncryptWithKey:(NSString+*)key+{
++++//do+something
}

-+(NSData+*)AES256DecryptWithKey:(NSString+*)key+{
//do+something
}|code-block|syntax|javascript|463968|然后在目标-c桥接头中添加以下内容|463969|#import+"NSData%2BNSDataEncryptionExtension.h"|463970|然后在Swift课堂上做类似的事情：|463971|public+extension+String+{
func+encryp(withKey+key:String)+->+String?+{
++++if+let+data+=+self.data(using:+.utf8),+let+encrypedData+=+NSData(data:+data).aes256Encrypt(withKey:+key)+{
++++++++return+encrypedData.base64EncodedString()
++++}
++++return+nil
}
func+decryp(withKey+key:String)+->+String?+{
++++if+let+data+=+NSData(base64Encoded:+self,+options:+[]),+let+decrypedData+=+data.aes256Decrypt(withKey:+key)+{
++++++++return+decrypedData.UTF8String
++++}
++++return+nil
}
}|463972|它如预期的那样工作。|463973|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|10|8|@]|9|@]|A|$G|H]]|$1|Q|3|R|5|6|7|11|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

I know this is an old question. But I figure out an alternative way to use the library in Swift project, which might be helpful for those who don't want to import framework introduced in these answers.

In Swift project, create a Objective-C bridging header, create NSData category (or custom class that to use the library) in Objective-C. The only drawback would be that you have to write all implementation code in Objective-C. 
For example:

<pre><code>#import "NSData+NSDataEncryptionExtension.h"
#import &lt;CommonCrypto/CommonCryptor.h&gt;

@implementation NSData (NSDataEncryptionExtension)
- (NSData *)AES256EncryptWithKey:(NSString *)key {
 //do something
}

- (NSData *)AES256DecryptWithKey:(NSString *)key {
//do something
}
</code></pre>

And then in your objective-c bridging header, add this

<pre><code>#import "NSData+NSDataEncryptionExtension.h"
</code></pre>

And then in Swift class do similar thing:

<pre><code>public extension String {
func encryp(withKey key:String) -&gt; String? {
 if let data = self.data(using: .utf8), let encrypedData = NSData(data: data).aes256Encrypt(withKey: key) {
 return encrypedData.base64EncodedString()
 }
 return nil
}
func decryp(withKey key:String) -&gt; String? {
 if let data = NSData(base64Encoded: self, options: []), let decrypedData = data.aes256Decrypt(withKey: key) {
 return decrypedData.UTF8String
 }
 return nil
}
}
</code></pre>

It works as expected.

blocks|key|13062|text|@mogstad很好地将@stephencelis解决方案包装在Cocoapod中：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|13063|豆荚'libCommonCrypto‘|13064|其他可用的吊舱对我没有用。|13065|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

@mogstad has been kind enough to wrap @stephencelis solution in a Cocoapod:

pod 'libCommonCrypto'

The other pods available did not work for me.

blocks|key|1251759|text|警告:+iTunesConnect可能会使用该方法的+拒绝+应用程序。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1251760|我的团队中的新成员意外地破坏了一个顶级答案给出的解决方案，所以我决定将其合并到一个名为CommonCryptoModule的小型包装项目中。您可以手动或通过Cocoapods安装它：|1251761|pod+'CommonCryptoModule',+'~>+1.0.2'|code-block|syntax|javascript|1251762|然后，您所要做的就是导入需要CommonCrypto的模块，如下所示：|CODE|1251763|import+CommonCryptoModule|1251764|希望其他人觉得这有用。|1251765|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/48481667/1607485|1|https://github.com/nkukushkin/CommonCryptoModule^0|0|Q|U|5|R|2|0|0|0|2J|17|I|1|0|0|0|Z|E|C|0|0|0|B|0^^$0|@$1|2|3|4|5|6|7|13|8|@$9|14|A|15|B|C]|$9|16|A|17|B|C]]|D|@$9|18|A|19|1|1A]]|E|$]]|$1|F|3|G|5|6|7|1B|8|@$9|1C|A|1D|B|C]]|D|@$9|1E|A|1F|1|1G]]|E|$]]|$1|H|3|I|5|J|7|1H|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|1I|8|@$9|1J|A|1K|B|C]|$9|1L|A|1M|B|O]]|D|@]|E|$]]|$1|P|3|Q|5|J|7|1N|8|@]|D|@]|E|$K|L]]|$1|R|3|S|5|6|7|1O|8|@$9|1P|A|1Q|B|C]]|D|@]|E|$]]|$1|T|3|-4|5|6|7|1R|8|@]|D|@]|E|$]]]|U|$V|$5|W|X|Y|E|$Z|10]]|11|$5|W|X|Y|E|$Z|12]]]]

WARNING: iTunesConnect may <a href="https://stackoverflow.com/a/48481667/1607485">reject</a> apps that are using this method.

<hr>

New member on my team accidentally broke the solution given by one of the top answers, so I decided to consolidate it in a small wrapper project called <a href="https://github.com/nkukushkin/CommonCryptoModule" rel="nofollow noreferrer">CommonCryptoModule</a>. You can install it manually or via Cocoapods: 

<pre><code>pod 'CommonCryptoModule', '~&gt; 1.0.2'
</code></pre>

Then, all you have to do is to import the module where you need <code>CommonCrypto</code>, like so:

<pre><code>import CommonCryptoModule
</code></pre>

Hope someone else finds this useful.

blocks|key|1251797|text|我想我对迈克·韦勒的出色作品有了改进。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1251798|在包含此bash的Compile+Sources阶段之前添加一个运行脚本阶段：|offset|length|style|CODE|1251799|#+This+if-statement+means+we'll+only+run+the+main+script+if+the
#+CommonCrypto.framework+directory+doesn't+exist+because+otherwise
#+the+rest+of+the+script+causes+a+full+recompile+for+anything
#+where+CommonCrypto+is+a+dependency
#+Do+a+"Clean+Build+Folder"+to+remove+this+directory+and+trigger
#+the+rest+of+the+script+to+run

FRAMEWORK_DIR="${BUILT_PRODUCTS_DIR}/CommonCrypto.framework"

if+[+-d+"${FRAMEWORK_DIR}"+];+then
echo+"${FRAMEWORK_DIR}+already+exists,+so+skipping+the+rest+of+the+script."
exit+0
fi

mkdir+-p+"${FRAMEWORK_DIR}/Modules"
cat+<<EOF+>+"${FRAMEWORK_DIR}/Modules/module.modulemap"
module+CommonCrypto+[system]+{
++++header+"${SDKROOT}/usr/include/CommonCrypto/CommonCrypto.h"
++++export+*
}
EOF

ln+-sf+"${SDKROOT}/usr/include/CommonCrypto"+"${FRAMEWORK_DIR}/Headers"|code-block|syntax|javascript|1251800|这个脚本构建了一个基本框架，其中module.map位于正确的位置，然后依赖于Xcode对BUILT_PRODUCTS_DIR框架的自动搜索。|1251801|我将原始的CommonCrypto包含文件夹链接为框架的Header文件夹，因此结果也应该适用于目标C项目。|1251802|entityMap^0|0|9|F|0|0|19|I|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@$D|U|E|V|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|W|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|X|8|@$D|Y|E|Z|F|G]]|9|@]|A|$]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|R|$]]

I think I have an improvement to Mike Weller's excellent work.

Add a Run Script phase before the <code>Compile Sources</code> phase containing this bash:

<pre><code># This if-statement means we'll only run the main script if the
# CommonCrypto.framework directory doesn't exist because otherwise
# the rest of the script causes a full recompile for anything
# where CommonCrypto is a dependency
# Do a "Clean Build Folder" to remove this directory and trigger
# the rest of the script to run

FRAMEWORK_DIR="${BUILT_PRODUCTS_DIR}/CommonCrypto.framework"

if [ -d "${FRAMEWORK_DIR}" ]; then
echo "${FRAMEWORK_DIR} already exists, so skipping the rest of the script."
exit 0
fi

mkdir -p "${FRAMEWORK_DIR}/Modules"
cat &lt;&lt;EOF &gt; "${FRAMEWORK_DIR}/Modules/module.modulemap"
module CommonCrypto [system] {
 header "${SDKROOT}/usr/include/CommonCrypto/CommonCrypto.h"
 export *
}
EOF

ln -sf "${SDKROOT}/usr/include/CommonCrypto" "${FRAMEWORK_DIR}/Headers"
</code></pre>

This script constructs a bare bones framework with the module.map in the correct place and then relies on Xcode's automatic search of <code>BUILT_PRODUCTS_DIR</code> for frameworks.

I linked the original CommonCrypto include folder as the framework's Headers folder so the result should also function for Objective C projects.

blocks|key|13132|text|好消息！SWIFT4.2+(Xcode+10)终于提供了CommonCrypto！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|13133|只需在您的快速文件中添加import+CommonCrypto即可。|offset|length|style|CODE|13134|entityMap^0|0|C|J|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Good news! Swift 4.2 (Xcode 10) finally provides CommonCrypto!

Just add <code>import CommonCrypto</code> in your swift file.

blocks|key|1251892|text|我在jjrscott的答案中添加了一些cocoapods魔术，以防您需要在cocoapods库中使用CommonCrypto。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1251893|1)将这一行添加到podspec中：|offset|length|style|BOLD|1251894|s.script_phase+=+{+:name+=>+'CommonCrypto',+:script+=>+'sh+$PROJECT_DIR/../../install_common_crypto.sh',+:execution_position+=>+:before_compile+}|code-block|syntax|javascript|1251895|2)将其保存在您的库文件夹中或任何您喜欢的地方(但是，不要忘记相应地更改script_phase+.)|1251896|#+This+if-statement+means+we'll+only+run+the+main+script+if+the
#+CommonCrypto.framework+directory+doesn't+exist+because+otherwise
#+the+rest+of+the+script+causes+a+full+recompile+for+anything
#+where+CommonCrypto+is+a+dependency
#+Do+a+"Clean+Build+Folder"+to+remove+this+directory+and+trigger
#+the+rest+of+the+script+to+run
FRAMEWORK_DIR="${BUILT_PRODUCTS_DIR}/CommonCrypto.framework"

if+[+-d+"${FRAMEWORK_DIR}"+];+then
echo+"${FRAMEWORK_DIR}+already+exists,+so+skipping+the+rest+of+the+script."
exit+0
fi

mkdir+-p+"${FRAMEWORK_DIR}/Modules"
echo+"module+CommonCrypto+[system]+{
++++header+"${SDKROOT}/usr/include/CommonCrypto/CommonCrypto.h"
++++export+*
}"+>>+"${FRAMEWORK_DIR}/Modules/module.modulemap"

ln+-sf+"${SDKROOT}/usr/include/CommonCrypto"+"${FRAMEWORK_DIR}/Headers"|1251897|工作起来很有魅力:)|1251898|entityMap^0|0|0|2|0|0|0|1F|0|0|0|A|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@$D|W|E|X|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|Y|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|Z|8|@$D|10|E|11|F|G]]|9|@]|A|$]]|$1|O|3|P|5|J|7|12|8|@]|9|@]|A|$K|L]]|$1|Q|3|R|5|6|7|13|8|@$D|14|E|15|F|G]]|9|@]|A|$]]|$1|S|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|T|$]]

I've added some cocoapods magic to jjrscott's answer in case you need to use CommonCrypto in your cocoapods library.

<hr>

1) Add this line to your podspec:

<pre><code>s.script_phase = { :name =&gt; 'CommonCrypto', :script =&gt; 'sh $PROJECT_DIR/../../install_common_crypto.sh', :execution_position =&gt; :before_compile }
</code></pre>

2) Save this in your library folder or wherever you like (however don't forget to change the script_phase accordingly ...) 

<pre><code># This if-statement means we'll only run the main script if the
# CommonCrypto.framework directory doesn't exist because otherwise
# the rest of the script causes a full recompile for anything
# where CommonCrypto is a dependency
# Do a "Clean Build Folder" to remove this directory and trigger
# the rest of the script to run
FRAMEWORK_DIR="${BUILT_PRODUCTS_DIR}/CommonCrypto.framework"

if [ -d "${FRAMEWORK_DIR}" ]; then
echo "${FRAMEWORK_DIR} already exists, so skipping the rest of the script."
exit 0
fi

mkdir -p "${FRAMEWORK_DIR}/Modules"
echo "module CommonCrypto [system] {
 header "${SDKROOT}/usr/include/CommonCrypto/CommonCrypto.h"
 export *
}" &gt;&gt; "${FRAMEWORK_DIR}/Modules/module.modulemap"

ln -sf "${SDKROOT}/usr/include/CommonCrypto" "${FRAMEWORK_DIR}/Headers"
</code></pre>

Works like a charm :)

blocks|key|1251916|text|我不确定Xcode+9.2是否改变了一些东西，但现在要做到这一点要简单得多。我唯一需要做的就是在框架项目目录中创建一个名为"CommonCrypto“的文件夹，并在其中创建两个文件，其中一个文件名为"cc.h”，如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1251917|#include+<CommonCrypto/CommonCrypto.h>
#include+<CommonCrypto/CommonRandom.h>|code-block|syntax|javascript|1251918|另一个名为module.modulemap：|1251919|module+CommonCrypto+{
++++export+*
++++header+"cc.h"
}|1251920|(我不知道为什么不能在模块地图文件中直接引用SDKROOT区域的头文件，但我无法让它工作)|1251921|第三件事是找到“导入路径”设置并设置为$(SRCROOT)。实际上，如果您不希望CommonCrypto文件夹位于根级，则可以将它设置为任何您想要的文件夹。|1251922|在此之后，您应该能够使用|1251923|import+CommonCrypto|1251924|在任何快捷的文件和所有类型/功能/等是可用的。|1251925|不过，一个警告词--如果你的应用程序使用libCommonCrypto+(或libcoreCrypto)，对于一个不太成熟的黑客来说，将调试器附加到应用程序并找出传递给这些函数的键是非常容易的。|1251926|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|13|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|14|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|S|3|T|5|6|7|16|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|17|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|X|$]]

I'm not sure if something's changed with Xcode 9.2 but it's now much simpler to achieve this. The only things I had to do are create a folder called "CommonCrypto" in my framework project directory and create two files inside it, one called "cc.h" as follows:

<pre><code>#include &lt;CommonCrypto/CommonCrypto.h&gt;
#include &lt;CommonCrypto/CommonRandom.h&gt;
</code></pre>

And another called module.modulemap:

<pre><code>module CommonCrypto {
 export *
 header "cc.h"
}
</code></pre>

(I don't know why you can't reference header files from the SDKROOT area directly in a modulemap file but I couldn't get it to work)

The third thing is to find the "Import Paths" setting and set to $(SRCROOT).
In fact you can set it to whatever folder you want the CommonCrypto folder to be under, if you don't want it at the root level.

After this you should be able to use 

<pre><code>import CommonCrypto
</code></pre>

In any swift file and all the types/functions/etc. are available.

A word of warning though - if your app uses libCommonCrypto (or libcoreCrypto) it's exceptionally easy for a not-too-sophisticated hacker to attach a debugger to your app and find out what keys are being passed to these functions.

blocks|key|13226|text|如果您有以下问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|13227|ld:未找到-lapple_crypto库clang:+error:+linker命令失败，退出代码1(使用-v查看调用)|blockquote|13228|在Xcode+10中，Swift+4.0。CommonCrypto是框架的一部分。|13229|添加|13230|+import+CommonCrypto|code-block|syntax|javascript|13231|删除|13232|来自链接二进制的CommonCrpto库文件和构建阶段的库|unordered-list-item|13233|来自桥接头的import+CommonCrypto|offset|length|style|CODE|13234|这对我有用！|13235|entityMap^0|0|0|0|0|0|0|0|6|J|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|13|8|@]|9|@]|A|$]]|$1|E|3|F|5|6|7|14|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|15|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|16|8|@]|9|@]|A|$L|M]]|$1|N|3|O|5|6|7|17|8|@]|9|@]|A|$]]|$1|P|3|Q|5|R|7|18|8|@]|9|@]|A|$]]|$1|S|3|T|5|R|7|19|8|@$U|1A|V|1B|W|X]]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1C|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|11|$]]

In case you have the below issue :

<blockquote>
 ld: library not found for -lapple_crypto
 clang: error: linker command failed with exit code 1 (use -v to see invocation)
</blockquote>

In Xcode 10, Swift 4.0. CommonCrypto is a part of the framework.

Add 

<pre><code> import CommonCrypto
</code></pre>

Remove 

<ul>
<li>CommonCrpto lib file from link binary with libraries from Build
phases</li>
<li><code>import CommonCrypto</code> from Bridging header</li>
</ul>

This worked for me!

blocks|key|463761|text|适用于任何使用带有Xcode+10的迅速4.2的用户|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|463762|CommonCrypto模块现在由系统提供，因此您可以像其他任何系统框架一样直接导入它。|463763|import+CommonCrypto|code-block|syntax|javascript|463764|entityMap^0|9|8|I|5|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|U|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

For anyone using swift 4.2 with Xcode 10:

CommonCrypto module is now provided by the system, so you can directly import it like any other system framework.

<pre><code>import CommonCrypto

</code></pre>

blocks|key|464081|text|在更新Xcode之后，我也发生了同样的事情。我尝试了我所能做的一切，比如重新安装cocoapods和清理项目，但是没有成功。现在，在重启系统之后，这个问题已经解决了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|464082|entityMap^0|1U|2|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

It happened the same to me after updating Xcode. 
I tried everything I can do such as reinstalling cocoapods and cleaning the project, but it didn't work.
Now it's been solved after restart the system.

How do you import <code>CommonCrypto</code> in a Swift framework for iOS?

I understand how to use <code>CommonCrypto</code> in a Swift app: 
You add <code>#import &lt;CommonCrypto/CommonCrypto.h&gt;</code> to the bridging header.
However, Swift frameworks don't support bridging headers. The <a href="https://developer.apple.com/library/prerelease/ios/documentation/Swift/Conceptual/BuildingCocoaApps/MixandMatch.html" rel="noreferrer">documentation</a> says:

<blockquote>
 You can import external frameworks that have a pure Objective-C codebase, a pure Swift codebase, or a mixed-language codebase. The
 process for importing an external framework is the same whether the
 framework is written in a single language or contains files from both
 languages. When you import an external framework, make sure the
 Defines Module build setting for the framework you’re importing is set
 to Yes.
 
 You can import a framework into any Swift file within a different
 target using the following syntax:
</blockquote>

<pre><code>import FrameworkName
</code></pre>

Unfortunately, import <code>CommonCrypto</code> doesn't work. Neither does adding <code>#import &lt;CommonCrypto/CommonCrypto.h&gt;</code> to the umbrella header.

Importing CommonCrypto in a Swift framework

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

如何在Swift框架中为CommonCrypto导入iOS？我了解如何在Swift应用程序中使用CommonCrypto：将#import <CommonCrypto/CommonCrypto.h>添加到桥接头中。但是，Swift框架不支持桥接头。说：您可以导入具有纯目标C代码基、纯Swift代码基或混合语言代码基的外...

问在Swift框架中导入CommonCrypto
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Swift框架中导入CommonCryptoEN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Swift框架中导入CommonCrypto
EN