Could not find auto-linked library 'swiftObjectiveC'

简介: Could not find auto-linked library 'swiftObjectiveC'

oc工程中使用swift的第三方库,结果没有一个swift文件,导致编译报错。

解决方案:建立一个swift文件(空的文件也可以)就可以。


允许 target 使用 swift 代码,开启这个配置后 Swift 的标准库将能够在该项目使用(使用 oc和 swift 混编可能导致包体积变大十几兆)

Build Options 中
Embedded Content Contains Swift Code 改为 YES (Xcode 8.1 and earlier)
Always Embed Swift Standard Libraries 改为 YES (Xcode 8.2+)

支持使用@import导入文件,当需要导入 framework 的时候这个选项必须是YES

Defines Module 改为 YES

目录
相关文章
|
2月前
|
Linux
dynamic shadow call stack support
dynamic shadow call stack support
|
Ubuntu Unix Linux
成功解决ERROR: Unable to find the development tool `cc` in your path; please make sure that you have the
成功解决ERROR: Unable to find the development tool `cc` in your path; please make sure that you have the
成功解决ERROR: Unable to find the development tool `cc` in your path; please make sure that you have the
|
6月前
|
资源调度 JavaScript 内存技术
error @achrinza/node-ipc@9.2.2: The engine “node“ is incompatible with this module. Expected version
error @achrinza/node-ipc@9.2.2: The engine “node“ is incompatible with this module. Expected version
429 0
|
6月前
|
Java
No tag [else] defined in tag library imported with prefix [c]] with root cause
No tag [else] defined in tag library imported with prefix [c]] with root cause 错误处理
47 0
|
11月前
|
数据库连接
(node:2612) DeprecationWarning: collection.ensureIndex is deprecated. Use createIndexes instead.
(node:2612) DeprecationWarning: collection.ensureIndex is deprecated. Use createIndexes instead.
|
缓存 内存技术
解决 Error: Node Sass does not yet support your current environment: OS X ...
解决 Error: Node Sass does not yet support your current environment: OS X ...
1395 0
Could not find com.serenegiant:common:4.1.1
Could not find com.serenegiant:common:4.1.1
253 0
MGA (Managed Global Area) Reference Note (Doc ID 2638904.1)
MGA (Managed Global Area) Reference Note (Doc ID 2638904.1)
321 0
|
算法
On the Correct and Complete Enumeration of the Core Search Space
在之前的文章中我们讨论了基于graph的DP-based算法,来解决join ordering的枚举问题。 这些DP算法通过join predicate描述的连通性,解决了枚举可能的表组合问题,但join graph本身(即使hypergraph)是无法完整的描述join语义的,因为连通边本身无法描述不同类型的join语义,例如left outer join/semi join/anti join...,因此即使找到了所谓的csg-cmp-pair,也不一定是有效的plan。 这篇paper讨论的就是这个问题,当枚举出一个csg-cmp-pair (S1 o S2),如何判断这是有效的join
442 0
On the Correct and Complete Enumeration of the Core Search Space
|
机器学习/深度学习
1064. Complete Binary Search Tree (30)
#include #include #include using namespace std; const int maxn = 1001; vector num(maxn), cbt(maxn); int n, c...
846 0