-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Consider gyp.js? #960
Comments
I think that is an excellent starting point. I suppose a flag would just change the child-process invocation to gyp.js? Not sure I'm the best person to lead on this though, I'm pretty pre-occupied. |
@Fishrock123 yep, the flag will just do this. |
Though, important thing about |
@indutny We might be able to transpile it back. Does it work on v4 or just v6? |
Just v6 at the moment. |
See issue nodejs#960 Added initial `gyp.js` support with --gypjs command line option. Environment variable `npm_config_gypjs` also turns this option on. Update configure and build usage strings depending on `npm_config_gypjs` environment variable
Added description for new command-line options and environment variables. See: nodejs#960
See issue nodejs#960 Added initial `gyp.js` support with --gypjs command line option. Environment variable `npm_config_gypjs` also turns this option on. Update configure and build usage strings depending on `npm_config_gypjs` environment variable. Set `npm_config_gypjs` env variable if `--gypjs` command-line option was set to affect usage text for `configure` and `build` commands. Update usage strings if `--gypjs` command-line option was supplied
Added description for new command-line options and environment variables. See: nodejs#960
Added description for new command-line options and environment variables. See: nodejs#960
See issue nodejs#960 Added initial `gyp.js` support with --gypjs command line option. Environment variable `npm_config_gypjs` also turns this option on. Update configure and build usage strings depending on `npm_config_gypjs` environment variable. Set `npm_config_gypjs` env variable if `--gypjs` command-line option was set to affect usage text for `configure` and `build` commands. Update usage strings if `--gypjs` command-line option was supplied Trying to load gyp.js module only if --gypjs command-line option was supplied.
Added description for new command-line options and environment variables. See: nodejs#960
See issue nodejs#960 Added initial `gyp.js` support with --gypjs command line option. Environment variable `npm_config_gypjs` also turns this option on. Update configure and build usage strings depending on `npm_config_gypjs` environment variable. Set `npm_config_gypjs` env variable if `--gypjs` command-line option was set to affect usage text for `configure` and `build` commands. Update usage strings if `--gypjs` command-line option was supplied Trying to load gyp.js module only if --gypjs command-line option was supplied.
@rvagg sorry, but I have feeling that we are not moving fast enough on this. Is there any way to expedite the review process? Should we invite more collaborators to this project? |
See: nodejs#960 Added initial `gyp.js` support with --gypjs command line option. Environment variable `npm_config_gypjs` also turns this option on. Update configure and build usage strings depending on `npm_config_gypjs` environment variable. Set `npm_config_gypjs` env variable if `--gypjs` command-line option was set to affect usage text for `configure` and `build` commands. Update usage strings if `--gypjs` command-line option was supplied Trying to load gyp.js module only if --gypjs command-line option was supplied.
It's been quite a while. Any update on the state of things? |
@stalkerg: Hmm, maybe, but AFAICT, that:
😢 |
ah... but I hope this problem is will fix |
@stalkerg thank you for bringing this to attention |
+1 |
It's been quite a while again, any update on the state of things? Removing the dependency on Python is super valuable for people who are JavaScript developers, not Python developers. Especially for those of us who need (or like) to use Windows (which does not come with any version of Python, and so anyone who is told they need python will download whatever is the latest version of Python. And then node-gyp still doesn't work. In 2017 =) |
Ops, sorry. I was sure that I was referenced here from https://github.com/lovell/sharp and didn't notice that it is |
In any case, you currently has C dependencies for natives modules, in fact it would be really difficult to erradicate them... |
@ArmorDarks GYP/Ninja/Cmake etc. are meta-build systems, they just generate the right Makefiles for each platform. The C/C++ compilation still has to be done whatever system you use. |
closing this with much sadness, gyp.js would have been nice but we were never organised enough to pull it of and @indutny has moved on now from it. If someone wants to pick this up again and push forward then please open a fresh PR and let's talk. |
Hello everyone!
We're working on https://github.com/indutny/gyp.js , which is a port of GYP to Node.js. I think the project is reaching the point when it could be actually used as an alternative "backend" for
node-gyp
.What do you think about bundling it here under a flag to see how well it will work?
Thank you,
Fedor.
The text was updated successfully, but these errors were encountered: