Nate - i'm not "against" npm so to speak. it just doesn't suit my
requirements as i like to do my own builds on a build machine and roll
everything out to the production machines i am using and have full
control over where everything goes. npm takes too much control away
from me and i am a control
Ok thanks for the confirmation Isaac. The latest version of node-gyp
(v0.0.5) now has its dependencies bundled.
On Fri, Feb 10, 2012 at 8:20 PM, Isaac Schlueter wrote:
> On Fri, Feb 10, 2012 at 18:34, Nathan Rajlich
> wrote:
> > And on top of that, I could just as easily just start commiting th
On Fri, Feb 10, 2012 at 18:34, Nathan Rajlich wrote:
> And on top of that, I could just as easily just start commiting the
> node_modules dir so that git-clone works properly.
That's a good idea regardless, actually. Commit the node_modules
folder, and list all the deps as bundledDependencies.
And on top of that, I could just as easily just start commiting the
node_modules dir so that git-clone works properly. Then what argument is
there for not using node-gyp?
On Fri, Feb 10, 2012 at 6:32 PM, Nathan Rajlich wrote:
> So Billy your argument is that you don't want to use node-gyp since i
So Billy your argument is that you don't want to use node-gyp since it has
dependencies, and you for some reason are against npm? Well that's a
first... What possible argument could you have at this point for not
wanting to use npm? It comes with node!!!
Additionally, limiting yourself to just mod
as an alternative to having gyp as an npm module, how about having a
node-sdk build of core with everything included to allow building of c+
+ modules and no need to install/use npm or any other external
modules? this is the way .Net and Java do things and it seems to
work...
On Feb 11, 12:54 am,
i tend to agree with Roman's sentiments. Whatever is used to build
addons should be included with the core node package and not be an
external module. node-waf worked really nice as far as i was
concerned.
also, node-gyp has a ton of dependencies which means if i don't want
to use npm (which i rea
I think you guys are reinventing the wheel here with respect to building
addons. Gyp and CMake were create specifically so you don't need to roll
your own system. Maybe it is just me but I liked the fact that node-waf
came bundled with the node install. This meant that I didn't have to go
fetch
On Sun, Feb 5, 2012 at 9:39 PM, Isaac Schlueter wrote:
> Wow, that looks really cool.
>
> The readme doesn't mentioning actually creating a gyp file. You still
> have to do that, right? It'd be nice to document what it should look
> like.
>
README updated! Thanks for the shout-out on nodeup to
Wow, that looks really cool.
The readme doesn't mentioning actually creating a gyp file. You still
have to do that, right? It'd be nice to document what it should look
like.
On Sun, Feb 5, 2012 at 19:15, Christopher Jeffrey wrote:
> Works well for me, very painless. I hope others start support
Works well for me, very painless. I hope others start supporting it
soon.
On Feb 5, 7:17 pm, Nathan Rajlich wrote:
> Ok I just tagged and published v0.0.1 of node-gyp on npm.
>
> Here is the repo:https://github.com/TooTallNate/node-gyp
>
> Native addon devs, please try it out and begin migrating
Ok I just tagged and published v0.0.1 of node-gyp on npm.
Here is the repo: https://github.com/TooTallNate/node-gyp
Native addon devs, please try it out and begin migrating your module to
using gyp. Let me know about your results!!
On Fri, Feb 3, 2012 at 11:13 PM, rhdoenges wrote:
> I will con
I will contribute!
On Feb 3, 2:53 pm, Nathan Rajlich wrote:
> Just so that people aren't duplicating efforts, I have begun creating a
> `node-gyp` project as described earlier in this thread. I'll be working on
> getting an initial version out by the end of this weekend that will
> hopefully be u
13 matches
Mail list logo
