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
There are various crypto symbols that in the amalgamation should be declared SQLITE_PRIVATE because they are private to this library. Similarly sqlite3mc_initialize/shutdown should be SQLITE_API.
apsw sets SQLITE_API and SQLITE_EXTERN to static and the resulting DLL contains a single exported symbol required by Python to load the extension. To repeat do this in the apsw-sqlite3mc project under Linux:
- #166: Add missing SQLITE_PRIVATE attributes to several internal functions
- Add check for cipher configuration parameter legacy_page_size to accept only valid page sizes
There are various crypto symbols that in the amalgamation should be declared SQLITE_PRIVATE because they are private to this library. Similarly sqlite3mc_initialize/shutdown should be SQLITE_API.
apsw sets SQLITE_API and SQLITE_EXTERN to
static
and the resulting DLL contains a single exported symbol required by Python to load the extension. To repeat do this in the apsw-sqlite3mc project under Linux:Current list of publicly exported symbols:
The text was updated successfully, but these errors were encountered: