setting of gyp variables via command line

[kontrafiktion]

As far as I understand the gyp documentation, I should be able to set a gyp variable using

  node-gyp configure -DLNNZ_VERSION=10

And in my binding.gyp file:

  'variables': {
    'LNNZ_VERSION%': '11'
  },

I would expect that the value of LNNZ_VERSION is 10 with the above invocation. Am I doing something wrong, or is this not supported by node-gyp?

Background: depending on the version of Oracle installed on the system, there is either a lnnz10 or a lnnz11 library. And the build must use the correct one ...
The only other solution would be to create a dynamic link 'lnnz' and use that as dependency

Any input?

[TooTallNate]

Try doing:

node-gyp configure --LNNZ_VERSION=10

Or alternatively:

node-gyp configure -- -DLNNZ_VERSION=10

[kontrafiktion]

If that is documented somewhere, I haven't found it.
If it is not documented, please add it. If it is documented, please
ensure that it can be found when googling for "command line" "variable" "node-gyp"

[Rantanen]

This could use better documentation. It's nasty especially as the README links to the gyp format reference which mentions the -D flag.

Ironically what vrvolle requested is now true as this issue can be found by googling.

[piranna]

How can this be done when installing a package with npm install?

[TooTallNate]

Just pass it along as a flag to npm. Unhandled options from npm get turned into gyp flags. See https://github.com/TooTallNate/node-speaker#audio-backend-selection for an example.

$ npm install foo --LNNZ_VERSION=10

Let me know if that doesn't work as expected.

[piranna]

Oh cool, thanks! Just didn't know it :-) I'll try it and tell you if it works ;-)

[piranna]

Ok, that worked :-) Thank you @TooTallNate! :-D