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

*.gyp support #14

Open
stevenvachon opened this issue Apr 10, 2017 · 3 comments
Open

*.gyp support #14

stevenvachon opened this issue Apr 10, 2017 · 3 comments

Comments

@stevenvachon
Copy link

Using gyp.js or gyp, we could provide backward-compatibility with current Node.js projects. This would provide time to deprecate gyp until removing support.

@refack
Copy link

refack commented Apr 10, 2017

I'm willing to tackle this one.

@eljefedelrodeodeljefe
Copy link
Owner

I like the idea. Slightly related is #16

@eljefedelrodeodeljefe
Copy link
Owner

Gyp handles finding binaries and headers. This is what the rather verbose part of this repo does too, but last years developments by MS can tackle this better. Just FYI.

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

No branches or pull requests

3 participants