coilyco-flight-deck/eco-replay
1
0
Fork 0
Code Issues 9 Pull requests Projects Releases Packages Wiki Activity Actions

Cache native libe_sqlite3.so install into Eco's apphost dir #6

New issue
Open
opened 2026-05-23 20:54:17 +00:00 by coilysiren · 0 comments
coilysiren commented 2026-05-23 20:54:17 +00:00
Owner
Copy link

Originally filed by @coilysiren on 2026-05-18T06:45:38Z - https://github.com/coilysiren/eco-replay/issues/2

Problem

Eco's mod loader uses AssemblyLoadContext.Default.LoadFromStream, which doesn't add the mod folder to .NET's native-library search path. So when Microsoft.Data.Sqlite P/Invokes e_sqlite3, the runtime looks in Eco's apphost extraction dir (e.g. ~/.net/EcoServer/<hash>/) and not in Mods/EcoReplay/.

Current workaround: manual symlink:

ln -sf /home/kai/Steam/steamapps/common/EcoServer/Mods/EcoReplay/libe_sqlite3.so \
       /home/kai/.net/EcoServer/oXJfcCrti-5I/libe_sqlite3.so

The hash oXJfcCrti-5I is stable per Eco-binary build but resets when Eco updates.

Next steps

  • Add an install-mod step (Makefile target) that re-symlinks after every install/Eco-update.
  • Or: drop Microsoft.Data.Sqlite in favor of a pure-managed SQLite (e.g. dotnet/runtime's built-in System.Data.SQLite once a Linux-native build is in the chain — see the work already done in /tmp during overnight session to build libSQLite.Interop.so from SDS 1.0.119 source).
  • Or: use SetDllImportResolver more aggressively, called from a module-initializer instead of from Initialize() so it fires before any other code touches Microsoft.Data.Sqlite. The current resolver code is wired up but Eco's pre-init reflection scan likely triggers SqliteConnection's static cctor before my plugin's Initialize runs.
_Originally filed by @coilysiren on 2026-05-18T06:45:38Z - [https://github.com/coilysiren/eco-replay/issues/2](https://github.com/coilysiren/eco-replay/issues/2)_ **Problem** Eco's mod loader uses `AssemblyLoadContext.Default.LoadFromStream`, which doesn't add the mod folder to .NET's native-library search path. So when `Microsoft.Data.Sqlite` P/Invokes `e_sqlite3`, the runtime looks in Eco's apphost extraction dir (e.g. `~/.net/EcoServer/<hash>/`) and not in `Mods/EcoReplay/`. **Current workaround:** manual symlink: ``` ln -sf /home/kai/Steam/steamapps/common/EcoServer/Mods/EcoReplay/libe_sqlite3.so \ /home/kai/.net/EcoServer/oXJfcCrti-5I/libe_sqlite3.so ``` The hash `oXJfcCrti-5I` is stable per Eco-binary build but resets when Eco updates. **Next steps** - Add an `install-mod` step (Makefile target) that re-symlinks after every install/Eco-update. - Or: drop `Microsoft.Data.Sqlite` in favor of a pure-managed SQLite (e.g. `dotnet/runtime`'s built-in `System.Data.SQLite` once a Linux-native build is in the chain — see the work already done in /tmp during overnight session to build `libSQLite.Interop.so` from SDS 1.0.119 source). - Or: use `SetDllImportResolver` more aggressively, called from a module-initializer instead of from `Initialize()` so it fires before any other code touches `Microsoft.Data.Sqlite`. The current resolver code is wired up but Eco's pre-init reflection scan likely triggers `SqliteConnection`'s static cctor before my plugin's `Initialize` runs.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/eco-replay#6
No description provided.