I don't think we should be linking to someone else's documentation about our project. We should just have the documentation required.

I don't think we should be linking to someone else's documentation about our project. We should just have the documentation required.

It makes sense. And what do you think about just adding some little text explaining the need of adding this linker flag?

I removed the external documentation and changed the note, but if you don't think we need this, I can close the PR without any problems. 😄

Maybe related - #5782

I think a more complete section in the docs would be useful. This topic comes up regularly, and there's a lot of confusion around it.

In summary, if you're using the iOS system-provided sqlite library, you're going to have -lsqlite3 somewhere. It is necessary. If you're bundling your own sqlite binary, as in #5782, or possibly using something like SQLCipher, you absolutely do not want -lsqlite3 to be there.

The SqlDelight plugin includes it by default. If you're building a dynamic framework with Kotlin/KMP, which I believe is now the default, then -lsqlite3 carries over (IIRC). You don't need to set it in Xcode. That is why some tutorials say you should use a dynamic framework, without really explaining the why. If you're building a static framework, you need to add -lsqlite3 in Xcode.

I'm on the fence about trying to detect if you're bringing your own sqlite. I can see how that might help, but I also lean more towards doing this kind of stuff explicitly.

The tricky thing I've found with KMP is that the devs setting up KMP tend to be Android devs, and on average don't know much about Xcode tooling or linking. So some concise "Xcode tooling for Kotlin devs" doc either exists or is long overdue to be published (not necessarily here), but I digress.

TL;DR it would probably be useful to have a more detailed section on this explaining it. I'd take a stab at expanding this one directly, but I'm already super behind for today, so for sure not today :)