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

Windows: node-gyp sets wrong include path #15

Closed
piscisaureus opened this issue Feb 9, 2012 · 3 comments
Closed

Windows: node-gyp sets wrong include path #15

piscisaureus opened this issue Feb 9, 2012 · 3 comments
Labels

Comments

@piscisaureus
Copy link
Contributor

My addon is on drive d:\ and my home dir is on drive c:.

This makes node-gyp set the include path as follows:

/I"..\..\..\..\..\C:Users\Bert Belder\.node-gyp\0.7\src" /I"..\..\..\..\..\C:Users\Bert Belder\.node-gyp\0.7\deps\uv\include" /I"..\..\..\..\..\C:Users\Bert Belder\.node-gyp\0.7\deps\v8\include"
@piscisaureus
Copy link
Contributor Author

You should use path.resolve instead of path.join btw. But that alone does not fix the issue.

@TooTallNate
Copy link
Contributor

Thanks for the report Bert. These are exactly the kind of kinks I wanna iron out. However, I don't know if there's anything I can do about it. It seems to be a bug in either gyp, gyp_addon, or the addon.gypi file.

I tried running gyp_addon and msbuild manually, not using node-gyp at all and the same thing happens :(

Thanks for the tip on path.resolve() though, I'll be sure to switch those over. Where do we go from here though?

bnoordhuis pushed a commit to nodejs/node-v0.x-archive that referenced this issue Mar 5, 2012
This fixes running gyp_addon from across filesystems on Windows.

This is essentially a gyp bug where it's not relativizing properly
across filesystems. See nodejs/node-gyp#15 for the gory details.
@TooTallNate
Copy link
Contributor

Should be fixed in node-gyp v0.2.2. Closing.

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

2 participants