You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -132,22 +127,6 @@ To install SQLite.swift as an Xcode sub-project:
132
127
You should now be able to `import SQLite` from any of your target’s source files and begin using SQLite.swift.
133
128
134
129
135
-
#### SQLCipher
136
-
137
-
> _Note_: To install with CocoaPods, [see above](#cocoapods).
138
-
139
-
To install SQLite.swift with [SQLCipher](http://sqlcipher.net) support:
140
-
141
-
1. Make sure the **sqlcipher** working copy is checked out in Xcode. If **sqlcipher.xcodeproj** is unavailable (_i.e._, it appears red), go to the **Source Control** menu and select **Check Out sqlcipher…** from the **sqlcipher** menu item.
142
-
143
-
2. Follow [the instructions above](#manual) with the **SQLiteCipher** target, instead.
144
-
145
-
> _Note:_ By default, SQLCipher compiles [without support for full-text search](https://github.com/sqlcipher/sqlcipher/issues/102). If you intend to use [FTS4](#full-text-search), make sure you add the following to **Other C Flags** in the **Build Settings** of the **sqlcipher** target (in the **sqlcipher.xcodeproj** project):
146
-
>
147
-
> - `-DSQLITE_ENABLE_FTS4`
148
-
> - `-DSQLITE_ENABLE_FTS3_PARENTHESIS`
149
-
150
-
151
130
### Frameworkless Targets
152
131
153
132
It’s possible to use SQLite.swift in a target that doesn’t support frameworks, including iOS 7 apps and OS X command line tools, though it takes a little extra work.
0 commit comments