Include sqlite3 about minghc HOT 10 CLOSED

For full clarity, the whole process of including sqlite3, per sqlite3 documentation, is:

> wget https://www.sqlite.org/2015/sqlite-amalgamation-3080803.zip
> tar -xzvf sqlite-amalgamation-3080803.zip
> cd sqlite-amalgamation-3080803
> gcc -shared sqlite3.c -o libsqlite3.a
> cp libsqlite3.a %MINGW%\lib
> cp sqlite3.h %MINGW%\include

In other words, this is extremely simple, but you do need to know what you are doing. This will allow packages such as peristent-sqlite to be installed without a problem on windows.

from minghc.

I don't think we want to distribute libraries as such - the intention was just to support cabal installers and setup programs. But a lot of people want us to include libraries, we need to think of a general answer and include it in the read me. @snoyberg

from minghc.

Ah right, I understand. It's a slippery slope and before you know it your simple package is becoming a huge burden to maintain (a.k.a. Haskell Platform). I think there is a difference between just including (Haskell) libraries and providing some additional commonly used C libraries to make life of using Haskell under Windows more bearable.

Btw, you might want to change the line "Add in C libraries to ease use of Haskell packages on Windows. Pull requests welcome." to be more descriptive.

from minghc.

Yep, we should figure out what our intention is, and fix the docs. I will try and figure out our options next week.

from minghc.

I wrote that line, and now I tend to agree that it's likely not something
we should undertake.

On Sat, Apr 4, 2015, 12:18 PM Neil Mitchell [email protected]
wrote:

Yep, we should figure out what our intention is, and fix the docs. I will
try and figure out our options next week.

—
Reply to this email directly or view it on GitHub
#37 (comment).

from minghc.

Maybe this problem will fix itself when Windows 10 is released and everyone starts writing Nuget packages to make installation/distribution of C libraries under Windows easier (since I do think that this is an OS-level issue, not a language- or compiler-level issue).

Closing issue.

from minghc.

Out of curiousity, why would you want to ship sqlite? The direct-sqlite package installs flawlessly by embedding the C code from sqlite inside the Haskell package. I use that (or rather sqlite-simple which builds on it), and it's very easy, far easier than shipping a separate library.

from minghc.

Hmmm if I recall correctly, it was because of persistent-sqlite through yesod. I ran into this issue, had to run my own build of sqlite on Windows, and figured I'd open a ticket since it would be a good proof-of-concept if minghc decided to go this route.

from minghc.

persistent-sqlite defaults to using a bundle sqlite3.c instead of using an installed library.

from minghc.

It appears you are correct. Then I forgot what I was trying to do back then; in any case, it's besides the point.

from minghc.