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

install error: Missing binding.gyp #367

Closed
DrYSG opened this issue Dec 13, 2013 · 6 comments
Closed

install error: Missing binding.gyp #367

DrYSG opened this issue Dec 13, 2013 · 6 comments
Assignees
Labels

Comments

@DrYSG
Copy link

DrYSG commented Dec 13, 2013

I am following up on issue #203 , I am assuming this is a different problem.

I did the following steps as you recommended:

  1. Upgrade to VS2013 PRO (we have MSDN subscription)
  2. upgrade node to v0.10.23
  3. npm install node-gyp -g [works fine]
  4. node-gyp clean [no problem]
  5. node-gyp configure (error below)

I am glad to help in any way (but I am a node novice, and have booked next week to learn all I can).

image

@DrYSG
Copy link
Author

DrYSG commented Jan 2, 2014

I am having problems building the package leveldown, (Level/leveldown#86 (comment)) and the owner is re-directing the issue to node-gyp.

@DrYSG

@springmeyer
Copy link
Contributor

This looks like user error. You are running node-gyp configure in a directory without a binding.gyp which likely means you are not in the directory you need to be. If you are trying to install node-leveldown then you need to get the code and run node-gyp configure build inside the node-leveldown checkout.

@DrYSG
Copy link
Author

DrYSG commented Jan 15, 2014

Tried what you suggested (created new leveldown directory) cd'd to it, and then the new install. But this is what I get today:
image

@JayBeavers JayBeavers self-assigned this Feb 11, 2014
@tk120404
Copy link

@DrYSG Can we close this issue?

@DrYSG
Copy link
Author

DrYSG commented Mar 14, 2018

@tk120404 well, I personally am not interested in this problem anymore. (I am not using leveldown)

@tk120404
Copy link

@DrYSG I hope this would have got fixed by now. So can you please close this

@DrYSG DrYSG closed this as completed Mar 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants