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
@@ -39,12 +39,12 @@ For example: ([GRDB.swift](https://github.com/groue/GRDB.swift)).
39
39
40
40
## Customization:
41
41
42
-
By default, SQLiteLib builds SQLite with options that match the built-in system version of SQLite on OSX and iOS (as of OSX 10.11.5, iOS 9.3.2), [with one exception*](#additional-details).
42
+
By default, SQLiteLib builds SQLite with options that match the built-in system version of SQLite on OSX and iOS (as of OSX 10.11.6, iOS 9.3.5), [with one exception*](#additional-details).
> By default, SQLiteLib compiles SQLite with options that match the built-in OSX/iOS version of SQLite (as of OSX 10.11, iOS 9.3.2), with one exception*.
47
+
> By default, SQLiteLib compiles SQLite with options that match the built-in OSX/iOS version of SQLite (as of OSX 10.11, iOS 9.3.5), with one exception*.
48
48
> You only need to follow the steps below if you wish to customize the options.
49
49
50
50
To specify additional options:
@@ -65,7 +65,7 @@ There is no need to modify any other files.
65
65
66
66
#### Compiling a Specific Version of SQLite:
67
67
68
-
SQLiteLib currently ships with the source for SQLite 3.13.0.
68
+
SQLiteLib currently ships with the source for SQLite 3.14.1.
69
69
70
70
If you'd like to compile a newer (or older) version, the process is simple:
71
71
@@ -94,11 +94,11 @@ You'll want the file named "sqlite-src-*version*.zip".
94
94
95
95
#### Default Compilation Options:
96
96
97
-
The built-in OSX/iOS version of SQLite were built with the following compilation options (as of OSX 10.11.5, iOS 9.3.2):
97
+
The built-in OSX/iOS version of SQLite were built with the following compilation options (as of OSX 10.11.6, iOS 9.3.5):
98
98
99
99
> Fetched using `PRAGMA compile_options;`
100
100
101
-
- MacOSX (10.11.5)
101
+
- MacOSX (10.11.6)
102
102
-`ENABLE_API_ARMOR`
103
103
-`ENABLE_FTS3`
104
104
-`ENABLE_FTS3_PARENTHESIS`
@@ -111,7 +111,7 @@ The built-in OSX/iOS version of SQLite were built with the following compilation
111
111
-`SYSTEM_MALLOC`
112
112
-`THREADSAFE=2`
113
113
114
-
- iPhoneOS (9.3.2)
114
+
- iPhoneOS (9.3.5)
115
115
-`ENABLE_API_ARMOR`
116
116
-`ENABLE_FTS3`
117
117
-`ENABLE_FTS3_PARENTHESIS`
@@ -127,7 +127,7 @@ The built-in OSX/iOS version of SQLite were built with the following compilation
127
127
128
128
SQLiteLib uses these settings with one exception - on iOS:
129
129
130
-
The SQLite code (verified in: 3.13.0) uses a deprecated function (`gethostuuid()`).
130
+
The SQLite code (verified in: 3.14.1) uses a deprecated function (`gethostuuid()`).
131
131
132
132
D. Richard Hipp (SQLite architect), suggests working around this on iOS using `-DSQLITE_ENABLE_LOCKING_STYLE=0`:
133
133
> "The SQLITE_ENABLE_LOCKING_STYLE thing is an apple-only extension that
@@ -140,7 +140,7 @@ D. Richard Hipp (SQLite architect), suggests working around this on iOS using `-
140
140
Thus, SQLiteLib uses `SQLITE_ENABLE_LOCKING_STYLE=1` on OSX,
141
141
**but on iOS, SQLiteLib compiles with `ENABLE_LOCKING_STYLE=0`**.
142
142
143
-
This removes the code that uses the deprecated function, but doesn't get rid of the warning that "`gethostuuid() is disabled`" (as of 3.13.0).
143
+
This removes the code that uses the deprecated function, but doesn't get rid of the warning that "`gethostuuid() is disabled`" (as of 3.14.1).
144
144
145
145
To prevent this warning, SQLiteLib separately specifies `-Wno-#warnings` when building for iOS.
146
146
@@ -174,4 +174,4 @@ This is a UI issue in Xcode - the path is properly set in the project.pbxproj fi
174
174
175
175
SQLiteLib's project will automatically generate this from the base template `SQLiteLib-USER.xcconfig.example` on first build, or you may copy and rename it yourself.
176
176
177
-
(Future builds will not display the warning. The warning does not affect functionality.)
177
+
(Future builds will not display the warning. The warning does not affect functionality.)
0 commit comments