Linux Static Compilation Support

[mredig]

I am unable to compile my project for linux using the static sdk.

I don't know if it's a reasonable ask to ask for support, but if it is, I'd appreciate it!

[mredig]

Good news! I learned more about the static sdk and found that it's simply a matter of the fact that the static sdk doesn't include a static build of sqlite3! Apart from that, there's nothing stopping the sdk linking against a static musl build of sqlite with some headers available.

Now, where could I find that?! Well, Alpine is a distro that is built off of musl... Perhaps we could borrow its build of sqlite?

Yep! (to be fair, I had hefty AI assistance in all this).

Here's my workflow where I got this to work: https://github.com/mredig/FingerString/raw/refs/heads/main/.github/workflows/release.yml

I don't know if this helps in any way to get this baked into Lighter by default, but it's a decent workaround otherwise.

[helje5]

I think on Ubuntu it should be sufficient to just delete the libsqlite3.so link. The linker should then pickup the .a instead of the .so.

[helje5]

When you say

I am unable to compile my project for linux using the static sdk.

What error do you get and how do you try to compile it?

[mredig]

Sorry about the fire and forget driveby nature of my issues. It basically goes:

1. checkout project on linux
2. swift build - success
3. swift sdk install https://download.swift.org/swift-6.3.3-release/static-sdk/swift-6.3.3-RELEASE/swift-6.3.3-RELEASE_static-linux-0.1.0.artifactbundle.tar.gz --checksum 87c3eaf908e67c0e13a84367119e12273cec1d2cd3d81f7d74bb36722d6b607b (install the Static SDK)
4. swift build --swift-sdk x86_64-swift-linux-musl

and then you get

Building for debugging...
<module-includes>:1:10: note: in file included from <module-includes>:1:
1 | #include "shim.h"
  |          `- note: in file included from <module-includes>:1:
2 |

/root/swift/.build/checkouts/Lighter/Sources/SQLite3-Linux/shim.h:1:10: error: 'sqlite3.h' file not found
1 | #include <sqlite3.h>
  |          `- error: 'sqlite3.h' file not found
2 |

/root/swift/.build/checkouts/Lighter/Sources/Lighter/ConnectionHandlers/SQLConnectionHandler.swift:8:8: error: could not build C module 'SQLite3'
  6 | import struct Foundation.URL
  7 | import struct Foundation.TimeInterval
  8 | import SQLite3
    |        `- error: could not build C module 'SQLite3'
  9 |
 10 | /**
<module-includes>:1:10: note: in file included from <module-includes>:1:
1 | #include "shim.h"
  |          `- note: in file included from <module-includes>:1:
2 |

/root/swift/.build/checkouts/Lighter/Sources/SQLite3-Linux/shim.h:1:10: error: 'sqlite3.h' file not found
1 | #include <sqlite3.h>
  |          `- error: 'sqlite3.h' file not found
2 |

/root/swift/.build/checkouts/Lighter/Sources/Lighter/ConnectionHandlers/SQLConnectionHandler.swift:8:8: error: could not build C module 'SQLite3'
  6 | import struct Foundation.URL
  7 | import struct Foundation.TimeInterval
  8 | import SQLite3
    |        `- error: could not build C module 'SQLite3'
  9 |
 10 | /**

# ... truncated - basically a ton of the same errors repeated

I'll see if I can figure out what you mean by deleting the so - I assume you don't mean the system installation so file?

However, I suspect that won't work if it's compiled with glibc and not musl.

[mredig]

FWIW, it's entirely possible that this isn't possible, given that the Static SDK requires using musl and, if the library depends on sqlite as an external dependency, it'll almost definitely be compiled with glibc.

My main holdout is the doc referencing a dependency free api which, not having full grasped what that truly means, would imply to me that this has some sort of implementation of the sqlite protocol included in some way that wouldn't require linking to the sqlite system libs.

[mredig]

I have no recollection of this conversation, but it looks like I might have had a different solution in the past! Lighter-swift/Examples#2