ericsink / cb Goto Github PK

The .NET tooling for web assembly is coming together, and soon the masses will demand SQLite in their browsers!

I know @jeromelaban did a bunch of work in unoplatform/Uno.sqlite-wasm to produce an e_sqlite3.bc file. What would it take to make this an official part of the main SQLitePCLRaw.provider.e_sqlite3 package?

IIRC, we're also waiting on the .NET team (mono-wasm team?) to define how *.bc files should be packaged so they flow through the toolchain into Emscripten. (I vaguly remember Immo mentioning something like a browser-wasm RID at one point.) Once this happens, I presume the same package could then work for both Blazor and Uno projects.

/cc @danroth27 @JeremyLikness @lewing @radical

While working on a Python3 wrapper for SQLite3 Multiple Ciphers several bugs/glitches were detected and fixed. Therefore the SQLite3 Multiple Ciphers version used in cb (and SQLitePCL.raw) should be updated to the latest version 1.8.6 (based on SQLite 3.46.0).

I tried to test this update in my cb fork, but the GitHub workflow fails for macOS with an obscure error message (see workflow log).

Unfortunately I don't have much experience with macOS. Could you please have a look to find out how to fix this problem? TIA.

Currently, the minimum requirement of the dynamic libraries on macOS x86_64 is

cb/bld> otool -l ./bin/e_sqlite3/mac/x86_64/libe_sqlite3.dylib | grep LC_BUILD_VERSION -A4
cmd LC_BUILD_VERSION
cmdsize 32
platform macos
sdk 13.1
minos 12.0

and It causes crash after successful compilation of dotnet apps built with https://github.com/ericsink/SQLitePCL.raw
such as https://github.com/jellyfin/jellyfin, Kareadita/Kavita#2026 on macOS 10.14

• jellyfin crash log

System.TypeInitializationException: The type initializer for 'Microsoft.Data.Sqlite.SqliteConnection' threw an exception.
 ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
 ---> System.DllNotFoundException: Unable to load shared library 'e_sqlite3' or one of its dependencies. In order to help diagnose loading problems, consider setting the DYLD_PRINT_LIBRARIES environment variable: 
dlopen(/Volumes/MACFOO/ConsoleApp/jellyfin-10.9.0/e_sqlite3.dylib, 1): image not found
dlopen(e_sqlite3.dylib, 1): image not found
dlopen(/Volumes/MACFOO/ConsoleApp/jellyfin-10.9.0/libe_sqlite3.dylib, 1): no suitable image found.  Did find:
	/Volumes/MACFOO/ConsoleApp/jellyfin-10.9.0/libe_sqlite3.dylib: cannot load 'libe_sqlite3.dylib' (load command 0x80000034 is unknown)
	/Volumes/MACFOO/ConsoleApp/jellyfin-10.9.0/libe_sqlite3.dylib: cannot load 'libe_sqlite3.dylib' (load command 0x80000034 is unknown)
dlopen(libe_sqlite3.dylib, 1): image not found
dlopen(/Volumes/MACFOO/ConsoleApp/jellyfin-10.9.0/e_sqlite3, 1): image not found
dlopen(e_sqlite3, 1): image not found
dlopen(/Volumes/MACFOO/ConsoleApp/jellyfin-10.9.0/libe_sqlite3, 1): image not found
dlopen(libe_sqlite3, 1): image not found

After compiling the libraries with additional option -mmacosx-version-min=10.14, There's no problem in my usage of the app.

Our legal is asking what license this code is released under and we don't see anything to inform us on that. Is it possible to associate a license with this project via the README, a CONTIRBUTING file or even a github license label?

It would be appreciated if you could add a simple specification about how to build this repo.

I adjusted bld/cb.cs in branch sqlite3mc of my fork of your cb repo, so that the mac builds no longer produce rather large numbers of warnings. This allows to detect "real" compile issues more easily.

Because I removed also almost all code that is not necessary for building the sqlite3mc libraries (to reduce usage of computing resources), you can't take the cb.cs file as is, but I can prepare a PR, if you want me to.