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.
indutny
All 20 comments
What do you think about bundling it here under a flag to see how well it will work?
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
on 17 Jun 2016
@Fishrock123 yep, the flag will just do this.
indutny
on 17 Jun 2016
Though, important thing about gyp.js is that it may not work on older versions of node, because of extensive ES6 usage. Is this going to be a problem for us, or can we manage it through semver?
indutny
on 17 Jun 2016
@indutny We might be able to transpile it back. Does it work on v4 or just v6?
Fishrock123
on 17 Jun 2016
Just v6 at the moment.
indutny
on 17 Jun 2016
@indutny See PR: #962
pmed
on 20 Jun 2016
@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?
indutny
on 10 Aug 2016
It's been quite a while. Any update on the state of things?
prasannavl
on 8 Jun 2017
I'll follow up on ~#962~ #1092
refack
on 8 Jun 2017
stalkerg
on 10 Jul 2017
@stalkerg: Hmm, maybe, but AFAICT, that:
- was last updated in April,
- has merge conflicts,
- has not been reviewed, and
- has not been merged.
馃槩
JamesMGreene
on 10 Jul 2017
ah... but I hope this problem is will fix
stalkerg
on 11 Jul 2017
Good news: https://chromium-review.googlesource.com/c/479691
@stalkerg thank you for bringing this to attention
refack
on 11 Jul 2017
+1
huan
on 24 Jul 2017
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 =)
Pomax
on 20 Aug 2017
@Pomax it's just a matter of limited resources... If you want to try and follow up on the work that's been done, I'd be very happy to help.
Good starting point: https://github.com/nodejs/node-gyp/pull/1092
refack
on 20 Aug 2017
~Won't it add dependencies on Ninja and C/C++ compilers, kinda making no difference, with C dependency instead of Python?~
Ops, sorry. I was sure that I was referenced here from https://github.com/lovell/sharp and didn't notice that it is node-gyp repository, not sharp's one.
ArmorDarks
on 3 Sep 2017
Won't it add dependencies on Ninja and C/C++ compilers, kinda making no difference, with C dependency instead of Python?
In any case, you currently has C dependencies for natives modules, in fact it would be really difficult to erradicate them...
piranna
on 3 Sep 2017
@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.
gibfahn
on 3 Sep 2017
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.
rvagg
on 20 Jun 2019
Related issues
swaj
路
3Comments
alexeyvo
路
3Comments
chen4393
路
3Comments
Flimm
路
3Comments
andrewaustin
路
3Comments
Most helpful comment
@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?