Vitali this is true, but it's also reasonable to want to error on
compilation if you're not compiling against the correct version of
node.
SamShull, why not just #include node_version.h in your addon? That
should work just as well. But as far as your patch, rather than add
it to wscript, would it be reasonable to just #include node_version.h
inside node.h? I assume you're including at least that header in your
addon. So then you would have access to node version included with
that. Try it out and let us know if it works the way you want.
:Marco
On Aug 4, 1:45 am, Vitali Lovich <
vlov...@gmail.com> wrote:
> node_version.h doesn't tell you which version of node you are actually
> running on. That requires doing a runtime check.
>
>
>
> On Tue, Aug 3, 2010 at 10:31 PM, SamShull <
brickysa...@gmail.com> wrote:
> > Be nice if I included thishttp://
gist.github.com/507695
>
> > On Aug 4, 1:31 am, SamShull <
brickysa...@gmail.com> wrote:
> > > I am hoping that this patch can be added to the source for the simple
> > > task of adding node_version.h as one of the files to be installed
> > > during 'make install'. This would make creating addons that require a
> > > particular version of node much easier. Thanks.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "nodejs" group.
> > To post to this group, send email to
nod...@googlegroups.com.
> > To unsubscribe from this group, send email to
> >
nodejs+un...@googlegroups.com<
nodejs%2Bunsu...@googlegroups.com>
> > .