nw-gyp

Native addon build tool for node-webkit

nw-gyp is a hack on node-gyp to build native modules for node-webkit. We are trying to provide a smooth way for developers rather than specifying a lot of command line arguments.

It supports node-webkit starts from v0.3.2 and users need to manually specify the version of node-webkit currently.

Features:

Easy to use, consistent interface
Same commands to build your module on every platform
Supports multiple target versions of Node

Installation

You can install with npm:

$ npm install -g nw-gyp

You will also need to install:

On Unix:
- python (v2.7 recommended, v3.x.x is not supported)
- make
- A proper C/C++ compiler toolchain, like GCC
On Windows:
- Python (v2.7.3 recommended, v3.x.x is not supported)
- Windows XP/Vista/7:
  - Microsoft Visual Studio C++ 2010 (Express version works well)
  - For 64-bit builds of node and native modules you will also need the Windows 7 64-bit SDK
    - If the install fails, try uninstalling any C++ 2010 x64&x86 Redistributable that you have installed first.
  - If you get errors that the 64-bit compilers are not installed you may also need the compiler update for the Windows SDK 7.1
- Windows 7/8:
  - Microsoft Visual Studio C++ 2012 for Windows Desktop (Express version works well)

Note that OS X is just a flavour of Unix and so needs python, make, and C/C++. An easy way to obtain these is to install XCode from Apple, and then use it to install the command line tools (under Preferences -> Downloads).

How to Use

To compile your native addon, first go to its root directory:

$ cd my_node_addon

The next step is to generate the appropriate project build files for the current platform. Use configure for that:

$ nw-gyp configure --target=<0.3.2 or other nw version>

Note: The configure step looks for the binding.gyp file in the current directory to processs. See below for instructions on creating the binding.gyp file.

Now you will have either a Makefile (on Unix platforms) or a vcxproj file (on Windows) in the build/ directory. Next invoke the build command:

$ nw-gyp build

Now you have your compiled .node bindings file! The compiled bindings end up in build/Debug/ or build/Release/, depending on the build mode. At this point you can require the .node file with Node and run your tests!

Note: To create a Debug build of the bindings file, pass the --debug (or -d) switch when running the either configure or build command.

Note: nw.js is packed with Node.js version 0.11.13 and a different version of V8 (3.28.71.2) than the one Node.js 0.11.13 has (3.24.35.22), it might lead to some inconsistent behaviour when building your native modules (see rvagg/nan#285).

The "binding.gyp" file

Previously when node had node-waf you had to write a wscript file. The replacement for that is the binding.gyp file, which describes the configuration to build your module in a JSON-like format. This file gets placed in the root of your package, alongside the package.json file.

A barebones gyp file appropriate for building a node addon looks like:

{
  "targets": [
    {
      "target_name": "binding",
      "sources": [ "src/binding.cc" ]
    }
  ]
}

Some additional resources for writing gyp files:

Commands

nw-gyp responds to the following commands:

Command	Description
`build`	Invokes `make`/`msbuild.exe` and builds the native addon
`clean`	Removes any the `build` dir if it exists
`configure`	Generates project build files for the current platform
`rebuild`	Runs "clean", "configure" and "build" all in a row
`install`	Installs node development header files for the given version
`list`	Lists the currently installed node development file versions
`remove`	Removes the node development header files for the given version

License

(The MIT License)

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Rob-- / nw-gyp