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
@@ -186,24 +210,6 @@ Some additional steps are required to install the application on an actual devic
186
210
187
211
7.**Add**.
188
212
189
-
### Frameworkless Targets
190
-
191
-
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.
192
-
193
-
1. In your target’s **Build Phases**, add **libsqlite3.dylib** to the **Link Binary With Libraries** build phase.
194
-
195
-
2. Copy the SQLite.swift source files (from its **SQLite** directory) into your Xcode project.
196
-
197
-
3. Add the following lines to your project’s [bridging header](https://developer.apple.com/library/prerelease/ios/documentation/Swift/Conceptual/BuildingCocoaApps/MixandMatch.html#//apple_ref/doc/uid/TP40014216-CH10-XID_79) (a file usually in the form of `$(TARGET_NAME)-Bridging-Header.h`).
198
-
199
-
```swift
200
-
#import<sqlite3.h>
201
-
#import"SQLite-Bridging.h"
202
-
```
203
-
204
-
> _Note:_ Adding SQLite.swift source files directly to your application will both remove the `SQLite` module namespace (no need—or ability—to `import SQLite`) and expose internal functions and variables. You will need to rename anything that conflicts with code of your own. Please [report any bugs](https://github.com/stephencelis/SQLite.swift/issues/new) (_e.g._, segfaults) you encounter.
205
-
206
-
207
213
## Getting Started
208
214
209
215
To use SQLite.swift classes or structures in your target’s source file, first import the `SQLite` module.
Copy file name to clipboardExpand all lines: Documentation/Planning.md
-5Lines changed: 0 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,15 +11,10 @@ _Lists agreed upon next steps in approximate priority order._
11
11
12
12
_A gathering point for ideas for new features. In general, the corresponding issue will be closed once it is added here, with the assumption that it will be referred to when it comes time to add the corresponding feature._
13
13
14
-
### Packaging
15
-
16
-
* linux support via Swift Package Manager, per [#315](https://github.com/stephencelis/SQLite.swift/issues/315), _in progress_: [#548](https://github.com/stephencelis/SQLite.swift/pull/548)
17
-
18
14
### Features
19
15
20
16
* encapsulate ATTACH DATABASE / DETACH DATABASE as methods, per [#30](https://github.com/stephencelis/SQLite.swift/issues/30)
21
17
* provide separate threads for update vs read, so updates don't block reads, per [#236](https://github.com/stephencelis/SQLite.swift/issues/236)
22
-
* expose more FTS4 options, e.g. virtual table support per [#164](https://github.com/stephencelis/SQLite.swift/issues/164)
23
18
* expose triggers, per [#164](https://github.com/stephencelis/SQLite.swift/issues/164)
0 commit comments