check for libsqlite3 during configure about node-sqlite3 HOT 10 CLOSED

There's code for checking at https://github.com/developmentseed/node-sqlite3/blob/master/wscript#L16-17. Seems it doesn't work correctly.

from node-sqlite3.

I'll take a look at fixing this up as I did with node-blend recently.

from node-sqlite3.

got exactly same issue, any status update?

from node-sqlite3.

@angelochen960 - 2793ca0 I added the option --internal-sqlite so for now you could checkout from master and do:

./configure --internal-sqlite
make

from node-sqlite3.

this got installed, also the usual ./configure, problem is only npm install sqlite3.
trying to do a test after this, but got:
Error: Cannot find module 'sqlite3'

i use this:var sqlite3 = require('sqlite3').verbose();

from node-sqlite3.

to run the tests locally you need to either do:

make test

or manually put the lib/ directory on your node path like:

 export NODE_PATH=`pwd`/lib

from node-sqlite3.

i run a local test:
make test
node-waf build
Waf: Entering directory /root/node-sqlite3/build' make[1]: Entering directory/root/node-sqlite3/deps/sqlite-autoconf-3070701'
make[1]: Nothing to be done for all'. make[1]: Leaving directory/root/node-sqlite3/deps/sqlite-autoconf-3070701'
Waf: Leaving directory `/root/node-sqlite3/build'
'build' finished successfully (0.016s)
Creating test database... This may take several minutes.
/bin/sh: line 3: 31907 Killed node test/support/createdb.js
make: *** [db] Error 137

from node-sqlite3.

the "killed" must be happening because you are on some host that limits cpu or ram. Perhaps, just don't run the tests then, and get on with coding :)

from node-sqlite3.

you are right! it works. now, how to move node-sqlite3 into the global node-modules? or have to use NODE_PATH all the time?

from node-sqlite3.

this should be improved and resolved again with a7de57a - now internal is truly default and external uses new configure checking code. closing.

from node-sqlite3.