On Sun, May 6, 2012 at 9:57 AM, Glenn Block <glenn.bl
...@gmail.com> wrote:
> Will a node-gyp binding allow deploying just a binary? Or will it still
> require the binary to be built locally?
> We have the node-sqlserver driver we are developing, initially only for
> Windows. The current plan was to include the binary so as not to
> require vs / express installed.
For the time being, it will still require builds to be done on the
install target. However, the plan is to pre-build them ahead of time.
That will probably land some time this year, and will only be done
for packages being built with the default node-gyp approach.
To be future-proofed to take advantage of this feature, use node-gyp
now; don't bundle binaries or fetch them from somewhere else or do
other custom stuff. If there's some reason it won't work for you,
now's the time to let us know.
On Sun, May 6, 2012 at 1:58 AM, Marcel Laverdet <mar
...@laverdet.com> wrote:
> For several hundred meg libraries the answer is much less obvious.. But even
> with a sophisticated or integrated build system, you still can't make
> assumptions about their environment? I think Node developers on Windows
> without a compiler even installed are quite common. Does node-gyp solve
> that?
Until pre-built binaries are available, it requires that the user have
a compiler on their system. MSVS Express is free and easy to install.
I don't think node-gyp installs it automatically, but I believe the
error message is fairly helpful.
