-
Notifications
You must be signed in to change notification settings - Fork 51
sqlite3_nif: Unspecified error #226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Does it open for a file instead of just |
Can you specify |
@warmwaffles unfortunately, no change with 0.11.9 and a database filename:
|
Found a problem, |
That's strange, even when using the settings for a 64 bit compiler, a 32 bit DLL is generated. |
Fixed via the instructions at riverrun/comeonin#75 - a 64 bit NIF was needed. |
@voltagex would you mind making a PR to the readme for special setup for windows? I think that would be beneficial to the next person. |
I can, but I'm still confused as to how the Makefile can call x64 host tools and produce an x86 DLL. Do you know anyone who would have more of an insight into the way NIFs work? To be honest, this is the first time I've touched Erlang / Elixir. I am also wondering if there's a way to get a better error message (the underlying error should have been something along the lines of "bad image format") |
There is a line in your compiler output that is really easy to miss
I wonder what your |
You're right! Oops! It seemed like even when opening "developer command prompt" for x64, I was getting the wrong compiler. The MSVC toolchain doesn't really use "$CC", but there is an equivalent vcvarsall.bat which sets the environment variables (mentioned by the other issue I linked) |
Yea normally when I am compiling stuff in windows, it's usually with CMake and it handles all that hoop jumping for me. |
As discussed in elixir-sqlite#226
Using Windows 10, exqite appears to build correctly, but I get
sqlite3_nif: Unspecified error
when trying to run{:ok, conn} = Exqlite.Sqlite3.open(":memory:")
The text was updated successfully, but these errors were encountered: