Skip to content
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

Debug Binding missing from NPM package #232

Closed
nibblesnbits opened this issue Nov 26, 2013 · 2 comments
Closed

Debug Binding missing from NPM package #232

nibblesnbits opened this issue Nov 26, 2013 · 2 comments

Comments

@nibblesnbits
Copy link

I'm not sure if this only applies to the tools I'm using, but when using Node.js Tools for Visual Studio, it tries to load the \lib\binding\Debug files, of which there are none in the current NPM package. Creating a copy of the Release folder works, but is hardly ideal.

@springmeyer
Copy link
Contributor

The intention is that some people may wish to custom compile a debug version or in the future we may wish to provide a pre-built binary of a debug version (we don't currently). Therefore a debug version is looked for first and then the release is used as a fallback (which currently should always be the case): https://github.com/mapbox/node-sqlite3/blob/master/lib/sqlite3.js#L4-L8

So, I don't see a problem here. If you want a debug version then you need to build it yourself by passing the --debug flag to npm install.

@springmeyer
Copy link
Contributor

This behavior of trying to check for the Debug folder is removed in #245

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants