Why is it that, when you install node, it automatically installs npm, which automatically installs node-gyp, but node and npm end up in your PATH, whereas node-gyp does not? I ask because the C library build script makes the availability of the bindings contingent upon the presence of node on the PATH. It would be nice if I didn't have to deduce the location of node-gyp from the directory in which I find node - i.e., $(dirname which node)/../lib/node_modules/npm/bin/node-gyp-bin/node-gyp. OTOH I'd really like to avoid having to tell people that, if they want the bindings, they need to first npm install -g node-gyp, especially knowing that node-gyp is already on their system whenever node is on their system. Perhaps node-gyp should also be bundled with node, like npm, since it kind of already is.

Anyhoo, my solution so far is to

node_bindings: $(SOL_LIB_OUTPUT)

    # Install dependencies
    node -e 'Object.keys(require("./package.json").dependencies).map(function(item){console.log(item);})' | xargs npm install

    # Build the package without clobbering build/
    SOLETTA_FROM_MAKE=true $(dirname `which node`)/../lib/node_modules/npm/bin/node-gyp-bin/node-gyp configure
    SOLETTA_FROM_MAKE=true $(dirname `which node`)/../lib/node_modules/npm/bin/node-gyp-bin/node-gyp build

PHONY += node_bindings

I guess if there's no cleaner solution then this issue can be closed.

Uh oh!

Modify output directory #848

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions