-
-
Notifications
You must be signed in to change notification settings - Fork 815
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
SQLCipher disappears when built on Windows #876
Comments
It looks like Can you try cloning the Then from you local checkout do:
Which will install all deps without installing node-sqlite3 itself. Then build node-sqlite3 like:
Context: What I think is happening is you are hitting a bug whereby npm > 2.x does not forward arguments to the underlying build tool (node-pre-gyp). More on this at mapbox/node-pre-gyp#300. By calling |
That appears to be exactly right. The resulting build from the cloned repo is able to encrypt and decrypt databases. I've tested it with the aforementioned test script to confirm, and I've also added the It looks like #300 in the Thank you again for your help! |
I'm attempting to build SQLite3 with SQLCipher in a Windows environment. So far I have had no success doing so. I'm running Node 8.5.0 with NPM 5.4.0.
This is about as basic a scenario as I can think up. In a new folder, I added test.js, and then called
npm install sqlite3 --build-from-source --sqlite_libname=sqlcipher --save
. This should have created a copy of sqlite3 that supports encryption. Then on the command line, I rannode test.js
.However, when I run the first code block in test.js, it creates an unencrypted database. Running the second block confirms unencrypted access. SQLCipher is not getting bundled in.
I re-ran the install command with --loglevel verbose and saved the output to this file. Nothing struck me as going wrong with it, though I did notice that the text "sqlcipher" never appeared - whether that means anything or not, I am not sure.
Any help would be appreciated!
The text was updated successfully, but these errors were encountered: